# CGPM Kills Leap Seconds, Caps UTC Drift

**URL:** <https://community.nwtime.org/t/cgpm-kills-leap-seconds-caps-utc-drift/468>\
**Category:** General\
**Created:** [October 19, 2026, 2:25pm UTC](https://community.nwtime.org/t/cgpm-kills-leap-seconds-caps-utc-drift/468 "2026-10-19T14:25:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dru](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nwtime.org/dru/32/337_2.png) [@Dru](https://community.nwtime.org/u/Dru)\
**Post date:** [October 19, 2026, 2:25pm UTC](https://community.nwtime.org/t/cgpm-kills-leap-seconds-caps-utc-drift/468/1 "2026-10-19T14:25:58Z")

</div>

Overview of the ramifications of Continuous UTC

> **[CGPM Kills Leap Seconds, Caps UTC Drift \[2026\]](https://tech-insider.org/cgpm-kills-leap-seconds-continuous-utc-2026/)**
>
> CGPM votes to abolish leap seconds for Continuous UTC, allowing 3,600s UT1/UTC drift. What it means for developers and time-sync code.