The International Earth Rotation Service’s decision to skip the 2024 leap second and ultimately abolish leap seconds by 2035 relieves programmers of complex time‑keeping hacks, as current NTP, PTP, and newer Windows systems can already handle adjustments while past leap seconds have repeatedly disrupted software.
This article explains the evolution of time concepts, the development of various clocks, the definitions of GMT, UTC, and atomic time, and how network time protocols like NTP synchronize computers, highlighting practical considerations for using local versus server time in time‑critical applications.
The article explains why leap seconds are added to keep UTC aligned with Earth's rotation, describes the three time scales (UT1, TAI, UTC), details Linux kernel bugs caused by leap‑second handling across various versions, and offers mitigation scripts while discussing the future removal of leap seconds.
The article explains how the International Earth Rotation Service’s decision to cease adding leap seconds after 2035 will affect computer systems, recounts past leap‑second‑induced outages, and discusses the long‑term timing drift challenges programmers may face.
The International Bureau of Weights and Measures announced the phase‑out of leap seconds, a practice that has caused system crashes and NTP headaches for major tech firms, and the decision—effective by 2035—will reshape how global time synchronization is handled in operations.
The article analyzes the 2012 Azure outage caused by a leap‑year date bug, explains Azure's cluster and Fabric Controller architecture, discusses common leap‑year and leap‑second pitfalls, and shows how time anomalies can cascade through DNS and other cloud services, illustrated with real code examples.
This article explores the origins of time measurement, the transition from astronomical clocks to atomic standards, how UTC and leap seconds are defined, and the technical mechanisms—especially NTP—that keep computers and devices precisely synchronized across the globe.
This article explores why clocks—both mechanical and computer—often lose accuracy, explains the physics behind the definition of a second, describes how atomic clocks and UTC were created, and details how network protocols like NTP synchronize system time while handling leap seconds and clock drift.
This article explores why clocks—both mechanical and computer—lose accuracy, explains the evolution from astronomical timekeeping to atomic standards, details how national time centers broadcast time, and shows how protocols like NTP synchronize devices while handling network delays and leap seconds.
This article explains the evolution of the second, the definitions of UT, TAI and UTC, why leap seconds are needed, their impact on critical IT systems, and details Alibaba's innovative approach of splitting the extra second into 86,400 parts to maintain seamless global time synchronization.
The article explains the historical definition of the second, the concept of leap seconds, their impact on large‑scale IT systems, and details Alibaba's multi‑step approach of splitting the extra second into 86,400 parts to maintain accurate time synchronization across its infrastructure.
The article explains the concept of a leap second, its scheduling by the IERS, the operational impact on large IT systems, and details Alibaba's technical strategy—including testing, time‑distribution methods, and team coordination—to guarantee a seamless transition during the 2015 positive leap second.
