How is it measured?
Every web server response carries a Date header with the current time in whole seconds, so a single reading can be off by up to a second. Minuto’s measuring server on Cloudflare sends several short HEAD requests to the site and narrows down the moment the second ticks over, which gives the offset to well under a second. It also measures the gap between that server and your device and combines the two. The ± value on screen is the largest error this method allows.
Why server clocks differ
Most servers sync with internet time (NTP), but some drift by hundreds of milliseconds or even seconds. Phone and computer clocks can be off too. Sales usually open by the seller’s server clock, so that is the clock worth watching.
Limits
- A slow or unstable connection widens the ± range.
- When a CDN caches responses, the
Dateheader can be hours old. Minuto uses a fresh address each time and throws away cached responses, but some sites may still be inaccurate. - The main site and the actual checkout or queue servers can differ. If checkout runs on another domain, try that domain.
- Knowing the server time does not guarantee a ticket. Queues and server processing order matter far more.
Using it for ticket sales
- Check the seller’s server time 5 to 10 minutes before the sale.
- Enter the target time (for example 10:00:00) and turn on the flash and beep.
- Refresh or press the button right at the target time. Pressing too early may just show a “not on sale yet” page.
- Don’t hammer the refresh button. Sites may treat it as abuse and block you or move you back in the queue.