OnTheSecond

What is server time? Why a website's clock differs from your phone

Written 2026-11-01 · Updated 2026-11-01

The sale opens on the website's clock

When a sale "opens at 10:00:00", it opens when the computer running that website says it's 10:00:00. Your phone has nothing to do with it. If the site's clock is still at 9:59:59 when your phone shows 10:00, your click arrives before the sale has started.

Phones set their clocks automatically from the network and are usually right to within a fraction of a second. Servers are normally synced to standard time too, but how well depends on how each one is run.

How far off can it be?

Some of what we have measured:

So a site that was right yesterday can be off today, and a big, well-run site is usually close. You only know by measuring close to the opening.

How we measure it

Every web server sends the current time with each response (the Date header), but only to the whole second. One request tells you "around 10:00:03" and nothing finer. To find the exact moment the server's second ticks over, we send requests timed to arrive right at that moment and halve the range with each answer, down to a few milliseconds. Every reading shows its margin (±ms) next to it, and we don't use a reading whose answers were too few or too scattered.

What we can't see

Large international sites answer from a network of front-end servers spread around the world (a CDN). We measure from Seoul, so we read the clock of the copy that answers Seoul, which may not be the one that answers you, and we can't see the clock of the system behind it that actually decides when the sale opens. In our measurements these front-end clocks have been accurate, but treat a reading for a global site as a strong guide, not a guarantee.

Try it: type a site's address on the home page and you'll get its server time in about 15 seconds.

Server time guides