The General Conference on Weights and Measures has voted to stop adding leap seconds to the world's clocks, warning that the practice could trigger a remediation effort comparable to the millennium bug. At the organization's 28th meeting last week, members decided to end the long-standing practice of inserting extra seconds to synchronize Universal Time with Coordinated Universal Time, the standard humans use to set clocks. The shift comes as billions of internet-connected devices lack the ability to properly handle these time adjustments, creating what officials call a "high risk" of widespread infrastructure failures.
The conference expressed particular alarm about a negative leap second, which has never been implemented before but became possible as Earth's rotation has recently accelerated. Officials estimate that preparing critical systems for such an adjustment would require financial investment similar to Y2K preparations, which historians now peg at $300 billion to $600 billion globally. The organization also pointed to inconsistencies created by different mitigation approaches among global service providers, which lead to timing discrepancies that don't conform to the standard second. Meanwhile, the proliferation of IoT technologies, distributed sensor networks, smart grids, and virtual services has amplified the danger that any leap second insertion could cause malfunctions across systems and services.
The Time Lords wrote in their resolution that "a negative leap second has not previously been applied, and it is considered to pose a high risk of causing anomalies and disruption to critical infrastructures that are largely unprepared." According to the conference, the growing influence of internet-connected technologies "creates an increasing risk of malfunction in operation of systems and services with the insertion of any leap second, especially with a negative one." The resolution noted that different mitigation methods used by service providers lead to "inconsistency in timing between different systems and in the disseminated time and frequency."
The concern centers on the fragmented state of IoT manufacturing and standards. Countless device makers produce equipment with insecure software, vulnerable code that allows malware infection, or no mechanism for easy updates, leaving billions of gadgets unable to correctly process a leap second. Digital certificates include a "notbefore" timestamp, and systems that encounter a misbehaving certificate will refuse it. In a worst-case scenario, if a major internet service provider's modems couldn't accommodate the extra sliver of time, the network might reject its own customers as untrustworthy and block their connections. The organization's resolution suggests officials have adopted a prudent long-term perspective on the inevitable shortcomings of software development, recognizing that expecting flawless implementation across billions of devices isn't realistic.
Starting next year, the conference will allow Universal Time and Coordinated Universal Time to drift apart by up to 3,600 seconds under a framework called "Continuous UTC." Humanity already has extensive practice adding and removing hours through Daylight Saving Time, which some jurisdictions are now moving to eliminate. The decision essentially acknowledges that keeping two time standards in lockstep isn't worth the infrastructure risk in an era when critical systems depend on synchronized timing across devices that may never receive proper updates. Regulators and technology leaders should recognize that infrastructure built on assumptions of vendor cooperation and device upgradeability may need fundamental rethinking as the installed base of unmanageable endpoints continues to grow.