Scientists in Versailles voted to scrap leap seconds in favor of leap hours, a structural change designed to prevent a global software crash caused by the Earth spinning faster.
For fifty years, we have relied on a tiny, one-second nudge to keep digital clocks aligned with the Earth's physical rotation. That mechanism is gone. At the General Conference on Weights and Measures in Versailles, France, a coalition of scientists and diplomats voted to kill the practice entirely. They are swapping it for a far less frequent leap hour. This fundamentally changes how Coordinated Universal Time interacts with the planet's spin, moving away from constant micro-corrections toward a system that tolerates larger drifts before acting.
The Rotation Problem
This is not a bureaucratic tweak. It is a structural overhaul of the global time standard that underpins GPS navigation and high-frequency trading. The decision follows thirty years of debate and is driven by a specific, dangerous engineering problem. The planet is spinning faster, and our current system for correcting for that speed is about to break the internet. We are no longer fighting a slow drift; we are facing a rapid acceleration that our legacy code cannot handle without catastrophic failure.
The Rotation Problem
To grasp the urgency, you must understand the mismatch between atomic time and solar time. UTC is calculated using a weighted average of atomic clocks around the world, making it incredibly precise. UT1, on the other hand, is based on the Earth's actual rotation. The Earth is a squishy, wobbling ball of rock and water, and its spin is irregular. It speeds up and slows down due to tidal forces, seismic activity, and even the redistribution of mass from melting ice sheets. This physical reality makes a perfect, unchanging second impossible to maintain against the planet itself.
The Rotation Problem
When UTC was established in 1960, scientists noticed that Earth's rotation was slowing down relative to atomic clocks. To keep the two time scales within one second of each other, they introduced the leap second in 1972. Since then, we have added 27 of these extra seconds. It was a simple patch for a slow drift. But physics is not static, and the drift has changed direction. The assumption that the Earth would always slow down was wrong, and the system now faces a reverse pressure that the original design never anticipated.

The Threat of Negative Time
In the mid-2010s, the trend reversed. Earth's spin began to speed up. This means that UTC is now running slightly slower than the actual rotation of the planet. According to Scientific American, scientists predicted that a negative leap second would be necessary soon, perhaps as early as 2029. This is the nightmare scenario for engineers. A negative leap second does not add a second to the day; it removes one. It effectively sends the entire world one second backward in time, a concept that most software simply does not know how to process.
The Threat of Negative Time
Nick Stamatakos, head of the Earth Orientation Parameters service at the International Earth Rotation and Reference Systems Service, calls this a mini Y2K event. Imagine every server in the world suddenly trying to process a timestamp that is in the past. Databases might reject the data. Transaction logs could become corrupted. The digital infrastructure that relies on strictly increasing time sequences would face a global stress test that few systems are prepared to handle, leading to widespread outages and data loss.
The Threat of Negative Time
The fear is not that the clocks would stop, but that the synchronization protocols would fail. When a system expects time to flow forward and it suddenly flows backward, the result is often a crash or a loss of data integrity. This is the primary driver for opening the window between UTC and UT1 to a much larger tolerance. By allowing more drift, we eliminate the need for the dangerous backward jump, replacing a potential catastrophe with a manageable, forward-looking adjustment.

The Leap Hour Solution
The new system replaces the one-second buffer with a one-hour buffer. Under the new rules, the difference between UTC and UT1 is allowed to grow to as much as 3,600 seconds before an adjustment is needed. When that limit is reached, a leap hour will be added or removed. This is a massive expansion of the allowed drift, but it solves the immediate engineering crisis by giving the system enough leeway to absorb the planet's variable spin without triggering a global software panic.
The Leap Hour Solution
Because the window is so much larger, the adjustments will happen much more infrequently. Instead of a leap second every few years, we might see a leap hour every few decades or even centuries. This gives software developers and system administrators plenty of time to update their code and test their systems. It turns a sudden, chaotic event into a manageable, planned maintenance task, allowing the industry to prepare methodically rather than scrambling to patch a live production environment.
The Leap Hour Solution
Noël Dimarcq, a senior scientist at the French National Center for Scientific Research and president of the BIPM's Consultative Committee for Time and Frequency, said the group is ready after thirty years of debate. The vote marks the end of an era of micro-adjustments and the beginning of a more robust, flexible time standard. It is a pragmatic admission that the old system was too brittle for the modern digital age, and that a broader tolerance is the only way to keep the lights on.

What This Means for You
For the average person, this change will be invisible. You will not see a clock skip a second, and you likely will not see a clock skip an hour in your lifetime. The impact is almost entirely in the background, in the code that keeps our global networks synchronized. However, the decision highlights a broader truth about the relationship between human technology and the physical world, showing that even our most abstract measurements are tethered to the messy reality of the planet.
What This Means for You
We built a time standard based on the vibration of atoms because it was more stable than the rotation of a planet. But we still need to account for the planet, because our lives are lived on it. The leap second was a compromise, a way to bridge the gap between the perfect, unchanging tick of an atom and the messy, changing spin of the Earth. The leap hour is a better bridge, one that is less likely to collapse under the weight of our digital dependence, ensuring that our technology remains robust against natural variability.
The Long Game
This vote is a win for pragmatic engineering. It prioritizes the stability of global systems over the purity of the time scale. It acknowledges that the Earth is not a perfect clock, and that our technology must be flexible enough to handle that imperfection. The next leap hour will not be coming for a long time, but when it does, it will be a moment that requires a conscious, coordinated effort from the global community to update their systems in unison.
The Long Game
In the meantime, we can take comfort in the fact that our clocks are safe from the immediate threat of a negative second. The world continues to spin, slightly faster than it did a decade ago, and our time standard will keep up, not with a frantic scramble of seconds, but with a slow, deliberate adjustment of hours. It is a small thing, but in the world of digital infrastructure, small things are the ones that keep us from falling into the dark, preserving the integrity of the systems we rely on every day.
Frequently asked questions

Keep subscribing to Theo BurnettHer next filing reaches you the moment it publishes, on her own subdomain.
Subscribe
