December 9, 2025
Time flies, then trips
Atomic time source failure at NIST Gaithersburg campus
Internet’s clock slips 10ms—nerds panic, conspiracies bloom, backups step in
TLDR: NIST’s Gaithersburg atomic clock glitched by 10 milliseconds, triggering server shutdowns and a fast-track backup plan. Commenters split between “don’t panic, redundancy works” and geopolitics-fueled cyber-attack theories, while many joked that even tiny time slips can ripple through the apps we rely on daily.
The internet’s official timekeeper at NIST’s Gaithersburg campus tripped over itself, jumping back by about 10 milliseconds—tiny in human terms, but a mini-earthquake for systems that live by precision. One server shut itself down, another paused time service, while others kept ticking because the glitch wasn’t “bad enough” yet. A backup clock is ready, with a fix slated for Tuesday. Meanwhile, Reddit and Hacker News lit up: memes about “time travel in your toaster” mixed with real worry about how many apps and payments depend on perfectly synced clocks.
Enter the big split. Calm engineers waved charts, echoing CaliforniaKarl’s load‑balancer analogy and the idea that smart clients can spot a bad time source using a “odd-number-of-servers” trick. On the other side, the tinfoil brigade: floatin linked a Reuters story about China accusing the U.S. of cyber breaches at a national time center, hinting at spy drama. Pragmatists like octaane gave a collective exhale—there are independent backup clocks in Boulder and Ft. Collins. The mood: half “it’s a routine hiccup,” half “who’s messing with time?” Either way, the internet learned that even 10 milliseconds can spark a full‑blown clock soap opera.
Key Points
- •On Dec 6, 2025 (~21:13 UTC), the NIST Gaithersburg atomic time source failed, causing a −10 ms time step.
- •The failure involved a single cesium beam atomic clock serving all local internet time servers.
- •time-a-g shut down due to an unexplained OS issue; time-f-g suspended NTP service after detecting the time step.
- •Other Gaithersburg servers continue serving time since the offset is below automatic unhealthy thresholds.
- •A backup clock is on site; a replacement attempt is planned for Dec 9, 2025, with brief service interruptions; Boulder and WWV/Ft. Collins servers are unaffected.