Leap Second Calculator

Calculate cumulative leap seconds and offsets between UTC, TAI, and GPS time scales for any date.

Recent Leap Seconds

Dec 31, 2016+1s (Total: 27)
Jun 30, 2015+1s (Total: 26)
Jun 30, 2012+1s (Total: 25)
Dec 31, 2008+1s (Total: 24)
Dec 31, 2005+1s (Total: 23)
Dec 31, 1998+1s (Total: 22)
Jun 30, 1997+1s (Total: 21)
Dec 31, 1995+1s (Total: 20)
Jun 30, 1994+1s (Total: 19)
Jun 30, 1993+1s (Total: 18)

Cumulative Leap Seconds

27

TAI - UTC

37s

GPS - UTC

18s

Time Information

Last Leap Second: December 31, 2016

Days Since Last: 3,486

Days Since Unix Epoch: 20,652

Total Leap Seconds (all time): 27

Leap Seconds by Decade

1970s
9
1980s
6
1990s
7
2000s
2
2010s
3

Note: Leap seconds are added to keep UTC within 0.9 seconds of UT1 (Earth rotation time). They are announced by IERS and typically added on June 30 or December 31. The last leap second was added on December 31, 2016.

What Is a Leap Second?

A leap second is an occasional one-second adjustment made to Coordinated Universal Time (UTC) to keep it synchronized with Universal Time 1 (UT1) β€” the time scale based on Earth's actual rotation. Unlike the predictable leap days added to calendar years, leap seconds are added irregularly because Earth's rotation is not perfectly uniform: it speeds up and slows down due to tidal friction, atmospheric pressure changes, and interactions with Earth's molten core.

Since 1972, when the UTC leap second system was introduced, 27 positive leap seconds have been added (as of 2024), all at 23:59:60 UTC on June 30 or December 31 of their respective years. The leap second makes the UTC clock read 23:59:60 before advancing to 00:00:00 of the new day, giving Earth's rotation a chance to catch up with atomic time.

The international decision was made in 2022 to eliminate leap seconds by 2035. Until then, the Leap Second Calculator shows the full history of all 27 leap seconds, the current UTC-UT1 offset (the Delta T value), and whether the selected date falls on or near a historical leap second insertion.

Leap Second Lookup

The calculator finds the cumulative leap seconds for any date by checking the date against a hardcoded table of all historical leap second insertions.

Cumulative Leap Seconds

leapSeconds = max(ls.cumulative for all ls where date >= ls.date)

Where:

  • leapSecondDates= Array of {date, cumulative} objects for each leap second insertion since 1972
  • cumulative= Total number of leap seconds added to UTC since 1972-01-01
  • Delta T (Ξ”T)= TT βˆ’ UT1 β‰ˆ cumulative leap seconds + 32.184 seconds (historical offset between TAI and UT1 at the 1972 epoch)
  • TAI βˆ’ UTC= = cumulative leap seconds (currently 37 seconds as of Jan 1, 2017)

History of Leap Seconds

All 27 leap seconds have been positive β€” adding 23:59:60 before the next minute. No negative leap second (removing a second) has ever been used, though the IERS (International Earth Rotation and Reference Systems Service) has the authority to insert them. The frequency of leap seconds has decreased in recent decades as Earth's rotation has been gradually accelerating:

  • 1972–1979: 9 leap seconds β€” very frequent early on as UTC calibrated to UT1
  • 1980–1999: 13 leap seconds β€” roughly one every 18 months
  • 2000–2016: 5 leap seconds β€” slowing frequency
  • 2017–2024: 0 leap seconds β€” none added in 7+ years

The last leap second was inserted on December 31, 2016. As of 2024, UTC is 37 seconds ahead of UT1 (International Atomic Time is 37 seconds ahead of UTC, which means TAIβˆ’UTC = 37s).

How to Use This Calculator

  1. Select a Date: Enter any date to see the cumulative leap seconds in effect on that date.
  2. Check History: The full table of all historical leap second insertions is displayed for reference.
  3. Leap Second Day: If the selected date is a historical leap second insertion date, the calculator notes that a leap second was added on that day.

Real-World Applications

