On October 15, 2026, at its 28th meeting, the General Conference on Weights and Measures (CGPM)—the policy-making body of the International Bureau of Weights and Measures (BIPM)—adopted Resolution 5, formally titled "On the technical actions needed to ensure the continuity of UTC." The resolution accelerates the retirement of the leap second, moving the deadline up from the previously planned "in, or before, 2035" timeframe (established by CGPM Resolution 4 in 2022) to a firm effective date of May 20, 2027. From that date forward, Coordinated Universal Time (UTC) will operate as a continuous time scale without single-second steps.
Why Earth and Atomic Clocks Stopped Getting Along
To understand why a single second can cause such a massive headache for IT infrastructure, you have to look at how humanity measures time. As confirmed in earlier CGPM resolutions, UTC is produced by the BIPM at the exact same rate as International Atomic Time (TAI), differing from TAI only by an integral number of seconds. UTC serves as the sole recommended time scale for international reference and forms the basis of civil time across most of the globe.
However, the physical Earth is a far less reliable timekeeper than a rack of cesium and rubidium clocks. The time scale describing the angular rotation of the Earth—known as UT1—fluctuates constantly due to forces exerted by the planet's core, oceans, atmosphere, and the gravitational pull of the Moon.
Since 1972, timekeepers have bridged the gap between atomic precision (UTC) and solar reality (UT1) by occasionally inserting a "positive" leap second. In all, 27 positive leap seconds have been added since 1972. During the most recent adjustment on December 31, 2016, properly configured clocks ticked to 23:59:60 before rolling over to 00:00:00 on January 1, 2017. Because Earth's rotational variations are unpredictable, leap seconds cannot be pre-programmed decades in advance like leap years. Systems must wait for operational announcements from the International Earth Rotation and Reference Systems Service (IERS) and handle the irregular 61-second minute gracefully.
Section Summary:
- UTC vs. TAI: UTC ticks at the exact rate of International Atomic Time (TAI) and is the international standard for civil time.
- The UT1 Problem: Earth's physical rotation (UT1) is irregular due to geological, atmospheric, and lunar forces.
- Historical Fixes: Since 1972, 27 positive leap seconds have been inserted to keep UTC closely tied to UT1, with the last occurring at the end of 2016.
The Y2K-Scale Threat of a "Negative" Leap Second
If systems have survived 27 positive leap seconds, why did the CGPM suddenly rush the retirement date forward by eight years to May 2027? The answer lies in an accelerating planet and the terrifying prospect of a 59-second minute.
In March 2025, a workshop organized by the Consultative Committee for Time and Frequency (CCTF) and the IERS brought together experts on Earth rotation. Their findings, cited directly in the 28th CGPM's Resolution 5, estimated that the probability of needing a "negative leap second" will increase rapidly in the near future, reaching a 30% probability by 2035.
While a positive leap second adds an extra tick (23:59:60), a negative leap second deletes one, jumping directly from 23:59:58 to 00:00:00. As the CGPM resolution notes, a negative leap second has never been applied in history. It is considered to pose a high risk of causing anomalies and severe disruption to critical infrastructures that are largely unprepared to see a second simply vanish.
In fact, the CGPM noted that preparing time-synchronized industries for a negative leap second would require a financial investment estimated to be on par with preparations for the Y2K millennium bug. Rather than forcing the global economy to spend billions auditing legacy code and replacing hardware for a 59-second edge case, international standards bodies—backed by formal statements from the ITU Telecommunication Standardization Sector (ITU-T), the International Union of Radio Science (URSI), the IEEE 1588 working group, and tech companies including Microsoft, Google, Meta, and Amazon—pushed to make UTC continuous well before the danger window opens.
Section Summary:
- Rising Risk: A March 2025 CCTF and IERS workshop estimated a 30% chance of needing a negative leap second by 2035.
- Untested Territory: A negative leap second (a 59-second minute) has never been tested in live global production.
- Massive Cost: The CGPM compared the potential financial cost of preparing infrastructure for a negative leap second to the Y2K millennium bug effort.
A "Continuous UTC" vs. The "Leap Hour" Headline
While reporting from outlets including Tom's Hardware, The Guardian, and Nature has popularized the idea that the leap second is being replaced by a "leap hour," Enterprise IT architects should read the actual regulatory text carefully.
Resolution 5 of the 28th CGPM does not schedule a future "leap hour" event or establish a procedure for jumping clocks by 60 minutes. Instead, it establishes two concrete rules:
- Continuous UTC becomes effective on May 20, 2027.
- The maximum permitted value for the difference between Earth rotation time and atomic civil time—expressed as
|UT1 - UTC|—is increased to 3,600 seconds (1 hour).
By widening the allowable tolerance from less than a second to a full hour, the CGPM ensures that UTC can run continuously without any adjustments "for several centuries". As The Guardian noted, the drift is slow enough that reaching a full one-hour gap would likely take thousands of years.
Why define a 3,600-second ceiling at all if nobody alive today will ever see it reached? The CGPM explicitly noted that software designers need a fixed, known maximum value for |UT1 - UTC| to appropriately design the software underlying operational systems. Furthermore, for anyone concerned that civil noon might eventually drift a few minutes away from solar noon, the CGPM pointed out a simple reality: in many countries, civil time already differs from local apparent solar time by more than an hour due to time-zone boundaries, and one-hour shifts are routinely introduced twice a year wherever daylight-saving time is observed.
| Metric / Rule | Legacy System (1972 – May 19, 2027) | New Continuous UTC (Effective May 20, 2027) |
|---|---|---|
| Adjustment Mechanism | Irregular positive (or theoretical negative) leap seconds | Continuous time scale; no leap-second adjustments |
Maximum \|UT1 - UTC\| Tolerance | Kept within ~1 second via IERS announcements | 3,600 seconds (1 hour) |
| Expected Continuity | Adjusted every few years as needed | Continuous for several centuries |
| Primary Risk to IT | Outages from 61-second/59-second minutes and mismatched time-smearing | Eliminated; consistent 60-second minutes guaranteed |
Section Summary:
- The Exact Rule: The CGPM did not schedule a leap hour; it raised the maximum allowable
|UT1 - UTC|drift to 3,600 seconds (1 hour). - Software Design: Fixing a strict 3,600-second bound gives systems engineers a defined constant for operational software design.
- Long-Term Stability: This tolerance guarantees continuous, unadjusted UTC for several centuries.
Why System Administrators and Cloud Architects Are Cheering
For the average desktop PC user, Tom's Hardware points out that a leap second is barely a blip, provided the operating system's Time Service server is properly updated. In the Windows ecosystem, the Windows Time service (W32Time) and modern Network Time Protocol (NTP) clients have evolved over the years to absorb positive leap seconds relatively quietly.
In the data center and across critical infrastructure, however, leap seconds have historically been a minefield. When a positive leap second was inserted in 2012, it famously triggered crashes and outages at major platforms including Reddit, LinkedIn, Foursquare, and Yelp, and even delayed Qantas airline flights. The Linux kernel and Java subsystems at the time struggled with unexpected time jumps, leading to CPU spikes and livelocks.
Even when tech giants engineered workarounds, the workarounds themselves created a new problem. To avoid sudden one-second steps in log files and database transactions, global cloud and service providers developed "leap smearing"—slowly stretching or compressing the length of a second over a 12- or 24-hour window. As the CGPM resolution highlights, the use of different mitigation methods by different global service providers leads to timing inconsistencies between systems and disseminated frequencies that do not actually conform to the International System of Units (SI). If one cloud provider smears time over 24 hours while a trading partner steps the clock at midnight, high-frequency financial logs, IEEE 1588 Precision Time Protocol (PTP) networks, and distributed multi-sensor systems fall out of sync.
The CGPM also cited two other major drivers for accelerating the transition:
- Modern Distributed Tech: The rapid growth of Internet of Things (IoT) technologies, dispersed multi-sensor systems, smart grids, and virtual services has drastically multiplied the number of endpoints that could malfunction during a leap second, alongside national critical infrastructure in transportation, energy distribution, telecommunications, and space projects.
- Preventing Time-Scale Fragmentation: The CGPM warned that delaying the move to continuous UTC risked pushing user organizations to abandon UTC altogether in favor of unadjusted time scales—such as Global Navigation Satellite Services (GNSS/GPS) time—which would seriously compromise international standardization in metrology.
What Happens to Systems That Still Need Earth-Rotation Time?
Retiring the leap second solves a massive headache for Windows Server admins, Linux maintainers, and network engineers, who can now rely on every minute containing exactly 60 seconds starting May 20, 2027. However, astronomers, geodesists, satellite operators, and space agencies still need to know the exact orientation of the physical Earth (UT1).
Resolution 5 addresses this transition directly. Users who require UT1 can retrieve the exact UT1 - UTC offset value through GNSS navigation messages and via internet services maintained by the IERS, National Metrology Institutes (NMIs), and related organizations. Additionally, because legacy radio time-signal stations transmit a coded UT1 - UTC offset with limited bit range, the ITU Radiocommunication Sector (ITU-R) Working Party 7A is studying updates to the transmission code. Under ITU Resolution 655 (REV.WRC-23), a transition period allows radiocommunication systems to disseminate the increased difference until 2035—and no later than 2040—to accommodate legacy radio equipment that cannot be replaced immediately.
For the rest of the IT world, the October 2026 CGPM vote is a rare and welcome victory for simplicity. By locking in continuous UTC starting May 20, 2027, the international metrology community has diffused a Y2K-scale time bomb years before it could detonate in our servers.