Why Your Computer Clock Is Probably Wrong Right Now
Your computer, phone, and watch all drift. Even with NTP syncing in the background, your clock is almost certainly off by some amount right now. Here is why — and how much it actually matters.
A Quiet Little Lie Running on Every Device You Own
Right now, the clock on your computer, your phone, your tablet, your smartwatch, and even the microwave in your kitchen is lying to you. Not by hours. Probably not even by minutes. But it is almost certainly wrong by some amount — a few hundred milliseconds here, a second or two there, sometimes more. You have probably never noticed, because for most of what you do in a day, the lie does not matter. But the lie is there, quietly ticking along, in every device you own. The reason is not that your hardware is broken. It is that keeping a clock perfectly accurate is one of the hardest engineering problems in the world, and the "good enough" solution that ships in consumer devices is... well, good enough. Most of the time. This article is about why your clock drifts, how much it drifts, and what you can actually do about it when "most of the time" is not good enough for you.
How Computer Clocks Actually Work
At the heart of almost every digital device is a tiny crystal of quartz. When you apply a small voltage to quartz, it vibrates at an extremely stable frequency — typically 32,768 times per second in a consumer device. The computer counts those vibrations and uses them to mark the passage of time. This is the same principle that drove mechanical wristwatches for decades, and for good reason: quartz is cheap, reliable, and accurate enough for everyday use. But "accurate enough" is a sliding scale. A typical consumer-grade quartz oscillator is rated for about 20 parts per million (ppm) of drift. That sounds impossibly precise — until you do the math. Twenty parts per million works out to about 1.7 seconds per day, or roughly one minute per month, of drift. And that is under perfectly ideal conditions.
Why the Drift Is Usually Worse Than the Spec
In the real world, your clock drifts more than the datasheet suggests. Temperature is the biggest culprit: a quartz crystal vibrates at slightly different frequencies when it is hot versus cold. The inside of a running laptop can swing from room temperature to over 60°C in minutes, which warps the crystal just enough to change the tick rate. Age also matters — crystals drift more as they get older, a phenomenon called "aging." Supply voltage, mechanical stress, and even atmospheric pressure contribute small errors. Add it all up, and a typical consumer device can drift anywhere from a few hundred milliseconds to several seconds per day without any help. Over a week of uninterrupted running, you could easily be 10–30 seconds off. Over a month without sync, you could be off by more than a minute.
"But My Computer Syncs Automatically"
Yes, it does. That is the reason your clock has not drifted into meaninglessness — your operating system periodically reaches out to a time server over the internet and corrects itself. This process uses a protocol called NTP (Network Time Protocol), which has been quietly running the internet's timekeeping infrastructure since 1985. On Windows, the time service typically syncs once a week by default. On macOS and Linux, it syncs more frequently, usually every few minutes to a few hours. On phones, the cellular network provides an additional time reference. All of this works well — most of the time. But "periodic sync" is not the same as "always accurate." In between syncs, your clock is drifting freely. And the sync process itself is not instantaneous — it carries its own small errors, which we will get to in a moment.
The Network Itself Is a Source of Error
Here is the twist: even when your computer is actively syncing with a time server, the sync is not perfect. The problem is that the time server is somewhere else on the internet, and the signal has to travel from there to you over a chain of routers and cables that introduce variable delay. If the server's time traveled to you instantly, your clock would be perfectly correct. But it does not. It takes anywhere from 10 to 200 milliseconds to arrive, and that round-trip time is not always symmetric — the path going out may take longer than the path coming back, and neither path is consistent from one request to the next. NTP is clever about this: it measures the round-trip time and estimates the true server time at the midpoint of that round-trip. That estimate is good, but it is still an estimate. For a typical home internet connection, the residual error after an NTP sync is somewhere between 10 and 100 milliseconds. For a mobile device on a cellular network, it can be worse.
So How Wrong Is Your Clock, Really?
Let us put some realistic numbers on it. A well-maintained computer that syncs frequently and has a stable network connection is typically within about 50–200 milliseconds of true time. A computer that has not synced recently — say, it has been running for a few days without a sync — can easily be 1–5 seconds off. A phone that just came out of airplane mode might be several seconds off for a few moments before it catches up. A laptop that was suspended for a week and then woken up is almost certainly wrong by at least a few seconds, sometimes much more. And if you have ever opened a device that had its battery die and come back to life with the wrong date, you already know how bad it can get in the extreme case. For everyday use — checking email, browsing the web, streaming videos — none of this matters. For things that actually depend on precise time, it very much does.
When a Wrong Clock Actually Hurts You
Most of the time, a clock that is 200 milliseconds off is invisible to you. But there are situations where even small errors cause real problems. Online auction snipes are won or lost in milliseconds — if your clock is fast, your "last-second" bid may actually be placed after the auction closes. Flash sales and limited-release product drops run on server time; if your clock is behind, you think you are clicking early when you are really clicking late. Video game competitive ladders and speedrun leaderboards rely on accurate timestamps. Financial traders who place orders manually can miss their intended prices if their quote timestamps are off. Software developers debugging distributed systems can chase phantom bugs when server logs from different machines have slightly different clocks. And then there are the situations where the cost of a wrong clock is not measured in money at all: you miscalculate a meeting start time, you join a live event a minute late, or you simply lose trust in the device in your pocket.
Authentication and Security Also Depend on Time
There is one more reason an inaccurate clock can bite you: modern authentication systems rely on time. Two-factor authentication codes from apps like Google Authenticator or Authy are generated from a shared secret and the current time, which means if your phone's clock is off by more than 30 seconds, the codes it generates will not match what the server expects. Kerberos, the authentication protocol used in many corporate networks, rejects requests where the client and server clocks disagree by more than a few minutes. HTTPS certificates have validity windows that must fall between two timestamps, and a badly wrong clock can make all secure websites appear broken. These systems are designed with some tolerance, but that tolerance is not infinite. A clock that drifts too far can silently lock you out of your own accounts.
How to Check If Your Clock Is Actually Right
The simple way to check your clock is to compare it against a source you trust. You cannot compare it against another clock on the same device, because all of those clocks share the same underlying hardware — they will all agree with each other even if they are all wrong. You need an external reference. Clockzilla does this for you automatically: when you open the site, it synchronizes against NTP-referenced time servers and displays the exact offset between your device and true time. If the offset is near zero, your clock is fine. If it is a few hundred milliseconds, your clock is slightly off but normal. If it is several seconds or more, something has gone wrong with your system's sync — usually that the service is disabled, the network is flaky, or the device just woke from sleep. Checking your clock this way takes about two seconds and requires nothing more than opening a web browser.
How Clockzilla Measures Your Clock Drift
When you visit Clockzilla, we do not just display time from your local computer — that would be pointless, because your local clock is exactly the thing we are trying to check. Instead, our engine sends multiple timing requests through our backend proxy to NTP-referenced time sources. For each request, we record the precise local timestamp just before the request leaves your browser and just after the response arrives. The difference between those two timestamps gives us the round-trip time (RTT). We estimate the true server time at the midpoint of that RTT, compute the offset between that estimated true time and your local clock, and repeat the process multiple times to collect a statistical sample. Then we throw out outliers using Median Absolute Deviation, weight the remaining samples by how fast their round-trips were (shorter round-trips are more accurate), and present you with a final offset measurement. That number is the best available estimate of how wrong your local clock actually is. In most cases, we can tell you your drift with a precision of a few tens of milliseconds.
How to Fix a Wrong Clock
If Clockzilla shows you are off by more than a few hundred milliseconds, the good news is that fixing it is usually easy. On Windows, open Settings → Time & Language → Date & Time, make sure "Set time automatically" is on, and click "Sync now." On macOS, open System Settings → General → Date & Time and ensure "Set time and date automatically" is enabled. On Linux, the timedatectl command can turn on NTP syncing (sudo timedatectl set-ntp true). On most phones, the time is automatically set by your cellular network, so simply toggling airplane mode off and on will often resync it. If you want to go further, you can point your operating system at a more aggressive NTP server pool — servers in the pool.ntp.org network are free, reliable, and used by millions of devices worldwide. For almost all users, enabling automatic sync is all you need. For the small number of users who need guaranteed accuracy, dedicated tools and hardware exist, but they are overkill for daily life.
The Bigger Picture: Trust Your Tools
It is easy to assume that the clock on your screen is correct, because it has always more or less been correct. But the clock is not magic. It is a quartz crystal and a piece of networking code doing their best to approximate an abstract quantity called "true time," which is itself defined by a network of atomic clocks scattered around the world. That approximation is usually fine. Sometimes it is not. And the reason Clockzilla exists is to give you a quick, honest answer to the question: "Is my clock lying to me right now?" Because your life revolves around the accuracy of time. Because every schedule, every deadline, every meeting, every deadline-driven moment depends on the clock being right. And because when the clock is wrong, the fix is usually simple — you just have to know that it is wrong in the first place.
Check Your Clock Now
If you are curious how accurate your own device is right now, open Clockzilla in this browser. The sync status badge in the header will tell you, within seconds, exactly how many milliseconds your clock is off from true time. Most users see "Excellent" (under 50ms). Some see "Good" (under 500ms). A surprising number of people discover their clock is off by much more than they expected — usually because automatic sync got disabled at some point and nobody noticed. Checking takes no account, no install, no fee. Just open the page, glance at the badge, and you will know. That is, in the end, the whole point: knowing where you stand. Time is too important to trust blindly, and Clockzilla is here to help you stop trusting it blindly.
Try Clockzilla Free
Accurate world time for 150,000+ cities with timezone converter, sunrise/sunset calculator, stopwatch, Pomodoro timer, and more.
Open Clockzilla →