Clock Drift Checker
A device clock that drifts quietly breaks scheduled meetings, fails 2FA one-time codes, and makes timestamps lie. This tool measures your clock against the TimeNowHub server clock and tells you, in plain language, whether it matters.
Direct Answer
A clock within a couple of seconds of real time is fine for meetings and scheduling. Once it drifts past a few seconds it starts eating into the tolerance of 2FA one-time codes; past a minute it is almost always a wrong timezone or a device that stopped auto-syncing. The measurement below is seconds-level — an honest error band of half the measured round-trip time is shown next to every offset.
Server time right now
01:08:37 UTCTue, Sep 1, 2026
Self-check your clock without JavaScript
- The value above is the server's UTC time at page render. Compare it with a UTC clock on your device.
- Within a few seconds: fine for meetings. Past ~5 seconds: 2FA one-time codes start to fail. Past a minute: check your timezone and time-sync settings.
- For a fresh, RTT-aware reading, reload this page or enable JavaScript to run the live check.
How far is your device clock from the server?
This measures one request to the server's UTC time endpoint, works out the round-trip time, and reports the offset with an honest error band. Everything runs in your browser — no account, no data sent anywhere except the request itself.
Precision is seconds-level, not milliseconds. HTTPS/CDN timing jitter and asymmetric network latency bound how tight the ±0s band can be — a low round-trip time does not remove that floor.
Why the error band exists
The check measures one request to the server's time endpoint and records the round-trip time. It assumes the response spent about half that round trip travelling back to you — the symmetric-network assumption. Real networks are asymmetric, so the true offset could sit anywhere within half the round-trip time of the estimate. That is the ±RTT/2 error band, and it is always shown next to the offset.
HTTPS/TLS and CDN edge hops add variable jitter to every request, which is why we claim seconds-level precision, never milliseconds. A low round-trip time is good, but it does not remove that floor. For authoritative time use your operating system's NTP sync; this tool tells you when that sync has drifted or stopped.
See the world clock
Live local time for every tracked city, grouped by region with UTC offsets, DST state, and business hours.
Open the world clock →How TimeNowHub computes time
Named data sources, precision limits, and the honest known limitations behind every clock on this site.
Read the methodology →Frequently Asked Questions
How precise is this check?
Seconds-level. HTTPS/CDN timing jitter and asymmetric network latency bound the accuracy, so every offset ships with an error band of half the measured round-trip time — never a false millisecond claim.
What should I do if the verdict says my clock is off?
Check that "set time automatically" is on and that your timezone is correct, then re-run the check. Drift past a minute almost always traces to a wrong timezone or a device whose time sync stopped.
Why does 2FA care about my clock?
Time-based one-time passwords (TOTP) derive codes from the current time and only tolerate a small window of drift. If your clock runs a few seconds off, the code you type can fall outside that window and be rejected as invalid.