Continuous UTC to End Leap Seconds
CGPM Resolution 5 makes UTC continuous from 20 May 2027, allowing the UT1–UTC gap to reach one hour and eliminating future leap-second insertions or skips. The change targets software and infrastructure failures caused by discontinuous clocks.
This is a deceptively important infrastructure change: distributed systems will no longer need to handle 59- or 61-second minutes, but migration work remains across time libraries and synchronization tooling.
- –Cloudflare’s 2017 DNS outage showed how leap-second assumptions can crash production systems.
- –Developers should audit NTP, PTP, GNSS, timestamp expiry, and POSIX-versus-leap-second handling.
- –Monotonic clocks remain essential for measuring durations; continuous UTC does not make wall clocks safe for elapsed-time logic.
- –IANA leap-second data, time-signal formats, schedulers, observability systems, and distributed databases will need updates.
- –AI infrastructure benefits from more predictable timestamps for job scheduling, retries, logging, and event ordering.
DISCOVERED
1h ago
2026-10-18
PUBLISHED
1h ago
2026-10-18
RELEVANCE
AUTHOR
Better Stack