Time lords prepare to kick leap seconds into the next millennium
- ID
- 21935
- Status
- summarized
- Published
- 06 Sep 2026, 4:09 PM
- Fetched
- 06 Sep 2026, 4:35 PM
- Provider
- The Register
- Category
- technology
- Original URL
- https://www.theregister.com/offbeat/2026/09/06/time-lords-prepare-to-kick-leap-seconds-into-the-next-millennium/5294538
- Source URL
- https://www.theregister.com/headlines.atom
Summary
- Score
- 6.0
- Created
- 06 Sep 2026, 4:35 PM
- Tags
- Audience
- developersdatabase_learnerssaas_founders
What happened
The General Conference on Weights and Measures will vote in October on a draft resolution making UTC continuous from May 20, 2027, and allowing it to drift up to one hour from Earth-rotation-based UT1. The push is driven by a 30% estimated probability that a never-before-attempted negative leap second would be needed by 2035, which most digital architectures and network time servers are not designed to handle since they assume leap seconds are strictly additive.
Why it matters
If the resolution passes, you can stop engineering leap-second accommodation into new time-handling, logging, and database synchronization code after May 2027. Until then, the real risk is a negative leap second that could break telecom, grid, and GNSS systems hardcoded for additive-only adjustments—worth a check if you maintain NTP infrastructure or distributed timestamp logic.
Discussion angle
What does your current stack actually do with leap seconds today—smearing, ignoring, or crashing—and would a negative leap second expose a hidden assumption in your timestamp ordering or monotonic clock code?