The International Bureau of Weights and Measures (BIPM) announced that it will cease issuing leap seconds, with the final adjustment slated for May 2027. The move ends a long‑standing practice of inserting a one‑second correction into Coordinated Universal Time.
Key Takeaways
- The BIPM will stop adding leap seconds after May 2027.
- Patrizia Tavella leads the BIPM time department that drove the decision.
- Google and Meta already mitigate leap‑second effects with a “smear” technique.
- Judah Levine of NIST has weighed in on the technical implications.
- A past leap‑second insertion disrupted Qantas’s booking system.
| Metric | Value | Why it matters |
|---|---|---|
| Organization ending leap seconds | International Bureau of Weights and Measures (BIPM) | Sets the global standard for Coordinated Universal Time. |
| Effective cessation date | May 2027 | Marks the final scheduled leap‑second insertion. |
| BIPM time‑department director | Patrizia Tavella | Provided official commentary on the policy shift. |
| NIST fellow commenting on the change | Judah Levine | Offers an independent standards‑body perspective. |
| Companies using smear method | Google, Meta | Demonstrates industry‑level mitigation strategies. |
| Airline impacted by a leap second | Qantas | Illustrates real‑world operational risk. |
Decision to End Leap Seconds
We see the BIPM’s announcement as the culmination of years of debate over whether a one‑second correction remains the most reliable way to keep atomic time aligned with Earth’s rotation. By setting May 2027 as the cut‑off, the bureau provides a clear horizon for developers, infrastructure operators, and regulators to adjust their systems.
Key Voices Behind the Change
Patrizia Tavella, who heads the BIPM time department, communicated the rationale in an email to WIRED. Judah Levine, a fellow at the U.S. National Institute of Standards and Technology, has also contributed technical insight, underscoring the broader standards community’s support.
Industry Workarounds: Smear Methods
We note that major platforms such as Google and Meta have already adopted a “smear” approach, spreading the extra second over a longer interval to avoid a sudden timestamp jump. This practice has become a de‑facto industry standard for handling the occasional leap‑second insertion without disrupting services.
Historical Glitches Highlight Need for Change
The disruption of Qantas’s booking system during a previous leap‑second event serves as a concrete reminder that even well‑engineered systems can falter when faced with an unexpected one‑second shift. That incident fuels the argument for a cleaner, leap‑second‑free timeline.
What Comes Next After May 2027
We expect system architects to begin phasing out leap‑second handling code well before the 2027 deadline. Monitoring tools will likely be updated to flag the final scheduled insertion, and organizations that have relied on smear techniques may revisit their time‑synchronization strategies.
Why it matters
Eliminating leap seconds simplifies timekeeping for distributed systems, reduces the risk of timestamp‑related bugs, and aligns global time standards with the expectations of modern high‑frequency applications. Stakeholders—from cloud providers to airline reservation engines—should track the BIPM timeline and verify that their time‑source configurations are prepared for a leap‑second‑free future.
Frequently asked questions
When will the last leap second be added?
The final leap second is scheduled for May 2027, after which the BIPM will no longer issue any further adjustments.
Who announced the discontinuation?
The International Bureau of Weights and Measures (BIPM) issued the decision, with input from its time‑department director Patrizia Tavella and NIST fellow Judah Levine.
How are major tech companies handling leap seconds today?
Both Google and Meta employ a smear technique that distributes the extra second over a longer period, preventing a sudden jump in system clocks.
What real‑world impact has a leap second had?
Qantas experienced a booking‑system outage during a past leap‑second insertion, illustrating the operational risk.
Will any other organizations adopt smear methods?
While the source mentions Google and Meta specifically, the precedent suggests that other large‑scale services may consider similar approaches to avoid timing glitches.
Bottom Line
We conclude that the BIPM’s decision to end leap seconds by May 2027 represents a decisive step toward a more stable, uniform timekeeping framework, with industry leaders already demonstrating viable mitigation strategies and past incidents underscoring the practical benefits.
Looking ahead, the tech ecosystem will need to validate that all time‑synchronization pipelines are ready for a leap‑second‑free world.
Reporting based on: original source.
Comments
Post a Comment