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
Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma
In October 2026 three Yandex data centers in Central Russia were physically destroyed within days, triggering the collapse of Yandex Cloud and multiple core services. Between the first and third site failures engineers had 74 hours to restore quorum and rebalance workloads yet failed to do so because Control Plane components remained tied to the lost zone and spare capacity had been eliminated to cut costs. Core banking and BNPL systems entered Read-Only mode after losing quorum, forcing a complete stop-the-world reconciliation that lasted until 22 October. Backups stored inside the same regional S3 buckets proved unusable, resulting in a seven-day RPO and primary-key collisions after restoration. The incident exposed that Metro-Cluster designs had been incorrectly treated as full Disaster Recovery and that aggressive AP microservice patterns created logical split-brain conditions outside the database layer.
Astra Group Releases Low-Code Astra AI Platform for Building Corporate AI Agents in Closed Environments
Astra Group has launched the Astra AI Platform, a low-code constructor designed for creating corporate AI applications that operate entirely within closed circuits without reliance on foreign clouds. The platform targets small and medium businesses as well as large corporations, enabling rapid deployment of AI secretaries, technical support assistants, and other agents in days rather than months. It forms part of the broader Astra AI ecosystem and includes two main constructors: one for machine learning model training and deployment, and another for LLM-based language assistants, document search, and process automation. Users can assemble scenarios from visual blocks, debug them in real time, or extend functionality with custom Python code when needed. The solution supports RAG-based knowledge bases, integration with external tools such as CRM and ERP systems, and the coordination of multiple agents for distributed task handling. One demonstrated use case involves processing ten pages of engineering drawings and specifications in five minutes to prepare data for downstream systems. The product is already listed in the Russian domestic software registry and available to customers.
Multi-Tenancy Isolation in VictoriaMetrics, VictoriaLogs and Grafana: Building Client Separation in a Shared Stack
Voltir runs a single shared monitoring stack consisting of VictoriaMetrics, VictoriaLogs, Grafana and vmalert for all customers instead of deploying separate instances per tenant. Isolation relies on numeric account IDs enforced at every layer: nginx validates tokens against the platform API before proxying writes, Grafana data sources hard-code tenant accounts, and vmalert rules receive automatic account filters. The team discovered that a single malformed rule or template could break alerting for every tenant because vmalert loads the entire rules directory at once. They also found that Grafana automatically created personal organizations granting Org Admin rights, accumulating hundreds of orphaned organizations and users that consumed disk space and resources. A dedicated cleanup module plus hourly reconciliation now removes rules, organizations, series and users when a tenant is deleted, while isolation tests verify both data and API objects across tenants.
The Real Costs of Using Claude and GPT for Russian Businesses Exposed
Accessing generative AI models like Claude and GPT has become straightforward for Russian companies, yet calculating their true expenses remains complex. Hidden factors such as intermediary commissions, currency conversion rates, taxes, and the often-overlooked costs of model reasoning tokens can double or triple initial estimates. Founder Vitaly Nagay of the Heli service analyzed these financial and organizational risks for Russian firms relying on foreign AI providers. In one example, a support department processing 20,000 monthly queries sees costs rise from $240 to $480 when reasoning tokens are included. Nagay recommends evaluating providers by dividing actual ruble charges by the model's official dollar pricing to reveal hidden markups. Additional concerns involve data control, document compliance, and access history when employees use personal subscriptions. Companies are advised to verify billing details, data storage policies, and issue dedicated API keys with spending limits before procurement.