Clock drift: the computer's time is off and the logs prove it
Posted: Sat Oct 31, 2026 11:42 pm
A PC clock that runs even half a second off can quietly mess up a scalper's records, signals, and news timing.
The effect shows up in several places. A strategy triggered at "8:30:00" on the local clock fires half a second early or late relative to the broker's server. Execution logs compare the local send time to the server's confirmation time and produce nonsense, such as fills that appear to happen before the order was sent. News-based entries meant to wait a certain number of seconds after the release use the wrong baseline.
Windows syncs its clock only occasionally by default, and virtual machines can drift noticeably, especially under load.
The remedy is easy. Use a proper time synchronization tool that checks against a reliable source frequently, and verify the offset between the PC and the broker's server time. Many platforms display server time in the market watch window or status bar.
Once time is aligned, execution analysis becomes meaningful. Latency numbers computed from synchronized clocks can be trusted, and weird results disappear.
How far apart are the PC clock and the broker's server time right now?
The effect shows up in several places. A strategy triggered at "8:30:00" on the local clock fires half a second early or late relative to the broker's server. Execution logs compare the local send time to the server's confirmation time and produce nonsense, such as fills that appear to happen before the order was sent. News-based entries meant to wait a certain number of seconds after the release use the wrong baseline.
Windows syncs its clock only occasionally by default, and virtual machines can drift noticeably, especially under load.
The remedy is easy. Use a proper time synchronization tool that checks against a reliable source frequently, and verify the offset between the PC and the broker's server time. Many platforms display server time in the market watch window or status bar.
Once time is aligned, execution analysis becomes meaningful. Latency numbers computed from synchronized clocks can be trusted, and weird results disappear.
How far apart are the PC clock and the broker's server time right now?