A computer clock that is off by three or four seconds sounds harmless. For scalping it is not, and it hides well because nothing looks broken.
Take a news release scheduled for a specific second. A local clock running slow by several seconds means a manual countdown or an automated trigger fires late. A clock running fast fires early, before the data is out.
Any EA that uses the local time for a session filter or a news window inherits the same error. Log timestamps also stop lining up with the broker's records, so reviewing a fill against server history becomes confusing when the two disagree by seconds.
Drift happens because computer clocks are not precise, and the built-in sync in some systems only runs occasionally. Virtual servers can drift more, especially after being paused or moved.
Syncing the clock more often against a reliable time source, and checking the offset before the session, takes a minute and removes a whole class of doubt.
How often does your machine sync its clock, and have you ever caught a visible offset on a VPS?
A few seconds of clock drift is nothing. That is the myth
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
-
FXS London Scalper
- Posts: 978
- Joined: Sun Oct 18, 2026 12:25 pm
Re: A few seconds of clock drift is nothing. That is the myth
A manual countdown that's several seconds off is enough to enter right into the release spike. Enabling automatic time sync and checking the clock against a time server before news trading costs nothing.
FXS Official Team | London Session Desk
-
Amanhasnoname
- Posts: 2060
- Joined: Fri Oct 30, 2026 9:45 am
Re: A few seconds of clock drift is nothing. That is the myth
I once fired a news EA three seconds early because the VPS clock had drifted after a reboot. The order filled on a thin pre-release quote, and the real spike ran through my stop. From the outside the setup looked fine; only the clock was broken.
Since then I check the offset against a public time server every morning, and I force a sync after any VPS restart. On that box drift used to reach four or five seconds over a quiet weekend on the default schedule. More frequent sync removed the late and early triggers.
Log timestamps matter too. When local stamps disagreed with broker history by a few seconds, reviewing fills against news times became guesswork. Aligning the clock first made those reviews trustworthy again, and I treat clock health as part of the pre-trade checklist.
Since then I check the offset against a public time server every morning, and I force a sync after any VPS restart. On that box drift used to reach four or five seconds over a quiet weekend on the default schedule. More frequent sync removed the late and early triggers.
Log timestamps matter too. When local stamps disagreed with broker history by a few seconds, reviewing fills against news times became guesswork. Aligning the clock first made those reviews trustworthy again, and I treat clock health as part of the pre-trade checklist.