Companies update software for leap second after the last occurrence in 2012 led to some service outages
Providing information for our customers … Gavin Clarke / The Register : Leap second boffins prepare to fiddle with the FABRIC of TIME
Context & Ripple Effects
The June 2015 leap second was flagged in January as a stability threat to UNIX and Linux systems, the same class of glitch that caused service outages at its last occurrence in 2012. This piece is the follow-through: vendors and operators updating their software so the one-second clock adjustment passes without a repeat.
The arc runs longer than one night — by 2022, Meta, Google, Microsoft, and Amazon had joined NIST's push to scrap the leap second entirely, an acknowledgment that periodic manual remediation across global infrastructure is a cost the industry wants to retire.
First-order effects
- Operators of UNIX and Linux systems must apply time-handling updates before June's insertion of a leap second, since the same adjustment produced outages in 2012.
Second-order effects
- Cloud-scale providers bear the operational burden of coordinating patches across fleets, which pushes them toward lobbying bodies like NIST rather than absorbing recurring fix cycles.
Third-order effects
- If the pattern holds, the industry moves from patch-every-seven-years firefighting to abolishing the leap second outright, shifting the burden from thousands of operators to standards bodies redefining how civil time tracks Earth's rotation.
The trend: Timekeeping is migrating from operator-side patching against irregular clock corrections toward industry-led abolition of the leap second itself.