← Retour au blog
tech 7 May 2026

How an HTTP Header Caused time.gov to Skew from UTC

Learn how a simple HTTP header disrupted time.gov's accuracy, causing it to skew from UTC, and how NIST addressed this issue.

Article inspired by the original source
How an HTTP header caused time.gov to skew from UTC ↗ alexsci.com

Introduction

Time accuracy is crucial for many applications, from meteorology to financial transactions and GPS systems. In the United States, the National Institute of Standards and Technology (NIST) is responsible for disseminating the official time, including via its website time.gov. However, an unexpected issue arose: an HTTP header caused time.gov to skew from UTC.

The Identified Problem

During a project requiring a reliable time source, Robert Alexander discovered that time.gov displayed clock estimates that did not match other sources, such as an NTP client. This discrepancy was significant enough to question time.gov's reliability for sensitive applications.

Understanding the NTP Protocol

The Network Time Protocol (NTP) is a commonly used method for synchronizing clocks over a network. To simplify, an NTP server returns a current timestamp when a request is received. The client must estimate the time elapsed since the timestamp was generated by measuring the request's round-trip time (RTT). This calculation allows adjusting the timestamp to obtain an accurate estimate of the current time.

The Impact of an HTTP Header

The issue lay in how time.gov handled HTTP requests. A specific HTTP header, likely related to caching or delay management, disrupted the RTT calculation, leading to poor synchronization with UTC. This skew was observed when time.gov was opened in multiple browser windows side by side, revealing significant discrepancies.

NIST's Solution

To resolve this issue, NIST adjusted how time.gov managed these problematic HTTP headers. By refining the RTT calculation and ensuring that HTTP headers did not introduce additional latency, they successfully restored the site's clock accuracy.

Implications and Lessons Learned

This situation highlights the importance of testing and verifying the accuracy of time sources, especially when integrated into critical systems. A simple HTTP header, if not properly managed, can have a disproportionate impact on time synchronization.

Conclusion

Ensuring time accuracy is a complex task that requires meticulous attention to details, including seemingly insignificant elements like HTTP headers. For your projects requiring precise synchronization, understanding these subtleties is crucial to avoid costly errors.

Let's discuss your project in 15 minutes.

HTTP header time synchronization NTP protocol time.gov UTC
Deepthix newsletter · 100% AI · every Monday 8am

An AI agent reads tech for you.

Our AI agent scans ~200 sources per week and ships the best articles to your inbox Monday 8am. Free. One click to unsubscribe.

Visit the newsletter page →

Want to automate your operations?

Let's talk about your project in 15 minutes.

Book a call