The Leap Second That Froze the Web
Tech & AI10 min

The Leap Second That Froze the Web

In June twenty twelve, a single extra second added to global clocks exposed a latent defect in the Linux kernel, triggering a cascade of server failures that took down major websites and airline booking systems. This is the story of how a rare astronomical adjustment revealed the fragile assumptions buried in the code that runs the modern world.

Listen in the Fylom app.

Show notes

Atomic clocks drift from solar days because planetary wobbles make Earth's rotation inconsistent.

A Linux kernel bug caused CPUs to reach one hundred percent utilization processing millions of overdue alarms.

Reddit suffered a ninety minute outage because servers entered a livelock state during the leap second.

Australian Ethernet switches seized during the time shift, causing localized internet blackouts for two hours.

The POSIX standard ignores leap seconds by assuming every day contains exactly eighty-six thousand four hundred seconds.

Time smearing prevents system crashes by stretching the extra second over several hours instead of one moment.

In this episode
  1. 01Intro1 min
  2. 02The Sixty-One Second Minute2 min
  3. 03The Livelock in the Kernel2 min
  4. 04The Infrastructure Cascade2 min
  5. 05The POSIX Problem and the Future of Time2 min
  6. 06Outro1 min
Sources
Your turn

Fylom generates episodes like this on any topic you're curious about.

Fylom episodes are researched, written, and voiced by AI. Automated checks help catch inaccuracies, but episodes aren't reviewed by a human and AI can still get things wrong. Treat them as a starting point, not a source of record — more in our accuracy disclaimer.

The Leap Second That Froze the Web — Fylom