Leap seconds are a significant operational concern for timekeeping infrastructure. When a leap second is inserted, networks, servers, and databases that rely on UTC must handle the discontinuity. A 23:59:60 timestamp does not exist in most computer systems β€” they may freeze the clock for one second, smear the second across a longer period (Google's "leap smear"), or experience brief anomalies.

Financial exchanges must handle leap seconds carefully because transaction timestamps are legally significant. A trade timestamped 23:59:60 on a leap second day could cause database integrity issues or sorting errors in systems that don't recognize the 60-second value.

GPS receivers, telecommunications networks (NTP/PTP), and astronomical observatories all maintain leap second tables. The decision to discontinue leap seconds after 2035 was made partly because managing them across global infrastructure has become increasingly complex and error-prone.

Worked Examples

Leap Seconds Before GPS

Problem:

How many leap seconds had been added by the GPS epoch (January 6, 1980)?

Solution Steps:

  1. 1GPS epoch: January 6, 1980 00:00:00 UTC
  2. 2Leap seconds added through December 31, 1979: 9 cumulative (1972–1979)
  3. 3GPS time does not count leap seconds, so GPSβˆ’UTC offset started at 0 seconds on Jan 6, 1980
  4. 4By January 1, 2017 (last leap second), 18 more were added: GPS is now 18 seconds ahead of UTC

Result:

At the GPS epoch (Jan 6, 1980): 9 cumulative leap seconds in UTC history. GPS-UTC offset = 18 seconds as of 2024.

TAI vs UTC

Problem:

How many seconds ahead of UTC is International Atomic Time (TAI) in 2024?

Solution Steps:

  1. 1TAI started 10 seconds ahead of UTC in 1972 (historical offset at system introduction)
  2. 227 positive leap seconds have been added since 1972
  3. 3TAI βˆ’ UTC = 10 + 27 = 37 seconds
  4. 4This 37-second offset has been constant since January 1, 2017 (last leap second)

Result:

TAI is 37 seconds ahead of UTC in 2024. This has been constant since the last leap second on January 1, 2017.

The Last Leap Second

Problem:

When was the most recent leap second inserted?

Solution Steps:

  1. 1Most recent leap second: December 31, 2016 at 23:59:60 UTC
  2. 2The UTC clock read: 23:59:59 β†’ 23:59:60 β†’ 00:00:00 (January 1, 2017)
  3. 3No leap second has been added since then (7+ years as of 2024)
  4. 4Decision to abolish leap seconds: CGPM resolution in 2022 β€” elimination by 2035

Result:

The last leap second was December 31, 2016. As of 2024, no new leap seconds have been added in over 7 years.

Tips & Best Practices

  • βœ“UTC is currently 37 seconds behind TAI (International Atomic Time) β€” TAI has been counting continuously since 1958 without any adjustments.
  • βœ“GPS is 18 seconds ahead of UTC (as of 2024) β€” GPS receivers add this offset automatically to display correct UTC time.
  • βœ“Systems that must handle leap seconds precisely (financial, telecommunications) should subscribe to IERS Bulletin C for advance notice of upcoming insertions.
  • βœ“The 'smearing' approach used by Google/AWS/Meta spreads the extra second over hours to avoid the 23:59:60 timestamp β€” check whether your time source smears.
  • βœ“Leap seconds are always inserted on June 30 or December 31 at 23:59:60 UTC β€” never at any other time or date.
  • βœ“After 2035, UTC will no longer observe leap seconds β€” the UT1-UTC difference will be allowed to grow, eventually requiring a 'mega-leap' correction decades hence.

Frequently Asked Questions

Earth's rotation rate is affected by multiple factors: tidal friction from the Moon slowing it down over geological time; redistribution of mass in the oceans, atmosphere, and ice sheets; interactions with the fluid outer core; and geological events like major earthquakes. The net effect is a gradual long-term slowdown (days were shorter in the geological past) with irregular short-term fluctuations. Currently Earth's rotation has been speeding up slightly, which is why no leap seconds have been needed since 2017.
A negative leap second would skip one second β€” the UTC clock would go from 23:59:58 directly to 00:00:00, with no 23:59:59 on that day. No negative leap second has ever been used; all 27 insertions have been positive. If Earth's rotation continues to accelerate (as it has in recent years), a negative leap second might theoretically be needed β€” but the decision to abolish leap seconds by 2035 makes this moot.
The 27th General Conference on Weights and Measures (CGPM) voted in November 2022 to discontinue leap seconds by 2035. The primary reasons are: (1) modern distributed computing infrastructure handles leap seconds poorly, causing outages, data corruption, and clock discontinuities; (2) the allowable UT1-UTC difference will be increased from 0.9 seconds to at least 1 minute; (3) UTC will then track TAI exactly, simplifying global timekeeping. A future mechanism for large-scale corrections (if ever needed) will be decided after 2035.
Google uses 'leap smearing': instead of inserting an extra second at midnight, they gradually spread the extra time over the 20 hours surrounding a leap second, making each clock second slightly longer (by about 13.9 microseconds per second during the smear window). This avoids the 23:59:60 timestamp that can confuse systems while still keeping Google's servers synchronized with UTC. Other implementations (AWS, Amazon, Meta) have since adopted similar smearing approaches.
No β€” GPS time is continuous atomic time that does not include leap seconds. GPS time was synchronized with UTC at the GPS epoch (January 6, 1980) and has run without leap seconds since. As of 2024, GPS time is 18 seconds ahead of UTC because 18 leap seconds have been added to UTC since the GPS epoch. The GPS navigation message broadcasts the current GPS-UTC offset so receivers can display the correct UTC time.

Sources & References

Last updated: 2026-06-06

πŸ’‘

Help us improve!

How would you rate the Leap Second Calculator?

<>

Editorial Note

MyCalcBuddy Editorial Team

This page is maintained as an educational calculator reference.

Source

Formula Source: Standard Mathematical References

by Various

UpdatedLast reviewed: May 2026
CheckedFormula checks are based on standard references and internal QA review.

Privacy choices

MyCalcBuddy uses necessary storage for the site to work. Optional analytics, notifications, and future advertising features stay off unless you allow them.