⏰GCPM Halts Leap Seconds, Earth's Clocks Go Solo
Leap seconds out, IoT chaos in?
TL;DR
The GCPM has decided to stop introducing leap seconds to keep Earth's rotation in sync with UTC, citing IoT device issues. This change could lead to inconsistencies in timing between different systems.
The General Conference on Weights and Measures (GCPM) has decided to stop introducing leap seconds to keep Universal Time (UT1) and Coordinated Universal Time (UTC) in sync. This decision is driven by the difficulty of updating IoT devices to handle leap seconds, which could cause significant disruptions similar to the Y2K bug. Developers and system administrators need to be aware of the potential inconsistencies in timing between different systems as a result of this change. The GCPM's new scheme, Continuous UTC, allows UT1 and UTC to diverge by up to 3,600 seconds, coming into effect next year.
Key Points
GCPM stops leap seconds to prevent potential disruptions in IoT devices.
Leap seconds have been used to keep UT1 and UTC in sync since their introduction.
Continuous UTC scheme allows UT1 and UTC to diverge by up to 3,600 seconds.
The change comes into effect next year, impacting global timing synchronization.
Manufacturers of IoT devices face challenges in updating for leap second handling.
Why It Matters
If you're managing IoT devices or systems reliant on precise timing, the end of leap seconds means potential inconsistencies in synchronization. For example, a smart grid system might experience timing discrepancies without proper updates, affecting its reliability and performance. This change highlights the need for robust mitigation strategies to maintain system integrity.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,567 builders reading daily.