Leap seconds stop on May 20, 2027, ending a 1972 compromise whose failures networks never fully learned to handle. The event goes away. The files, offsets and smears built around it stay unless someone decides what happens to them.
The leap-seconds.list file distributed with the IANA time zone database carries a line that will soon look odd: “File expires on 28 June 2027.” That is five weeks after UTC stops taking leap seconds. Unless the file is reissued, ntpd 4.2.8 and later will log it as expired and stop using it, even though the offset it records, 37 seconds between TAI and UTC, is not expected to change for centuries.
A 1972 fix for the gap between clocks and the planet
Leap seconds exist because atomic clocks keep steadier time than Earth’s rotation. From 1972, UTC ran at the atomic rate and was stepped by a whole second whenever its difference from UT1, the time scale tied to the planet’s rotation, approached 0.9 seconds. UT1 is what celestial navigation needs, and keeping civil time close to it preserved that link. NIST notes that the earlier adjustment scheme had already accumulated 10 seconds by the time leap seconds started.
Twenty-seven positive leap seconds followed, the last at the end of December 2016. Each one inserted a 61st second, 23:59:60, into a minute that most software assumes has 60. Systems that never adjusted kept their own fixed offsets. GPS time, for example, is not adjusted for leap seconds and runs 18 seconds ahead of UTC, according to the U.S. Naval Observatory.
A code path that ran once every few years
Leap-second failures came from rarity: the code handling the event ran so seldom that bugs survived between occurrences. On June 30, 2012, a Linux kernel timekeeping bug caused futex-related CPU load spikes on some systems after the leap second was inserted. Reddit, LinkedIn and Mozilla were reported among those hit, and the Amadeus reservation system used by Qantas and Virgin Australia was down for about an hour while staff checked passengers in by hand.
On Jan. 1, 2017, the problem moved to application code. Cloudflare’s DNS software measured upstream response times with wall-clock time. When the clock stepped back during the leap second, a measured duration went negative, and a Go random-number call that cannot accept a negative argument panicked. At peak, about 0.2% of Cloudflare’s DNS queries were affected, all for sites using CNAME records, over nearly seven hours.
A negative leap second, deleting 23:59:59, would have exercised code that had never run in production. The 2022 General Conference on Weights and Measures (CGPM) described its insertion as something that had “never been foreseen or tested.” The prospect was not abstract: geophysicist Duncan Agnew calculated in Nature in 2024 that UTC as defined would need a negative discontinuity by 2029.
Smearing traded one failure mode for another
Large operators responded by hiding the event. Google recommends a 24-hour linear smear from noon to noon UTC, adjusting clock rate by about 11.6 ppm; AWS smears on its Time Sync Service. Meta used a 17-hour smear. Each removes the 61-second minute, but a smeared server and an unsmeared one disagree by as much as a second, depending on the smear, while it runs. Google and AWS both advise against mixing smeared and non-smeared sources, and AWS notes that its PTP hardware clock offers no smeared option at all.
So the operational answer to leap seconds became a set of local conventions: which upstream servers smear, which clients may use them, which leap file each daemon reads and which devices carry a manually entered offset. Those conventions are now in production networks, many of them undocumented.
What the CGPM decided in October
Resolution 5 of the 28th CGPM, adopted in October 2026, makes UTC continuous from May 20, 2027, and lets the difference between UT1 and UTC grow to 3,600 seconds. The resolution cites estimates that the probability of a first negative leap second will reach 30% by 2035. It also cites Resolution 655 of the ITU’s 2023 World Radiocommunication Conference, which allows radio time-signal services until 2035 to disseminate the larger UT1-UTC difference, extendable to 2040 where existing equipment cannot be replaced earlier.
For network protocols, the change is quiet. Cisco’s timing engineers write that continuous UTC requires no changes to PTP message formats or the NTP protocol, and that existing leap-second signaling “will no longer be invoked to adjust UTC.” IERS Bulletin C 72 announced no leap second for the end of December 2026, and continuous UTC begins before the next scheduled opportunity at the end of June 2027. Unless that schedule changes, December 2016 was the last leap second. Because the protocols do not change, the transition itself does not require new switches, routers or grandmaster clocks.
What is left to clean up
The leftover risk sits in the workarounds rather than the protocols. Start with leap files. The tz database maintainer, Paul Eggert, wrote on Oct. 15 that he had contacted the IERS and expects the file’s expiry date to be dropped or pushed far into the future. Until a reissued file reaches the servers and appliances that read one, plan for expiry warnings in June 2027 and decide whether they page anyone. Where a system relies on that file for its TAI offset, check what it does once the file is rejected; a missing offset is easier to overlook than a wrong one.
Next, freeze the offsets deliberately. TAI minus UTC stays at 37 seconds and GPS minus UTC at 18 seconds, and Resolution 5 is designed to keep it that way for several centuries. PTP grandmasters, GNSS receivers and any device with a manually configured UTC offset should be checked once against those values, because no future leap second will expose a wrong one, and a wrong one will persist silently in timestamps and logs.
Then decide what to do with smearing. After May 2027, a smear configuration is inert, because no leap event will trigger it. It is not worth a change window to remove, but it should be documented as dormant, so that a future engineer does not treat mixed smeared and unsmeared sources as an active fault. Remaining leap indicators matter too: a server that wrongly announces a leap second can still trigger handling in clients that honor it. Multiple independent upstream sources, already a requirement for time that authentication depends on, limit what one bad announcement can do.
Retiring the last second on purpose
The rarity that made leap-second code fragile now applies to the workarounds: leap files, frozen offsets and smears will be touched rarely and understood by fewer people each year. A one-time review before June 2027, recorded where the next team will find it, costs little. It also avoids rediscovering, a decade from now, why one appliance’s clock disagrees with the rest by exactly 37 seconds.
Sources
- BIPM: Resolution 5 of the 28th CGPM on the continuity of UTC
- BIPM: Resolution 4 of the 27th CGPM on the future of UTC
- NIST: Leap seconds FAQ
- U.S. Naval Observatory: GPS time and leap seconds
- U.S. Naval Observatory: No leap second at the end of December 2026
- IANA tz database: leap-seconds.list and its expiry date
- Meinberg: How ntpd handles an expired leap second file
- tz mailing list: Paul Eggert on leap-seconds.list after the CGPM decision
- LWN: Linux kernel fix for the 2012 leap second futex spikes
- The Register: 2012 leap second disruption at Amadeus and websites
- Cloudflare: How the 2016 leap second affected its DNS
- Nature: Agnew, A global timekeeping problem postponed by global warming
- Google: Leap smear
- Google: Public NTP FAQ on mixing smeared and non-smeared servers
- AWS: Amazon Time Sync Service and leap second smearing
- Meta: It’s time to leave the leap second in the past
- Cisco: Continuous UTC implications for timing and synchronization equipment
About NetworkTigers

NetworkTigers is the leader in the secondary market for Grade A, seller-refurbished networking equipment. Founded in January 1996 as Andover Consulting Group, the company originally built and re-architected data centers for Fortune 500 firms. Today, NetworkTigers provides consulting and network equipment to global government agencies, Fortune 2000 companies, and healthcare companies. Visit www.networktigers.com
