Scientists Consider Replacing Leap Seconds with a Century-Scale 'Extra Hour' to Protect Global Digital Infrastructure from Negative Leap Second Risks
Global timekeeping authorities are preparing a landmark decision that could fundamentally change how the world manages civil time. Instead of continuing to insert occasional leap seconds, they are considering a system that would allow an extra hour to accumulate over hundreds of years before any major correction is needed. The goal is not to lengthen the day but to permanently remove the recurring one-second adjustments that have long destabilized computer systems and may become even more dangerous as Earth's rotation speeds up.
The leap second was first introduced in 1972 to keep Coordinated Universal Time (UTC) aligned with the planet's irregular rotation. While atomic clocks maintain exceptional stability, Earth's spin varies due to internal geological processes, ocean currents, atmospheric conditions, and other factors. When the difference between atomic time and astronomical time grows too large, specialists add a single extra second to the calendar year.
For ordinary users the adjustment is barely noticeable. For digital infrastructure, however, it creates serious problems. Computer systems rely on precise sequencing of events, and an abruptly inserted second has already triggered outages at Meta, Reddit, and Cloudflare. It has also disrupted airline operations and interfered with high-frequency stock trading. As networks and financial platforms operate at ever-higher speeds, their tolerance for non-standard time changes continues to shrink.
Many developers have therefore adopted a workaround known as leap-second smearing, in which the extra second is gradually distributed over a longer interval rather than inserted all at once. While this approach reduces immediate crashes, it creates a new inconsistency: different systems begin operating under slightly different time rules.
No leap seconds have been added since 2016 because Earth's rotation has begun to accelerate. Scientists are now discussing the opposite scenario: if the planet starts to outpace atomic time, the first-ever negative leap second may be required. Removing a second from UTC has never been attempted, and experts have no data on how today's infrastructure would respond.
The risk of a negative leap second prompted the General Conference on Weights and Measures in 2022 to accelerate a review of UTC rules, originally targeting 2035 as the deadline. Updated assessments now indicate that waiting that long could be risky, with the probability of needing a negative leap second before 2035 estimated at approximately 30 percent.
The new proposal under discussion would replace the current one-second corrections with a much larger allowable deviation—potentially an entire hour—between atomic time and Earth's position. This change would push the next major adjustment centuries into the future, effectively ending the era of leap seconds for practical purposes. If approved, the revised rules could come into force as early as 2027.
The International Bureau of Weights and Measures considers the issue urgent. Even a 10 percent chance of a negative leap second is viewed as unacceptable for global digital systems. By removing the most disruptive element before it can trigger unpredictable large-scale failures, authorities hope to safeguard servers, exchanges, aviation networks, and telecommunications infrastructure.
The reform would not completely sever the connection between civil time and Earth's rotation, but it would make that link far more flexible. UTC would continue to rely primarily on atomic clocks, while any accumulated difference with astronomical time would be allowed to grow over decades or centuries. Although humanity may eventually have to address an entire hour of divergence, computer systems would no longer need to prepare for sudden one-second jumps that cause more damage than they appear to.
Related articles
Inside the Fortress: Why Perimeter Security Tools Fall Short and How Microsegmentation Protects Networks Internally
Companies invest heavily in perimeter defenses such as firewalls and intrusion detection systems, yet these measures no longer guarantee safety as attackers increasingly operate from within networks. Traditional L2 domains leave virtual machines unisolated, enabling traffic interception, lateral movement, and malware spread similar to an apartment building with poor soundproofing. Microsegmentation powered by SDN divides VLANs into isolated microsegments down to individual VM ports, enforcing granular policies based on ports, IP addresses, and protocols. This approach implements Zero Trust by placing virtual packet filters directly at VM network interfaces on the hypervisor, independent of guest OS actions. Performance remains high because filtering runs on powerful virtualization servers, and scaling occurs naturally as additional hypervisors absorb new workloads without extra configuration. A real-world case from the oil and gas sector shows one customer creating up to 5,000 new microsegmentation rules per week via open REST API. The technology complements rather than replaces perimeter firewalls, delivering both strict internal controls and operational agility.
Good Bear 1.0 Released: Firefox-Based Browser with Isolated Russian PKI Trust Container
Good Bear 1.0 is a Russian-language browser built on Firefox 156.0 that provides an isolated container for handling Russian PKI certificates without mixing trust contexts or user data with the standard browsing session. The release includes .deb packages for Ubuntu 24.04 LTS amd64 and Windows x64 installers, using Mozilla Public License 2.0 and reproducible build processes from pinned Firefox sources. Instead of globally importing root certificates, the browser performs secondary chain validation only inside a dedicated userContextId container with strict OriginAttributes isolation for caches, storage, and connections. Password autofill and sensitive session data are disabled in the container when separation cannot be guaranteed, and POST requests trigger explicit user choice before reopening in the isolated context. The interface shows both a persistent container marker and a separate RU indicator only when Russian PKI is actively used, along with detailed security panels explaining the trust source. Updates, crash reporting, and automatic MAR mechanisms are intentionally omitted to avoid creating unverified trust chains for the distribution itself.
Survey of 254 Russian Domains Shows 89% DMARC Adoption but Highlights Gaps in Reporting and Subdomain Policies
A manual review of public DNS records across 254 prominent Russian domains from 17 sectors found strong baseline adoption of email authentication mechanisms. MX records appeared in 96.1% of domains, SPF in 93.7%, DMARC in 89.0%, and DKIM records via common selectors in 62.2%. Among domains with DMARC, 40.7% published a reject policy and 42.9% used quarantine, while 16.4% remained at none. Notably, 19% of DMARC-enabled domains lacked any rua address for aggregate reports, including 33 domains enforcing reject or quarantine. The study also identified cases of inconsistent policies between parent domains and subdomains, as well as SPF records ending in ~all paired with strict DMARC settings. Researchers emphasized that DNS data alone cannot confirm actual mail flow alignment or report consumption.
Server Outage Halts Vehicle Registration Across Smolensk Region
A technical failure on a unified server has temporarily suspended vehicle registration services in the Smolensk region of Russia. The outage affects the interdistrict traffic police department No.1 located on Lavochkina street, preventing new registrations from being processed. Regional UMVD officials confirmed that the problem impacts the single server used for the entire oblast's registration system. According to department head Maxim Zykov, the disruption is considered temporary, though no precise restoration timeline was provided. Applicants who submitted requests through the Gosuslugi portal will receive services in the first working days after the system is restored. The UMVD plans to issue an additional announcement once operations resume.