Global Timekeepers May Abolish Leap Seconds to Avert IT Infrastructure Risks

The General Conference on Weights and Measures (CGPM) is preparing to vote on a radical overhaul of Coordinated Universal Time (UTC) to eliminate the disruptive practice of leap second insertions. The move comes as Earth's accelerating rotation increases the likelihood of a negative leap second, an event that could trigger widespread failures across global digital infrastructure.

According to TechTimes, the CGPM is expected to vote in October 2026 on a resolution—specifically Draft Resolution C—to stop the insertion of leap seconds. This urgency is driven by the fact that Earth's rotation speed reached record highs in 2024 and 2025. These shorter days have increased the probability that timekeepers will need to implement a negative leap second, which involves removing a second from the clock to keep UTC aligned with the planet's actual rotation.

The Legacy of Clock Drift

Since 1972, 27 leap seconds have been added to UTC to maintain synchronization with UT1, the time based on Earth's rotation. While these adjustments have historically been positive, they have become a persistent liability for the tech industry. Leap seconds are notorious for causing software bugs and system crashes, particularly within distributed computing environments where precise synchronization is critical.

Until now, every leap second has been an addition. However, the recent speed-up of the Earth's rotation has created a scenario where a second must be subtracted. A negative leap second has never been implemented in history, and it is viewed by experts as a significantly higher risk to IT infrastructure than the positive adjustments the world has already experienced.

Why the Shift Matters

For the global IT sector, the stakes are high because most existing systems are designed to either handle positive adjustments or no adjustments at all. The introduction of a negative leap second could cause unprecedented failures in critical infrastructure, as software may not know how to process a clock that skips a second backward.

By moving away from frequent, second-by-second corrections, the CGPM aims to reduce the frequency of these high-risk events. Shifting the burden from constant synchronization to a more managed approach would mitigate the risk of sudden, systemic crashes across the internet and financial markets.

What's Next

Industry observers are now looking toward the October 2026 vote to see if the leap second system will be officially retired or replaced. While some reports suggest the possibility of allowing UTC to drift significantly before performing larger, infrequent corrections, the official details of any replacement mechanism remain under deliberation. For now, the primary goal of the CGPM is to avert the technical chaos associated with the first-ever negative leap second.