Basically they're just starting a 1000-year pause in the technical inconveniences connected with occasional 1-second corrections - which should be long enough for somebody else to figure out a better solution.
this post was submitted on 15 Oct 2026
169 points (98.8% liked)
Technology
88825 readers
3758 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
Ending the leap second is the right call, but the 'leap hour' compromise is quietly funny — it's a change designed to never actually be used. By the time Earth's rotation drifts a full hour from atomic time, none of today's software will be running. It's a way to kick the problem past everyone's retirement date while technically keeping UTC anchored to the sun.
The messy part is the transition they just voted away from. Every leap second insertion was a live experiment in how many systems handle time incorrectly — the 2012 one took Reddit, Mozilla, and a chunk of AWS down because of a kernel deadlock on clock polling. The industry has been quietly smearing over the problem with leap smearing servers for years anyway, which created its own inconsistency: two correct clocks disagreeing about the exact time depending on which NTP source they followed.
Haha, that sounds like procrastination to me.
Definitely world class procrastination!
this seems crazy. a whole hour? I mean why not do a minute that would make it much less often without being so off.
Yes, you're reading this right. In a 50-100 years the difference between UTC and UT1 will grow to one minute. In about 6000 years it can be even one hour and we will have to change our schedules.
They never give us enough time, you know?
At least we'll get an extra hour here in several thousand years.
I feel like the "problem" here is that we won't remember to do this in 6000 years, and the habit of doing it each leap second keeps us maintaining time, whereas the leap hour will just fall into forgotten history.
So essentially I feel like with this announcement, scientist are basically saying "balls to this, we're done here".
Maybe we should build a scary-looking shrine with pictograms to remind our descendants of the issue and warn them to keep track
Our descendants: Makes a religion around it or studies it as an unexplainable artifact
The year 8k problem.
Remember to future-proof your code against the year 8027 problem.
So in 144000 years we either skip a leap year or don’t skip one we usually would, whichever it is
It says “more than 1,000 years”, how’d you get 6,000?
1 minute every ~100 years, 60 minutes in an hour. Why 1000? 🤷
Good riddance to the leap second — it's a scheduled outage for distributed systems. The 2017 Cloudflare incident happened purely because some code paths choked when 23:59:60 showed up, and every insertion window means NTP, databases, and financial systems all hold their breath.
The leap hour is a clever deferral though: pushing the correction out roughly a century means nobody running today has to implement anything, and by the time it matters the drift gets handled wholesale instead of one second at a time. Slightly odd that it's the same diplomatic mechanism as the CGPM voting on measurement units deciding how software keeps time, but the engineering outcome is right.
https://gist.github.com/timvisee/fcda9bbdff88d45cc9061606b4b923ca
If your software is choking on completely expectable events, it it not sufficiently robust.
As you just proved, while it might be possible to write robust software that deals with dates/times, I wouldn't bet on it, and it's Definitely not practical to try.
But you are right that leap seconds were common enough to try and handle. There's a bunch of ways to handle them though, each incompatible with the others.
There is an easy solution in 100 years. You simply adjust your timezone. Something we already have the capability to do. We already tolerate hour deviations from noon.
Think of it more like that the arbitrarily zero time point on the globe moves 1 hour west. But we keep longitude fixed.
The only weird thing is more places will go to +13 and some to +14. But that's all relative.
It's funny that the easiest way to break infrastructure around the world is not to be a world class hacker, but to ask computers to simply subtract a second from their clocks.
For a computer, it's as confusing as the international date line for people
Hey, can scientists and the like please vote on whether following DST is stupid af? So that we can all just agree on that? Thanks
UTC is now UTU - universal uncoordinated time
UtU
eh doesn't have the appeal like UwU
This feels odd, id expect scientists to urge for closer unity with reality - this further distances us from it.
If we just wanted to skip leapseconds, we could have created a different paradigm not based on earths daily rotation, such as epoch time or based on some other observable and more stable instance - instead now well just be talking two orders of magnitude less precisly about our own world because we got frustrated adding leap seconds to account for our already innapropriate paradigm.
They solved this problem with ductape, and with the offbrand stuff that really makes it all look ratty and bad
Earth's rotation is unpredictable. It gradually slows due to tidal forces, but recently (since around 2020) it's been speeding up due to climate factors like melting ice at the poles redistributing mass toward the equator. This acceleration means a negative leap second might have been needed soon, a scenario that terrifies computer engineers 😆
Thats what im saying, its a flawed paradigm were currently using.
Theres a daily time that makes sense for terrestial entities, like ourselves, who through our native sensors can easily detect boundries between days and night and highnoon and with tools and techniques more precision from there - but still the paradigm itself of measuring time as subdivisions of days and further years - is profoundly flawed for entities or concepts which are not dependent on earth - such as servers - who care not when the suns up or down or which season it is - purely that one moments happens after the next in sequential measurable order
Leap seconds are iirelavent to humans and a poor lens to perceive time through for servers. But now with this change to leap hours, theoretically times intended for humans tonperceive can be up to minutes off from reality - it means timing a sunset or sunrise or other earthly and solarly moments are now slightly more nuanced to coordinate.
Personally id have prefered all analog clocks to simply be centered on its local high noon - and then all coordinating systems like logistics, transport, servers, and so on to just use epoch time (or some more readable equivalent thats seperate from earthly physical days and years)
Astronomy has gotten way too easy since we accepted elliptical orbits. Let's kludge it the fuck up again.
Astronomy works great. It's the world's software that can't handle 61 seconds in a minute and keeps crashing every time there's a correction.
Piece wise Weirstrauss function orbits?
It will make your differential equation based orbit solvers more fun!
What will happen to things like GPS that depend heavily on time, but cannot easily be reprogrammed in all devices that use it?
GPS doesn't handle leap seconds. Currently devices have to subtract ~18 seconds to convert from GPS time to UTC, this just means that offset will never need to be updated for a few thousand years. Other GNSS constellations may be different, but I assume they'd also be unaffected.
GPS doesn't handle leap seconds. Currently devices have to subtract ~18 seconds
Very interesting info, thanks!!
I think it shouldn't matter. IIRC, the GPS algorithm depends on time differences, not absolute time. As long as the satellites are coordinated with each other, receivers won't care which parameters the absolute time matches.
Not true. My 2015 car uses gps satellites to determine its clock. In 2019 there was a gps week number rollover due to a 10-bit counter rolling over. My car hasn't had the correct time since and the manufacturer doesn't distribute update CDs for it. I can set the clock manually and even change the settings to not auto update, but it resets every time I turn off the car.
So while yes the satellites just count seconds, it's interpreted by other devices and the differences will confuse them.
But does the GPS work? Is it able to correctly locate your car on the map? There are other cool things we use GPS satellites for, but their purpose is to calculate the position on a globe. A Global Positioning System, if you will.
Irrelevant, you said the receivers didn't care, and they definitely need updates to read the GPS satellites' output correctly.
Well, great, clocks are lying now too. (Or, will be, ever-so-infinitessimally, after May 2027)
To be fair they are always lying and always have been lying
Now they just lie in a different way.
😒