UTC Explained

The /learn/time-zones-explained pillar covers how civil time zones are defined as offsets from UTC. This article goes deeper on UTC itself — what it actually is, how it's computed, why leap seconds exist, the role of the BIPM and the contributing laboratories, and the planned 2035 transition to a leap-second-free regime.

What UTC is

UTC is a single, globally coordinated time reference. Every country's civil time is defined as an offset from UTC. GPS satellites broadcast time linked to UTC. Internet protocols (NTP, HTTP date headers, RFC 3339 timestamps) use UTC. Financial settlement, telecommunications, scientific observations, and weather forecasting all reference UTC.

The formal definition comes from ITU-R Recommendation TF.460-6 (Standard-frequency and time-signal emissions). The ITU (International Telecommunication Union, a UN agency) issues this recommendation; the BIPM (Bureau International des Poids et Mesures, the international metrology organization based outside Paris) coordinates the actual realization.

The two ingredients

UTC has two components:

1. TAI (International Atomic Time) — a continuous, atomic-clock-based timescale. TAI advances at the SI second rate (defined by the cesium-133 hyperfine transition at 9,192,631,770 Hz). TAI has no leap seconds and no astronomical corrections.

2. Leap seconds — occasional one-second adjustments inserted into UTC to keep it close to UT1 (Universal Time 1, the astronomical timescale based on Earth's actual rotation).

The relationship:

UTC = TAI - (accumulated leap seconds)

As of 2026, the accumulated leap seconds since UTC's 1972 introduction is 27, so TAI - UTC = 37 seconds (starting from a 10-second offset at the 1972 baseline, plus 27 leap seconds added subsequently = 10 + 27 = 37, matching the BIPM record).

Why two components? TAI gives the precision and stability of atomic clocks; the leap-second mechanism preserves a useful link to astronomical time. If UTC were just TAI, civil “noon” would slowly drift away from solar noon over centuries. If UTC were just UT1, it would have sub-millisecond unpredictability (Earth's rotation fluctuates with atmospheric and oceanic effects).

How the BIPM coordinates UTC

The BIPM operates a continuous worldwide coordination process. Roughly each step:

1. Local realizations: each contributing laboratory maintains its own atomic timescale, called UTC(k) where k is the laboratory code. UTC(USNO) is the U.S. Naval Observatory's realization; UTC(NIST) is NIST's; UTC(PTB) is the Physikalisch-Technische Bundesanstalt in Germany. Each laboratory runs cesium fountain clocks and/or hydrogen masers to maintain its realization.

2. Data submission: each laboratory transmits its measurements (clock comparisons via GPS common-view, two-way satellite time transfer, etc.) to the BIPM.

3. EAL (Échelle Atomique Libre): the BIPM computes a free-running weighted average of all contributing clocks, called EAL.

4. Scaling: EAL is scaled by primary frequency standards (cesium fountains at NIST, NPL, PTB, others) to produce TAI at the exact SI-second rate.

5. Leap-second adjustment: TAI minus accumulated leap seconds gives UTC.

6. Circular T: the BIPM publishes monthly the “Circular T” report, giving the offset between each UTC(k) and UTC for every five-day interval. Laboratories adjust their realizations to track UTC at the nanosecond level.

The participating laboratories include national metrology institutes (NIST, NPL, PTB, NMIJ, BIPM itself, IFAG, KRISS, NIM, VNIIFTRI, ONRJ, etc.) and observatories (USNO, etc.) across ~50 countries. As of 2026, the total active clock count is approximately 400.

UT1: the astronomical reference

UT1 is the astronomical timescale based on Earth's actual rotation, derived from observations of distant quasars by Very Long Baseline Interferometry (VLBI) and satellite-based observations.

UT1 fluctuates on multiple timescales:

• Long-term: Earth's rotation is slowing due to tidal friction with the moon, lengthening the day by about 2.3 milliseconds per century averaged over millennia.
• Decadal: irregular variations of ~10 ms over decades due to core-mantle coupling.
• Annual: a ~30 ms annual cycle from atmospheric mass redistribution.
• Sub-daily: ~1 ms variations from tides and weather.

The International Earth Rotation and Reference Systems Service (IERS) in Paris coordinates the UT1 determination. IERS Bulletin A provides predicted UT1 values; Bulletin B provides final post-analysis values.

Why leap seconds exist

UTC is required to stay within 0.9 seconds of UT1. When the predicted difference (UT1 - UTC) approaches that threshold, IERS announces a leap second via Bulletin C, issued about six months in advance of the insertion.

Leap seconds are inserted at the end of June 30 or December 31 (UTC). The mechanism: the UTC second 23:59:59 of the affected day is followed by 23:59:60 (an additional second), then 00:00:00 of the next day. Some software handles this correctly; some doesn't.

The 27 leap seconds added since 1972 (and the 10-second baseline TAI-UTC offset at January 1, 1972) give the current TAI - UTC = 37 seconds.

Recent and notable leap seconds:

• December 31, 2016 — most recent leap second.
• June 30, 2015 — preceded the 2016 one.
• June 30, 2012 — caused notable Internet outages (Cassandra, Hadoop, Linux kernel bugs).
• December 31, 2008 — a notable end-of-year leap second.

The variable insertion rate reflects Earth's unpredictable rotation: 1972–1979 averaged a leap second per year; 1999–2005 saw none; 2008, 2012, 2015, 2016 saw four in eight years.

The 2022 CGPM Resolution 4

In November 2022, the General Conference on Weights and Measures (CGPM) — the world's highest authority for metrology — adopted Resolution 4: the maximum allowed difference between UTC and UT1 should be increased by or before 2035. The practical effect: leap seconds will be suspended, and UTC will be allowed to drift further from UT1 than the current 0.9-second limit.

The motivation: leap seconds cause persistent operational problems for time-dependent software systems (databases, distributed-consensus protocols, financial systems, satellite systems). The 2012 leap second caused documented outages at Reddit, LinkedIn, Mozilla, Qantas (airline reservations), Yelp, and many other services. The 2015 and 2016 leap seconds caused fewer but still non-trivial problems despite years of preparation. Major platforms (Google, Amazon, Meta, Microsoft) have advocated for leap-second abolition for over a decade.

The exact replacement mechanism is still being defined. One likely approach: allow UTC to drift from UT1 by minutes (rather than seconds), with infrequent (perhaps decadal) larger corrections. The 2035 deadline gives time for software, standards, and operational systems to adapt.

UTC and GPS Time

GPS Time is a separate atomic timescale used by the Global Positioning System. Key facts:

• GPS Time epoch: January 6, 1980 at 00:00:00 UTC.
• GPS Time advances at the SI-second rate (same as TAI).
• GPS Time has no leap seconds.
• GPS Time - UTC = number of leap seconds added since the epoch.

As of 2026, GPS Time - UTC = 18 seconds. The 18 leap seconds: every leap second since the 1980 epoch (the 1972–1979 ones predate GPS). GPS satellites broadcast both GPS Time and the GPS Time - UTC offset; receivers display UTC by applying the offset.

GPS Time - TAI = -19 seconds (constant, because both run at the same atomic rate, and the 19-second offset was set at the 1980 epoch).

The three timescales — TAI, UTC, GPS Time — are linked by simple constant or near-constant offsets:

TAI - UTC = 37 seconds (changes only when leap seconds are added)
TAI - GPS Time = 19 seconds (constant)
GPS Time - UTC = 18 seconds (changes only when leap seconds are added)

UTC and civil time

Every civil time zone is defined as an offset from UTC. For details, see /learn/time-zones-explained.

The relationship of UTC to UTC offsets:

Local time = UTC + offset

So Eastern Standard Time (UTC-5) is computed as UTC - 5 hours; India Standard Time (UTC+5:30) is UTC + 5:30. The offset depends on the location and on whether DST applies at the time of interest.

UTC in software

Best practices:

• Store timestamps in UTC in databases, APIs, internal state. Convert to local time only at the presentation layer.
• Use ISO 8601 / RFC 3339 for serialization: 2026-05-24T17:30:00Z (with Z for UTC) or 2026-05-24T17:30:00+00:00 (explicit offset).
• Sync with NTP for system clock accuracy. Sub-second precision typically requires PTP (Precision Time Protocol) or GPS-synchronized clocks.
• Handle leap seconds gracefully until they're abolished. Common strategies: leap-smear (gradually distort time over a window to absorb the leap second without a discontinuity), used by Google, Meta, AWS. The 0.9-second-or-less drift during smearing is acceptable for most applications.
• For pre-1972 dates: UTC didn't exist; use UT1 or local time. The IANA tz database provides civil-time data back to ~1970.

Common misconceptions

“UTC and GMT are the same.” They're synchronized to within 0.9 seconds and look identical for civil purposes, but they're technically distinct. GMT is based on Earth rotation (essentially UT1 for civil use); UTC is based on atomic time with leap-second corrections. See /learn/gmt-vs-utc for detail.

“TAI is what GPS broadcasts.” GPS broadcasts GPS Time, which is offset from TAI by a constant 19 seconds. GPS receivers compute and display UTC by applying the broadcast GPS Time - UTC offset.

“Leap seconds are added because Earth's rotation is speeding up.” Leap seconds are added because Earth's rotation is slowing on long timescales. Short-term fluctuations can produce intervals of speeding up (no leap seconds inserted) or slowing down (leap seconds inserted). The 2020s have been an unusual decade with no leap seconds inserted since 2016, partly because Earth has been rotating slightly faster than expected.

“Leap seconds happen at midnight.” They happen at the end of June 30 or December 31 in UTC — which is, depending on time zone, midnight or some other time of day locally. In Tokyo (UTC+9), a leap second inserted at 23:59:60 UTC happens at 08:59:60 local time the next morning, well into the working day.

“The BIPM has the world's best clock.” The BIPM doesn't run clocks itself; it computes a weighted average from clocks at ~80 contributing laboratories. The most accurate individual clocks are optical-lattice clocks at NIST (USA), JILA (USA), NPL (UK), and elsewhere; these contribute to TAI/UTC realization but neither operates as “the” world clock.

“UTC will be abolished in 2035.” UTC will continue. What changes is the leap-second mechanism. The exact replacement is still being designed; one likely form is a wider UT1-UTC tolerance with infrequent larger corrections rather than annual one-second adjustments.

“Internet protocols use TAI.” Most use UTC. HTTP, RFC 3339, NTP, and most application-level protocols use UTC. PTP (Precision Time Protocol) provides nanosecond-precision UTC over Ethernet for telecom and financial-trading use.

“UTC is a U.S. or European thing.” The BIPM is in France, but UTC contributions come from ~50 countries; the system is genuinely international. The ITU recommendation is a UN-level standard. Major non-NATO contributors include Japan (NMIJ), China (NIM), Russia (VNIIFTRI), India (NPLI), Brazil (ONRJ), and South Korea (KRISS).