Clock Drift / Time Sync
Also known as: time skew, clock synchronisation
What is it?
Clock drift is the slow, gradual way two computers' internal clocks fall out of agreement with each other over time, even when they started out matching. Every computer keeps its own clock, and these clocks are not perfectly accurate, so one machine's idea of the current time can creep ahead of or behind another's by seconds or more if nothing corrects it. Time sync is the fix: a process such as NTP (Network Time Protocol, a standard internet service that automatically keeps a computer's clock accurate) regularly nudges each machine's clock back into agreement with a trusted reference, keeping their timestamps comparable.
This matters in signal trading because so much depends on time being correct and consistent across systems. When does a signal become too old to act on, how long did a signal take to reach you, and whether two events happened in the right order, are all questions answered by comparing timestamps. If your own machine's clock has drifted, those comparisons become unreliable.
For example, if a server's clock is running a few seconds fast, perfectly fresh signals can look as though they have already expired, and the measured delay can appear much larger than it really is, causing the system to wrongly skip valid trades or accept stale ones. A common and confusing mistake is to chase a delivery problem for late signals when the real culprit is simply a drifted local clock. The practical rule is straightforward: keep automatic time sync running on any machine that handles or executes signals, and never run trading automation on a computer whose clock is not kept in sync.
Why it matters: If your machine's clock drifts, signal timestamps, expiry checks, and latency measurements all become unreliable.
Drifted clocks corrupt expiry and latency logic, causing wrong skips or accepts.
Real-world example
A VPS clock 3 seconds fast makes fresh signals look expired and inflates measured latency, triggering false skips.
How SignalBots handles it
SignalBots stamps signals from a synced source so expiry and latency are measured against a reliable clock, not a drifting one.
Pro tip
Keep time sync running on any machine that executes signals; never trade automation on an unsynced clock.
Common pitfalls
Diagnosing 'late signals' that are really a drifted local clock, not a delivery problem.
Frequently asked questions
How does clock drift affect signal expiry?
A wrong local clock can mark fresh signals as expired or accept stale ones. Keeping automatic time sync running prevents this so expiry checks stay accurate.
How do I keep my clock in sync?
Enable automatic time syncing on your device or server, usually via NTP, a standard internet service that quietly corrects your clock against a trusted reference.
Why do my signals look delayed when delivery is fine?
Often the real cause is a drifted local clock making timestamps look wrong, not a slow connection. Checking your time sync first can save chasing a delivery problem that is not there.
Does clock drift matter if I trade manually?
It matters less for a person glancing at a chart, but it still affects expiry checks and any latency figures you read. For automation it is critical.
Is a few seconds of drift really a problem?
For short-term and OTC trades, yes. A few seconds can be the difference between a signal counted as fresh and one wrongly treated as expired, so accuracy matters.