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
Rostelecom Outage Triggers 29-Minute Mass Disruptions Across Russian Internet Services
A 29-minute failure in Rostelecom's data transmission network on August 6 caused widespread access problems to Russian online services. The operator quickly rerouted traffic to backup equipment, restoring normal operations without revealing the root cause. Users reported issues connecting to marketplaces, banks, social platforms, IT company services and other telecom providers. The majority of complaints originated from Rostelecom's own subscribers who experienced connection and service access failures. Although the incident remained brief and did not escalate into prolonged digital disruption, it highlighted the heavy reliance on a single major provider. The event demonstrated how even a short technical problem at a large operator can simultaneously affect access to stores, financial services and everyday online platforms.
Read-Only Utility Automates Detailed Audits of UserGate NGFW Firewall Policies
A cybersecurity specialist at Gazprom CPS developed a read-only utility to analyze large-scale UserGate NGFW firewall policies without making any configuration changes. The tool connects via the UserGate XML-RPC API to collect rules, statistics, zones, network lists, services, users, and groups, then normalizes the data into a unified model for analysis. It performs eleven independent checks grouped into lifecycle, overly permissive access, observability, and documentation categories, flagging rules that have not fired recently, allow management ports broadly, lack logging, or have empty descriptions. Results are exported to a navigable Excel report featuring a rules-by-checks matrix, human-readable object names, and editable manual verdicts such as OK, requires attention, or false positive. The first full run on a production policy with over 1000 rules and 4500 related objects took 24 minutes and highlighted 39 percent of rules for review, with more than half showing multiple red flags. The approach preserves the original snapshot in JSON for repeatable offline analysis and comparison over time.
Internet Outages Disrupt Access to Russian Websites and Applications Across Multiple Regions
Users in several Russian regions reported widespread connectivity problems where internet access appeared available but failed to load most domestic websites and online services. Affected areas include Saint Petersburg along with Nizhny Novgorod, Rostov, and Tyumen regions according to reports compiled by the Telegram channel Baza. Connections remained technically active yet produced repeated errors when attempting to reach Russian sites, mobile applications, and web-based platforms. The precise scale of the disruption remains undetermined and it is unclear whether the incidents stem from a single technical fault or simultaneous failures among multiple network operators. No official statements have been issued regarding the root causes or expected restoration timelines. Individuals affected continue to refresh pages and restart applications while waiting for services to recover.
Step-Up Authentication vs 2FA: Implementing Additional Verification for Sensitive Operations in Corporate Systems
Traditional two-factor authentication secures only the initial login, leaving active sessions vulnerable to misuse during sensitive tasks such as accessing payroll data. Step-Up Authentication addresses this by requiring extra verification at the moment of critical actions rather than at login. The article details how one project moved beyond standard Identity Provider features in WSO2 by building a dedicated PIN-code service and gateway-2fa microservice. This approach uses signed cookies with TTL controls and JWT cross-checks to enforce elevated trust levels without disrupting normal user flows. The solution aligns with Zero Trust principles and was monitored via Matomo and ELK for usage and performance metrics. Key implementation considerations include balancing TTL duration, encrypting stored PINs, and conducting load testing before deployment.