January 4 – The Day Computers Ran Out of Time

0:00 Speaker 1: Welcome back, dear listeners to the Strange History Podcast, where

0:03 Speaker 1: history reminds us that humanity didn't just invent technology, we

0:07 Speaker 1: also invented incredibly creative ways for it to fail. Today

0:11 Speaker 1: is January fourth, and this is the story of a

0:14 Speaker 1: moment when computers, powerful, confident, very expensive computers suddenly realized

0:21 Speaker 1: they could not count high enough to handle the future.

0:24 Speaker 1: And when that happened, everything quietly broke when time became

0:29 Speaker 1: a technical problem. By the early nineteen seventies, computers were

0:34 Speaker 1: no longer rare lab curiosities, governments, universities, and corporations were

0:40 Speaker 1: using massive shared systems to run payroll, research, communications, and

0:46 Speaker 1: military planning. These machines filled rooms, required special cooling, and

0:51 Speaker 1: spoke languages only a handful of humans truly understood. One

0:56 Speaker 1: of the most popular operating systems at the time was

0:59 Speaker 1: called TOPS ten, used primarily on dec mainframes. It handled

1:05 Speaker 1: time in a very simple way by counting seconds. The

1:08 Speaker 1: problem it could only count so many. Time, unfortunately, does

1:13 Speaker 1: not stop cooperating just because your computer has a limit.

1:17 Speaker 1: January fourth, nineteen seventy five, midnight arrives, and so does chaos.

1:24 Speaker 1: On January fourth, nineteen seventy five, systems running tops ten

1:28 Speaker 1: reached a number they were never designed to handle. The

1:31 Speaker 1: internal clock hit its maximum value and then rolled over

1:35 Speaker 1: to zero. To the computer, this didn't mean the future.

1:39 Speaker 1: It meant time no longer made sense. Suddenly, processes thought

1:44 Speaker 1: they were running in the past. Scheduled tasks fired at

1:47 Speaker 1: the wrong moment or not at all. Files appeared to

1:51 Speaker 1: be created before they existed. Time based permissions broke. Logs

1:56 Speaker 1: became nonsense. Nothing exploded, no alarms bladed aired. Things just

2:02 Speaker 1: stopped working correctly. Engineers stared at terminals, wondering how the

2:06 Speaker 1: most fundamental concept, time had betrayed them. The strange part,

2:12 Speaker 1: this wasn't a bug. It was a design choice. Here's

2:15 Speaker 1: what makes this so fascinating. No one forgot about the future.

2:20 Speaker 1: They simply didn't expect their systems to still be running.

2:24 Speaker 1: In the nineteen sixties and early seventies, computers were upgraded, replaced,

2:29 Speaker 1: or retired frequently. The idea that one operating system would

2:33 Speaker 1: survive long enough to hit a time limit felt unrealistic,

2:37 Speaker 1: but technology stuck around and time kept moving. This wasn't

2:43 Speaker 1: an isolated incident either. Other systems across the world began

2:47 Speaker 1: encountering similar problems as their internal clocks reached arbitrary limits.

2:52 Speaker 1: Engineers quietly patched, reset, or rewrote code, often without the

2:57 Speaker 1: public ever noticing. Recalls these events time rollover bugs, and

3:02 Speaker 1: January fourth stands as one of the earliest real warnings

3:06 Speaker 1: the ghost of problems yet to come. If this story

3:10 Speaker 1: feels familiar, that's because it should. January fourth, nineteen seventy

3:16 Speaker 1: five was an early cousin of the Y two K problem,

3:20 Speaker 1: when computers stored years as two digits and panicked at

3:23 Speaker 1: the arrival of zero zero. It's also related to the

3:27 Speaker 1: year twenty thirty eight problem, when Unix based systems will

3:31 Speaker 1: face another time overflow. In other words, we keep doing this.

3:35 Speaker 1: We build systems that assume the future will politely wait.

3:40 Speaker 1: It never does. A quiet disaster that shaped modern computing.

3:46 Speaker 1: Unlike nuclear accidents or space failures, this event didn't leave

3:50 Speaker 1: craters or headlines, but it left something arguably more important,

3:54 Speaker 1: a lesson. Engineers began designing systems with longer time horizons.

4:00 Speaker 1: Programmers became painfully aware that shortcuts taken today turn into

4:04 Speaker 1: disasters tomorrow, and somewhere in the collective memory of computing.

4:09 Speaker 1: January fourth became a cautionary tale whispered in server rooms.

4:14 Speaker 1: The future will arrive, ready or not. Before we wrap

4:19 Speaker 1: up today's episode, a word from our sponsor, because apparently

4:23 Speaker 1: even time needs better planning.

4:25 Speaker 2: This episode is brought to you by Time Sure Future

4:28 Speaker 2: Proof Calendars, the only calendar system guaranteed to work past ay.

4:32 Speaker 2: We'll fix it later. Time Shore calendars come preloaded with

4:37 Speaker 2: leapy years accounted for century changes included absolutely zero assumptions

4:42 Speaker 2: that civilization will end by Friday. Perfect for programmers, planners,

4:47 Speaker 2: and anyone who has ever said we'll cross that bridge

4:50 Speaker 2: when we get there, only to realize the bridge expired

4:53 Speaker 2: in nineteen seventy five. Time Sure, because the future is coming,

4:57 Speaker 2: whether your code is ready or not. Use promo co

5:00 Speaker 2: what year is it? For ten percent off and a

5:03 Speaker 2: free reminder that time is relentless.

5:05 Speaker 1: And that, dear listeners, is your strange history. Entry for

5:08 Speaker 1: January fourth, the day computers discovered that time waits for

5:13 Speaker 1: no machine. Join me tomorrow for January fifth, when astronomers

5:17 Speaker 1: find something so big and strange it accidentally knocks Pluto

5:21 Speaker 1: out of planetary status. Until then, keep your clocks updated,

5:26 Speaker 1: your assumptions checked, and your systems ready for tomorrow,