What a leap second is
Coordinated Universal Time, UTC, is built from atomic clocks, but it is meant to stay close to UT1, the time scale defined by the Earth's rotation. The Earth's rotation is not perfectly steady, so the two drift apart. To keep UTC within 0.9 seconds of UT1, an extra second has occasionally been added at the end of June 30 or December 31. On those days the last minute has 61 seconds:
23:59:58 23:59:59 23:59:60 the leap second 00:00:00
The International Earth Rotation and Reference Systems Service (IERS) announces in its Bulletin C whether a leap second will be added at the next opportunity. The most recent bulletin, number 72 of July 6, 2026, says there will be none at the end of December 2026. For how UTC relates to time zones and GMT, see UTC and Time Zones Explained.
UTC and TAI: 37 seconds apart
International Atomic Time, TAI, counts SI seconds and is never adjusted. UTC ticks at the same rate but is held back by every leap second. IERS Bulletin C states that UTC minus TAI is −37 seconds, in effect since January 1, 2017. In other words, when it is midnight UTC, TAI already reads 00:00:37.
Only 27 of those 37 seconds are leap seconds. The other 10 date from before the first leap second, so the leap seconds alone do not explain the whole gap.
Every leap second since 1972
The first leap second came on June 30, 1972, the last on December 31, 2016. Of the 27, 11 were added at the end of June and 16 at the end of December. 9 came in the 1970s alone; from 2000 on there were only 5.
| Decade | Leap seconds |
|---|---|
| 1970s | 9 |
| 1980s | 6 |
| 1990s | 7 |
| 2000s | 2 |
| 2010s | 3 |
| 2020s so far | 0 |
| Total | 27 |
By November 2026 it has been about 9.8 years since the last one, longer than the longest gap between two leap seconds, which was 7 years. All 27 were positive, adding a second.
The negative leap second
The rules also allow a negative leap second: a second taken away, so that the minute ends at 23:59:58 and the next second is midnight. It would keep UTC close to UT1 if the Earth's rotation sped up enough. It has never been applied. The 2026 resolution of the General Conference on Weights and Measures (CGPM) cites a 2025 estimate that the probability of a negative leap second will rise quickly, reaching 30 percent by 2035, and calls it a high risk for critical infrastructure.
What computers do with a leap second
Unix time, the seconds counter used by most computers, does not count leap seconds. The POSIX definition accounts for each and every day with exactly 86,400 seconds. December 31, 2016 had 86,401 seconds in UTC, but in Unix time the day from 1483142400 to 1483228800 is 86,400 seconds long. A real stopwatch running across that midnight measured 86,401.
| Moment (UTC) | Unix time | Julian date | MJD |
|---|---|---|---|
| Dec 31, 2016 00:00 | 1483142400 | 2457753.5 | 57753 |
| Jan 1, 2017 00:00 | 1483228800 | 2457754.5 | 57754 |
How a system brings its clock back in line with UTC is left to the implementation. Either way, subtracting two Unix timestamps across a leap second gives a result that is one second short. The Unix timestamp converter turns those numbers into dates, and the Julian date converter does the same for the day count astronomers use, where the NIST table lists the last leap second at MJD 57753.
Leap seconds are not leap years
The two fixes sound alike but solve different problems. A leap day keeps the calendar in step with the Earth's orbit around the Sun, and it follows a fixed rule that can be worked out centuries ahead; see Leap Year Rules Explained. A leap second kept the clock in step with the Earth's turn on its axis, and each one was announced in an IERS bulletin months ahead. The scale is very different too. A leap day adds 86,400 seconds at once. At the pace of 0.6 leap seconds per year seen from 1972 to 2016, adding up to one leap day's worth would take about 144,000 years. Leap years stay exactly as they are; only the second-level patch ends.
For most data the practical lesson is simple. A timestamp that reads 23:59:60 on one of the 27 leap second dates is valid UTC, not a typo, and a log or measurement that spans one of those midnights may be one second longer than the Unix timestamps suggest.
The end of leap seconds
The CGPM has decided to stop adding leap seconds. Two resolutions set the course:
- 2022, Resolution 4: the maximum allowed difference between UT1 and UTC will be increased in, or before, 2035. The CIPM was asked to propose a new limit that keeps UTC continuous for at least a century.
- 2026, Resolution 5: continuous UTC will take effect on May 20, 2027, and the maximum value for the difference between UT1 and UTC will be 3,600 seconds, one hour.
With no more leap seconds, the gap between TAI and UTC stays at 37 seconds. UTC and the Earth's rotation will slowly drift apart instead. From 1972 to 2016 leap seconds were needed at about 0.6 per year; at that pace a one-hour gap would take about 6,000 years. Time zones keep their offsets from UTC, so local time works as before, and the time zone converter gives the same answers.
Rules of thumb
- UTC is TAI minus 37 seconds, and will stay so.
- 27 leap seconds were added between 1972 and 2016, all positive, none since.
- Unix time has no leap seconds; every day is 86,400 seconds.
- From May 20, 2027, UTC is continuous by international agreement.
Frequently asked questions
What is a leap second?
A one-second adjustment to Coordinated Universal Time (UTC) that keeps atomic clock time close to the time given by the rotation of the Earth. When one is added, the last minute of June 30 or December 31 has 61 seconds and clocks read 23:59:60 before midnight. NIST lists 27 since 1972, all positive.
When was the last leap second?
On December 31, 2016. No leap second has been added since then. IERS Bulletin C 72, dated July 6, 2026, says no leap second will be introduced at the end of December 2026.
What is the difference between TAI and UTC?
TAI, International Atomic Time, runs on atomic clocks without any adjustments. UTC ticks at the same rate but has been set back by every leap second. Since January 1, 2017 UTC has been 37 seconds behind TAI, according to IERS Bulletin C.
Are leap seconds being abolished?
Yes. In 2022 the General Conference on Weights and Measures decided to raise the allowed difference between UT1 and UTC in or before 2035. In 2026 it resolved that continuous UTC will take effect on May 20, 2027, with a maximum difference of 3600 seconds, or one hour.
Can a leap second be negative?
In principle, yes: a negative leap second would remove a second, and the minute would end at 23:59:58. None has ever been applied. The 2026 CGPM resolution cites an estimate that the probability of one would reach 30 percent by 2035, and calls it a high risk for critical systems.
Sources
- NIST: Leap seconds (definition; UTC kept within 0.9 s of UT1; the table of 27 positive leap seconds from June 30, 1972 to December 31, 2016; the 23:59:60 sequence; UTC and TAI differ by 37 s)
- IERS Bulletin C 72, July 6, 2026 (no leap second at the end of December 2026; UTC-TAI = -37 s from 2017 January 1, 0h UTC)
- BIPM: Resolution 4 of the 27th CGPM, 2022 (the maximum value for UT1-UTC will be increased in, or before, 2035)
- BIPM: Resolution 5 of the 28th CGPM, 2026 (continuous UTC effective May 20, 2027; maximum |UT1-UTC| of 3 600 s; negative leap second never applied, 30 % probability estimate by 2035)
- The Open Group Base Specifications, 4.19 Seconds Since the Epoch (each day is accounted for by exactly 86400 seconds)