Since 1972, humanity has paused its clocks twenty-seven times to keep the precision of atomic time tethered to the imprecision of a spinning planet. This week, delegates meeting near Versailles are expected to sever that tether — accepting a slow, centuries-long drift between our machines and the Earth beneath us, to be corrected only once, far in a future none of us will see. It is a quiet but profound admission: that the clocks we built have outgrown the world that inspired them.
Global timekeepers vote to ditch leap second, replacing it with future 'leap hour'
Clocks themselves are a very artificial thing.
So leap seconds have been around since 1972, and we're only now deciding to get rid of them? What changed?
Earth started spinning faster around 2020. That meant we might need a negative leap second—time jumping forward instead of backward. It's never happened before, and nobody knows if software can handle it.
Right, but that's the risk we're trying to avoid. The real problem is that leap seconds have always been disruptive to computer systems. This acceleration just made the decision urgent.
How often do we actually add leap seconds?
Twenty-seven times since 1972. The last one was at the end of 2016. They're irregular—scheduled only six months in advance—which makes it hard for software engineers to prepare.
And when they do happen, systems crash. Cloudflare, Reddit. But I'd note that most systems probably handle them fine. It's the ones that don't that make headlines.
So what's the replacement?
A "leap hour" system. UTC will gradually drift from Earth's rotation until they're an hour apart, then we'll add a leap hour to sync them again. But that won't happen for over a thousand years.
Which is the whole point—by then, our current systems will be completely different. We're essentially kicking the problem so far into the future that it becomes someone else's problem.
Is there any argument for keeping leap seconds?
Some people say it keeps our timekeeping connected to Earth's actual rotation. There's something philosophically important about that connection.
But the counterargument is that clocks are artificial anyway. They're tools we built to serve our needs, not the other way around. And right now, they need to be stable more than they need to be philosophically pure.
Der Puls
- Earth's recent acceleration since 2020 has pushed the leap second system toward a breaking point — a negative leap second, never before attempted, could trigger cascading software failures across global infrastructure.
- Every leap second inserted into UTC has been a small crisis for the digital world, crashing platforms like Cloudflare and Reddit because software was never designed to experience time moving backward.
- Delegates from international timekeeping bodies are gathering near Versailles this week to formalize a 2022 decision: retire leap seconds entirely by 2035, before the unprecedented negative version can cause real damage.
- The replacement plan is almost philosophical in its patience — let UTC drift freely from Earth's rotation for a millennium, then correct it with a single 'leap hour' when today's vulnerable systems are long obsolete.
Since 1972, humanity has paused its clocks twenty-seven times to keep the precision of atomic time tethered to the imprecision of a spinning planet. This week, delegates meeting near Versailles are expected to sever that tether — accepting a slow, centuries-long drift between our machines and the Earth beneath us, to be corrected only once, far in a future none of us will see. It is a quiet but profound admission: that the clocks we built have outgrown the world that inspired them.
Twenty-seven times since 1972, the world's clocks have paused for a single second. These leap seconds were never meant to be permanent — they were a patch, a way of keeping atomic time aligned with the Earth's actual, imperfect rotation. This week, delegates near Versailles will almost certainly vote to end the practice for good.
The tension at the heart of the issue is a mismatch between two ways of measuring time. Earth doesn't spin like clockwork — it speeds up and slows down depending on atmospheric conditions, ocean currents, and the Moon's gravitational pull. In the 1960s, scientists adopted a far more stable definition of a second, based on the vibrations of caesium atoms. That atomic second became the foundation of UTC, the standard underpinning GPS, financial systems, and the internet. To keep UTC and Earth's rotation from drifting apart, timekeepers began inserting leap seconds whenever the gap grew too wide.
For decades this seemed workable. Then the digital age revealed a deeper problem: software assumes time only moves forward. When a leap second arrived, systems crashed. Cloudflare went down. Reddit went down. The unpredictability made it worse — leap seconds were announced only six months in advance, unlike time zones or daylight saving, which follow known patterns.
The urgency sharpened recently because Earth has been spinning faster since 2020. The next correction might require a negative leap second — time jumping forward rather than back. This has never happened, no software has been tested for it, and the potential for cascading failures seemed too serious to risk.
The proposed solution is elegant in its patience: simply let UTC drift from Earth's rotation, year by year, until the gap reaches a full hour. Then, sometime in the next millennium, a single leap hour would restore alignment. Given that Earth loses less than a second per year, that correction is more than a thousand years away — by which point, researchers note, today's systems will almost certainly be unrecognizable.
Some see a philosophical loss in the change — a severing of our timekeeping from the planet's own rhythm. But clocks have always been human constructs, shaped to serve human needs. For the delegates voting this week, the calculation is straightforward: accept a drift that won't matter for a thousand years, or keep patching a system that breaks every few.
Twenty-seven times in the past hundred years, our clocks have stopped for a single second. That pause—a leap second—was never meant to be permanent. It was a fix, a small adjustment to keep the machines that measure time in perfect sync with the planet's actual rotation. But this week, delegates gathering near Versailles will likely vote to end the practice altogether, replacing it with something that won't matter for another thousand years or more.
The problem began with a mismatch between two different ways of measuring time. For centuries, humans defined a second as one eighty-six-thousandth of a day—a straightforward division of Earth's rotation. But Earth doesn't rotate like clockwork. Our planet spins slightly faster or slower depending on atmospheric conditions, ocean currents, melting glaciers, and the slow gravitational tug of the Moon. Over the long term, Earth's rotation is slowing. Over shorter periods, it can speed up. Since around 2020, it has been accelerating.
In the late 1960s, the International Bureau of Weights and Measures adopted a far more precise definition of a second based on the vibrations of caesium atoms. This atomic second became the foundation of Coordinated Universal Time, or UTC, the global standard that underpins GPS, financial transactions, and the internet itself. The atomic second is stable in a way Earth's rotation simply is not. But that stability came at a cost: UTC and Earth's actual day began to drift apart. To keep them tethered, timekeepers introduced the leap second. When Earth's rotation fell behind atomic time, an extra second was inserted into the clock. The first leap second arrived on June 30, 1972. The most recent came at the end of 2016.
For decades, this seemed like a reasonable compromise. But the digital age exposed a fundamental problem: software was not built to handle time moving backwards. Leap seconds broke assumptions that programmers had baked into their code—that time only moves forward, that a minute always contains sixty seconds. When a leap second was inserted, systems crashed. Cloudflare went down. Reddit went down. The irregularity of leap seconds made the problem worse; they were scheduled only six months in advance, giving engineers little time to prepare. Unlike daylight saving time or time zones, which follow predictable patterns, leap seconds arrived without warning.
The urgency to abandon them intensified recently. Because Earth has been spinning faster since 2020, the next leap second might need to be negative—time would jump forward instead of backward. This has never happened before. No software has ever been tested for it. The risk of cascading failures across systems that depend on precise timekeeping seemed too high to ignore. In 2022, the BIPM's governing body decided to retire leap seconds by 2035. This week's vote will formalize that decision and approve the replacement system.
The leading proposal is elegant in its simplicity: let UTC drift from Earth's rotation. Allow the two to separate gradually, year after year, until they are an hour out of sync. Then, centuries or millennia from now, observe a single "leap hour" to bring them back into alignment. Given that Earth's rotation currently loses less than a second per year, the first leap hour won't be necessary for more than a thousand years. By then, the timekeeping systems we rely on today will almost certainly be obsolete, replaced by technologies we cannot yet imagine. One researcher at Australia's National Measurement Institute noted that in a hundred years, software will likely be so automated that the kinds of problems leap seconds create today simply won't exist.
There is a philosophical dimension to the change. Some argue that abandoning leap seconds severs our connection between the way we count time and our actual experience of it—the rotation of the Earth beneath our feet. But clocks themselves are artificial constructs, designed to serve human needs. The atomic second serves those needs far better than Earth's variable spin ever could. For the timekeeping authorities gathering this week, the choice is clear: solve the problem now by accepting a drift that won't matter for a thousand years, or keep patching a system that breaks every few years. The vote will almost certainly go one way.
Bemerkenswerte Zitate
Leap seconds break software assumptions about time, such as that it only moves forwards and there are 60 seconds in a minute.— Darryl Veitch, computer networking researcher, University of Technology Sydney
A negative leap second has never happened before, and therefore the software for that has never been tested.— Darryl Veitch, computer networking researcher