The Hidden Science of Timekeeping: How We Measure a Second (and Why It Keeps Changing)
A second feels obvious—until you ask what it is. Inside atomic physics, global coordination, and the leap-second compromise that keeps clocks friendly to the sky.

Key Points
- 1Replace the sky with physics: the SI second is fixed by caesium-133, not Earth’s irregular rotation.
- 2Separate definitions from policies: the SI second stays stable, while UTC and leap seconds remain contested civil-time rules.
- 3Rely on global coordination: BIPM combines ~85 labs and ~450 clocks, using GNSS/TWSTFT links to build UTC and TAI.
A second feels simple—until you try to define it
That choice wasn’t aesthetic. It was a concession to reality. Earth does not rotate like a perfectly machined wheel. It wobbles, speeds up, slows down—subtly, unpredictably, and for reasons ranging from ocean tides to earthquakes. Civilizations once built “time” on the Sun’s rhythm; modern technology can’t afford the drift.
So when people ask why “the second” keeps changing, they’re often mixing up two different stories: the stable scientific definition of the SI second, and the messier politics of civil timekeeping—UTC, leap seconds, and what it means to keep noon near the middle of the day.
“The SI second is designed to be the same everywhere. Civil time is designed to stay friendly to the sky.”
— — TheMurrow Editorial
The second isn’t “1/86,400 of a day” anymore—and that’s the point
Earth, unfortunately, refuses to behave like a metrologist’s dream. Its rotation is irregular, influenced by tides, atmospheric circulation, earthquakes, and interactions between the core and mantle. Those changes are tiny but consequential. Precision science, navigation, telecommunications, and financial systems don’t just want “roughly right.” They want reproducible time—time that can be rebuilt in any lab, in any country, without asking the planet how it feels today.
The 1960 stopgap: the ephemeris second
It didn’t last long. Atomic standards proved more reproducible and far more practical for building clocks that could keep pace with modern needs.
What it means for readers
The modern SI second: 9,192,631,770 counts of caesium
In 1967–1968, the 13th CGPM defined the second as the duration of 9,192,631,770 periods of radiation corresponding to the transition between two hyperfine levels of the ground state of caesium-133. That number is not a poetic flourish; it’s a specification precise enough to anchor the world’s measurement system.
“A second is not a slice of the day. It’s a specified number of oscillations in caesium-133.”
— — TheMurrow Editorial
The 2019 reframing: constants, not artifacts
For time, the substance stayed the same but the style changed: the second is defined by fixing the value of the caesium hyperfine transition frequency at ΔνCs = 9,192,631,770 Hz. The definition reads like physics because it is physics.
The ideal caesium atom doesn’t exist in a lab
Metrology labs therefore build clocks that approximate the ideal and apply corrections for known perturbations. That is not a weakness of the definition; it’s the work of making a definition real.
Key Insight
The confusion: the SI second is stable, civil time is contentious
Two different “changings” get tangled together:
- The definition of the SI second (rarely updated, and currently stable).
- Civil timekeeping rules (UTC, leap seconds, how close civil time stays to Earth rotation), which are frequently debated and operationally difficult.
The SI second is a metrology choice: build a unit that is reproducible and invariant. Civil time is a societal choice: decide how to label moments so that clocks remain aligned with the rotating Earth—at least loosely.
Why that distinction matters
The SI second provides the stable “tick.” Civil time decides how to group those ticks into calendar time that humans recognize. Confusing the two leads to needless panic—and bad decisions.
“Precision timekeeping isn’t a single clock. It’s a treaty between physics and society.”
— — TheMurrow Editorial
SI second vs. civil timekeeping
Before
- SI second (physics-defined
- invariant)
- reproducible anywhere
- rarely updated
After
- Civil time (UTC rules)
- leap seconds
- debated policies to keep clocks aligned with Earth rotation
How the world builds time: TAI, UTC, and the quiet authority of BIPM
That scale matters. No single clock is perfect. The modern approach is statistical and cooperative: combine many clocks, weight their performance, and compute a timescale more stable than any individual device.
TAI: the continuous atomic backbone
UTC: civil time, tied (loosely) to Earth
BIPM’s description is crisp: UTC is the global civil reference time, while TAI is continuous atomic time. Their difference is not fractional—UTC is offset from TAI by whole seconds.
UTC(k): what your country actually maintains
For readers outside time metrology, Circular T is a reminder that “the time” is not a single object sitting in a vault. It’s a continuously maintained international alignment problem.
The global timekeeping stack (in practice)
- ✓Define the second via caesium-133 (SI)
- ✓Realize it with national and metrology-lab atomic clocks
- ✓Combine clock data into TAI (continuous)
- ✓Derive UTC from TAI plus leap seconds (civil reference)
- ✓Maintain UTC(k) locally and publish UTC–UTC(k) in Circular T
Time transfer: comparing clocks across continents without moving them
BIPM lists several key methods used in UTC computation:
- GNSS-based methods such as GPS common-view, carrier-phase, and all-in-view
- Two-way satellite time and frequency transfer (TWSTFT)
- Increasing use of new systems and links, including Galileo
Galileo joins the official toolkit
More signals, more paths, and better measurement techniques improve the reliability of comparisons—especially as clocks themselves become more accurate and demand better transfer infrastructure.
Practical implication: the bottleneck moves
For anyone building systems that depend on precise timing—telecom synchronization, power grids, satellite operations—the message is clear: time is only as good as your ability to distribute it.
Key takeaway: precision is a network property
Leap seconds: the one-second fix that can cause outsized trouble
Operationally, that means a minute with 61 seconds—a deeply unfriendly concept for computers and systems designed around uniform time steps.
Why leap seconds exist
- Keep civil time aligned with the sky (so noon remains near when the Sun is highest).
- Maintain a uniform time scale for technology.
Without leap seconds, UTC would gradually drift away from UT1. With leap seconds, UTC remains tied to Earth’s rotation, but systems must cope with discontinuities.
Why engineers dislike them
Real-world case studies exist across the industry, but the core point doesn’t require brand-name anecdotes: the leap second is the rare event that tests every assumption you didn’t know your code was making.
Multiple perspectives, same underlying tension
Both sides have a coherent position because they optimize for different things: the sky’s meaning versus the network’s stability.
Leap seconds in civil timekeeping
Pros
- +Keeps UTC close to UT1
- +preserves a sky-linked meaning of noon
- +supports Earth-orientation needs
Cons
- -Introduces discontinuities
- -breaks software assumptions
- -complicates distributed systems and logging
What changes next: not the second (yet), but how we manage global time
The SI second is stable—optical clocks are the long-term question
No date in the provided record commits the world to an optical redefinition. The more responsible framing is that the existing definition remains the backbone, while technology evolves toward clocks whose performance will eventually challenge how the SI second is realized and compared.
Timekeeping infrastructure will keep evolving
For readers, the practical takeaway is not that your wristwatch will break. The takeaway is that the global systems you rely on—navigation, communications, finance—depend on a continuously maintained international process that must keep adapting as accuracy improves.
A second is physics; “the time” is coordination
Frequently Asked Questions
Is a second still 1/86,400 of a day?
No. Before 1960, that was the historical approach: define the second as 1/86,400 of the mean solar day. Earth’s rotation turned out to be irregular, making that definition unsuitable for precision. The SI second is now defined using a fixed atomic frequency tied to caesium-133, making it reproducible anywhere.
What exactly is the SI definition of the second today?
The SI second is defined by fixing the value of the caesium hyperfine transition frequency at ΔνCs = 9,192,631,770 Hz (formalized in the 2018 SI revision, effective 20 May 2019). Historically, the definition is expressed as 9,192,631,770 periods of radiation for that transition.
If the second is defined by caesium, why do we need many clocks?
No real clock is perfectly isolated from temperature, motion, or electromagnetic effects. Metrology uses ensembles of clocks because combining many independent sources produces a more stable timescale than any single device. BIPM describes UTC computation drawing on about 85 laboratories and around 450 atomic clocks worldwide.
What’s the difference between TAI and UTC?
TAI (International Atomic Time) is a continuous atomic timescale. UTC (Coordinated Universal Time) runs at the same rate as TAI but differs by a whole number of seconds due to leap seconds, which are added to keep UTC close to Earth-rotation time (UT1). TAI is continuous; UTC is civil time with occasional discontinuities.
What is UTC(k), and why does it matter?
UTC(k) is a country or lab’s real-time realization of UTC (for example, UTC(NIST)). Because UTC itself is computed and published with a lag, national labs maintain UTC(k) locally and compare it to UTC. BIPM publishes offsets UTC – UTC(k) in Circular T at 5-day intervals, allowing global alignment.
How do laboratories compare clocks across long distances?
Labs use time transfer methods, including GNSS techniques (GPS common-view, carrier-phase, all-in-view) and two-way satellite time and frequency transfer (TWSTFT). BIPM also reports expanding use of other satellite systems; notably, Galileo was first used officially in UTC computation in Circular T no. 425 (June 2023).















