Latest / The Unseen With Adrianne / The Y2k Bug That Was Supposed To End The World
Transcript
- 0:00Speaker 1: Hey guys, welcome back to another episode of The Unseen
- 0:03Speaker 1: with Adrienne. Today we are talking about Y2K, the bug
- 0:09Speaker 1: that was supposed to end the world.
- 0:11Speaker 2: It's kind of a.
- 0:12Speaker 1: Little different, again, than what I've talked about in my
- 0:15Speaker 1: last episodes. It's not really like true crime related. It's
- 0:19Speaker 1: more like conspiracy and like mystery, but let's get into it.
- 0:24Speaker 1: 🎵 Now imagine it's December 31st, 1999. It's the final
- 0:36Speaker 1: night of the 20th century. People are throwing parties, fireworks
- 0:40Speaker 1: are ready to go off, and everyone is counting down
- 0:44Speaker 1: to year 2000. But somewhere in the back of your mind,
- 0:48Speaker 1: there's a terrifying thought. What if when the clock strikes midnight,
- 0:53Speaker 1: the world as we know it just stops? What if
- 0:57Speaker 1: the power goes out? What if the bank loses everybody's money?
- 1:01Speaker 1: What if airplanes suddenly have problems navigating? What if computers
- 1:05Speaker 1: controlling important systems start malfunctioning? And what if the tiny
- 1:09Speaker 1: little machines we've spent decades trusting to run our lives
- 1:13Speaker 1: suddenly can't figure out what.
- 1:15Speaker 2: Year it is?
- 1:16Speaker 1: That was the fear surrounding something called the Y2K bug.
- 1:21Speaker 1: And no, this wasn't some conspiracy theory floating around the internet.
- 1:25Speaker 1: This was a genuine technological problem that governments, major corporations, banks,
- 1:31Speaker 1: experts around the world spent years trying to fix.
- 1:35Speaker 2: I hadn't heard about this.
- 1:36Speaker 1: Until I watched a video about it and it just
- 1:41Speaker 1: blew my mind. Some people were prepared for the worst.
- 1:45Speaker 1: Some stock up on food, water, batteries, and emergency supplies.
- 1:50Speaker 1: Others thought the whole thing was ridiculous. And when midnight
- 1:54Speaker 1: finally arrived, the world watched. The clock hit 12, the
- 1:58Speaker 1: year changed, and nothing stopped. The lights stayed on, most
- 2:04Speaker 1: planes kept flying, the world entered the year 2000 without
- 2:08Speaker 1: the apocalyptic disaster that so many people were scared of.
- 2:13Speaker 2: So some people decided the whole thing was a hoax.
- 2:17Speaker 2: But this is the interesting part.
- 2:20Speaker 1: What if the person, what if the reason the world
- 2:24Speaker 1: didn't fall apart was that thousands of people had spent
- 2:27Speaker 1: years making sure it wouldn't? So we're going to talk
- 2:31Speaker 1: about the Y2K bug, what it was, why people thought
- 2:35Speaker 1: it would bring civilization to an end.
- 2:38Speaker 2: How the world prepared for it, and whether... We almost
- 2:43Speaker 2: avoided the world ending. Let's go back to where all began.
- 2:47Speaker 1: So to like fully understand Y2K, we need to go
- 2:51Speaker 1: back into the early days of computing. Think about the
- 2:55Speaker 1: computers we use today. You know, phones have enormous amounts
- 2:59Speaker 1: of storage. Laptops can process information at crazy speeds. We
- 3:04Speaker 1: can store thousands of photos, stream movies, and run programs
- 3:09Speaker 1: on devices that literally fit in our pockets. Now imagine
- 3:13Speaker 1: working with computers when storage was very expensive and limited.
- 3:19Speaker 1: Every little bit of memory mattered. And so back in
- 3:22Speaker 1: the 50s, 60s, and 70s, programmers had to be more
- 3:26Speaker 1: careful about how much space their programs used. One way
- 3:31Speaker 1: they saved space was by.
- 3:33Speaker 2: Shortening the date.
- 3:34Speaker 1: Instead of recording the year as 1965, a computer system
- 3:39Speaker 1: might store it as 65. Instead of 1978, it would
- 3:44Speaker 1: just be 78, and so.
- 3:46Speaker 2: On and so forth.
- 3:47Speaker 1: And so at the time, that was completely reasonable.
- 3:51Speaker 2: They were like, you know what, why not?
- 3:53Speaker 1: Why waste all that storage space recording the first two
- 3:57Speaker 1: digits of a year when everybody already knew which century
- 4:01Speaker 1: we were living in?
- 4:02Speaker 2: You know, that worked out for a while.
- 4:04Speaker 1: But the problem was that computers and software didn't always
- 4:08Speaker 1: understand the way the dates, the way humans did.
- 4:12Speaker 2: A person looking at the.
- 4:13Speaker 1: Number 99 could figure out that it probably meant 1999,
- 4:16Speaker 1: but a computer might simply just treat those two digits
- 4:21Speaker 1: as a number and use them in calculations.
- 4:23Speaker 2: And so then it became the year 2000.
- 4:25Speaker 1: If your computer stores the year using only two digits,
- 4:31Speaker 1: what does the year 2000 look like? It looks like 00.
- 4:34Speaker 1: And what happens if a program interprets 00 as 2000?
- 4:39Speaker 1: 1900 instead of 2000. Suddenly there's like an issue here
- 4:44Speaker 1: because like the computers don't know what their what year
- 4:47Speaker 1: it is.
- 4:48Speaker 2: They don't they're not like us.
- 4:50Speaker 1: They're just like they have code and stuff like it's
- 4:52Speaker 1: just different. So imagine you're running a bank and someone
- 4:56Speaker 1: takes out a mortgage in 1995.
- 4:59Speaker 2: Your computer records.
- 5:00Speaker 1: The date using two digits for the year. Now the
- 5:03Speaker 1: calendar rolls over to January 1st 2000. If the system
- 5:06Speaker 1: doesn't mistakenly interprets the date as January 1st, 1900, it
- 5:13Speaker 1: might calculate that the mortgage began a century ago. Depending
- 5:17Speaker 1: on how the program was written, it could produce incorrect
- 5:20Speaker 1: interest calculations, reject transactions, or who knows what else. Or
- 5:25Speaker 1: you could imagine a program that calculates someone's age using
- 5:29Speaker 1: the current year minus their birth year. If it reads
- 5:33Speaker 1: 00 as 1900, the results could be wrong. That could
- 5:37Speaker 1: create errors in scheduling, records, payments, and so many other things.
- 5:43Speaker 1: And one important detail, not every computer was guaranteed to
- 5:49Speaker 1: interpret 00 as 1900. Some systems had special rules that
- 5:56Speaker 1: Other years used four digit years or had already been
- 6:01Speaker 1: designed to handle the transition. But the problem was that
- 6:05Speaker 1: nobody could safely assume that they would all, you know,
- 6:09Speaker 1: behave correctly. And that was a real nightmare for the
- 6:16Speaker 1: people back then. Like the bug became known as Y2K
- 6:20Speaker 1: short for the year 2000.
- 6:23Speaker 2: It's also called.
- 6:24Speaker 1: The millennium bug. And the closer the world got to
- 6:27Speaker 1: the new millennium, the more people realized this just wasn't
- 6:31Speaker 1: an annoying little programming mistake. These old date formats had
- 6:35Speaker 1: found their way into systems that helped keep modern society running.
- 6:39Speaker 2: I mean, like computers are in everything.
- 6:42Speaker 1: Banks, insurance companies, government agencies, hospitals, like you name it,
- 6:47Speaker 1: there's a computer in there. And the shortcut had been
- 6:51Speaker 1: made decades earlier. And so now we're coming up to
- 6:56Speaker 1: the new millennium. Everybody's like, what are we going to
- 6:59Speaker 1: do about the computers? Like, are they going to crash? Like,
- 7:03Speaker 1: everybody was freaking out. A date might seem like one
- 7:07Speaker 1: of the easiest pieces of information a computer handles, but
- 7:12Speaker 1: dates are everywhere. Your bank needs dates to calculate interest
- 7:17Speaker 1: and determine when payments are due and An airline needs
- 7:20Speaker 1: dates to organize.
- 7:22Speaker 2: Flights and schedules. A hospital uses dates to.
- 7:25Speaker 1: Track patient information, maintenance, everything. Like these dates are everywhere.
- 7:32Speaker 1: And these systems don't operate independently. One computer might send
- 7:38Speaker 1: information to another. That second system might pass it along
- 7:41Speaker 1: to a third. If the information is wrong, an error
- 7:45Speaker 1: can spread. And that's why experts were worried about the
- 7:48Speaker 1: possibility of a chain reaction. A computer doesn't need to
- 7:52Speaker 1: explode or burst into flames to cause, you know, serious harm. Like,
- 7:57Speaker 1: sometimes all it takes is for a piece of software
- 8:00Speaker 1: to make the wrong decision. And the consequences depend on
- 8:04Speaker 1: what that software controls. So here's another example. A hospital
- 8:09Speaker 1: has an old computer system that stores dates incorrectly. A
- 8:13Speaker 1: patient record suddenly appears to have an impossible date. The
- 8:16Speaker 1: software refuses to process the record. There might be a
- 8:20Speaker 1: minor inconvenience if someone can correct it manually, but what
- 8:26Speaker 1: if the same kind of day errors occur in a
- 8:29Speaker 1: system that schedules important procedures, processes insurance claims, or manages
- 8:35Speaker 1: equipment maintenance? Now you're dealing with something a lot more serious.
- 8:40Speaker 1: The same logic applied to financial systems, utilities, transportation, government services. Like,
- 8:47Speaker 1: the concern wasn't that every machine on Earth would suddenly
- 8:52Speaker 1: stop working.
- 8:53Speaker 2: It was that.
- 8:54Speaker 1: Nobody knew how many systems contained vulnerable code, how those
- 9:00Speaker 1: systems would behave, or whether one failure could affect another.
- 9:04Speaker 1: Some equipment relied on embedded computer chips. Some software was
- 9:09Speaker 1: decades old. Some systems were maintained by organizations. It didn't
- 9:13Speaker 1: really fully stand all the programs that they depended on.
- 9:17Speaker 1: Even if a company knew... that it was an old
- 9:20Speaker 1: computer system, it might not know where the original source
- 9:24Speaker 1: code was or whether the people who wrote it were
- 9:28Speaker 1: like still available to help. So imagine being handed a
- 9:31Speaker 1: computer program that was written 30 years ago with thousands
- 9:36Speaker 1: of thousands code and being told you have to find
- 9:40Speaker 1: every date related problem before midnight on December 31st, 1999,
- 9:45Speaker 1: and you cannot get this wrong. And that was the challenge.
- 9:48Speaker 1: It wasn't happening in one building. It was happening everywhere.
- 9:52Speaker 1: The United States government treated Y2K as a major risk
- 9:57Speaker 1: to critical operations. Congress held hearings, government agencies tracked their progress,
- 10:04Speaker 1: and businesses.
- 10:05Speaker 2: Began inspecting their systems. The U.S.
- 10:09Speaker 1: Government Accountability Office identified Y2K as a high-risk issue in
- 10:16Speaker 1: 1997 because of.
- 10:17Speaker 2: The potential consequences.
- 10:20Speaker 1: And in other words, this wasn't just a bunch of
- 10:22Speaker 1: people worrying about computers for fun.
- 10:24Speaker 2: There were real problems to investigate.
- 10:28Speaker 1: But there was a huge difference between saying some computer
- 10:31Speaker 1: systems might fail and saying civilization is about to collapse.
- 10:36Speaker 2: As we get closer to.
- 10:37Speaker 1: 2000, those two ideas increasingly became more tangled together because
- 10:44Speaker 1: fear has a way of growing fear. when the thing
- 10:46Speaker 1: you're afraid of is complicated and difficult to predict. And
- 10:51Speaker 1: computers were already becoming the backbone of everyday life. So
- 10:56Speaker 1: in the late 90s, Y2K was becoming a household term.
- 11:01Speaker 1: News reports discussed it. Businesses warned customers about it. Computer
- 11:06Speaker 1: experts tried to explain it. Politicians asked whether the country
- 11:10Speaker 1: was prepared for this. And the public started asking some...
- 11:16Speaker 1: pretty reasonable questions. Would ATMs still work? Would people be
- 11:21Speaker 1: able to access their bank accounts? Would airplanes be safe?
- 11:25Speaker 1: Is the electricity going to go out? Like most importantly,
- 11:29Speaker 1: how much of this was like actually going to happen?
- 11:32Speaker 1: The problem was that nobody could give one answer that
- 11:36Speaker 1: applied to every computer system in the world. Because this
- 11:40Speaker 1: was happening worldwide. Some systems were already like compliant, like
- 11:45Speaker 1: they were okay. Others need simple fixes and some required
- 11:51Speaker 1: major upgrades. And some were so old or poorly documented
- 11:55Speaker 1: that testing them properly was a serious undertaking. That uncertainty
- 11:59Speaker 1: created the perfect environment for worst case scenarios.
- 12:03Speaker 2: Just picture the.
- 12:04Speaker 1: Headlines and television coverage of the era. The year 2000
- 12:08Speaker 1: wasn't just another January on the calendar. It represented the
- 12:12Speaker 1: start of a new millennium, and people were already thinking
- 12:16Speaker 1: symbolically about the end of an era. And then you
- 12:20Speaker 1: had a computer problem with a hard deadline, the possibility
- 12:23Speaker 1: of widespread disruptions, and the fact that most people have
- 12:27Speaker 1: no idea how the technology behind their electricity, banking, or
- 12:32Speaker 1: transportation systems evolved. actually work. It's a recipe for disaster.
- 12:37Speaker 1: And the Y2K scare became bigger than the original technical issue.
- 12:42Speaker 1: Some people worried about losing their money. Others imagine a
- 12:46Speaker 1: complete breakdown of the public infrastructure. Some survivalists prepared for
- 12:51Speaker 1: extended emergencies while apocalyptic predictions blended the bug with unrelated
- 12:57Speaker 1: fears about the end of the world. Businesses sold products
- 13:01Speaker 1: that were designed around Y2K concerns. Consultants started offering to
- 13:06Speaker 1: check systems. Companies marketed software as Y2K compliant. Emergency preparedness
- 13:13Speaker 1: products found an audience among people who feared the worst.
- 13:17Speaker 1: And of course, the media had a story that was
- 13:20Speaker 1: practically designed to attract attention. A mysterious technological problem, a
- 13:26Speaker 1: countdown to a fixed date, potentially enormous consequences, and everybody
- 13:31Speaker 1: was waiting to see what happened. But it's important to
- 13:34Speaker 1: not confuse the loudest predictions with the actual work being done.
- 13:39Speaker 1: Behind the headlines programmers were investigating old systems, rewriting code,
- 13:44Speaker 1: replacing equipment, and testing software. Governments were coordinating with businesses
- 13:49Speaker 1: in other countries. The danger wasn't really that every prediction
- 13:54Speaker 1: of catastrophe would become true. The danger was that enough
- 13:58Speaker 1: systems might fail to cause serious problems, you know, if
- 14:02Speaker 1: nobody prepared for it. The people responsible for keeping those
- 14:06Speaker 1: systems running couldn't just shrug and, you.
- 14:08Speaker 2: Know, hope for the best. They had a.
- 14:10Speaker 1: Lot of freaking work to do and they had to
- 14:13Speaker 1: finish before 1999 now let's go back to new year's
- 14:18Speaker 1: eve 1999 the final hours of the year for most
- 14:23Speaker 1: people this was a celebration you know it was the
- 14:26Speaker 1: end of the.
- 14:27Speaker 2: 1900s the beginning of a new millennium in.
- 14:30Speaker 1: Pop culture and a chance to welcome the new year
- 14:34Speaker 1: for the people responsible for computer systems it was um crazy,
- 14:40Speaker 1: massive operational tests. Organizations around the world had staff monitoring systems,
- 14:47Speaker 1: checking reports, and preparing to respond if something failed.
- 14:51Speaker 2: The key thing to remember is.
- 14:53Speaker 1: That midnight didn't arrive everywhere at the same moment. The
- 14:57Speaker 1: new year moves across time zones, beginning in places such
- 15:01Speaker 1: as the Pacific island nations and moving westward around the globe.
- 15:06Speaker 1: This meant there wasn't just one moment when everybody could relax.
- 15:12Speaker 1: As each region entered January 1st, organizations watch to see
- 15:17Speaker 1: whether their systems continued working correctly. Imagine sitting in a
- 15:21Speaker 1: control room on New Year's Eve. You've spent like months
- 15:25Speaker 1: testing old software and you've checked the equipment, you know,
- 15:28Speaker 1: you've had backup plans in place, but you can't guarantee
- 15:32Speaker 1: that every system would behave.
- 15:35Speaker 2: And now, you know, the time is here.
- 15:38Speaker 1: So the clock counts down and it's It's now Happy
- 15:43Speaker 1: New Year, the year is 2000, and the first thing
- 15:46Speaker 1: that happened was nothing unusual. Lights stayed on, phones worked,
- 15:52Speaker 1: people celebrated, most banking systems and other services continued operating.
- 15:59Speaker 1: The feared apocalypse did not happen. There was no blackout,
- 16:04Speaker 1: planes didn't fall out of the sky, banks didn't lose
- 16:07Speaker 1: their customers' records. The story wasn't quite simple as nothing happened.
- 16:12Speaker 1: Some Y2K-related problems were reported.
- 16:16Speaker 2: The U.S.
- 16:18Speaker 1: Government Accountability Office later documented issues affecting systems, including satellite-based
- 16:25Speaker 1: intelligence systems. His ground processing station temporarily failed after the rollover.
- 16:32Speaker 1: Backup procedures allowed operations to continue, and the system was
- 16:36Speaker 1: returned to full operations on January 3rd. There was some
- 16:40Speaker 1: also errors involving Medicare claims, including claims submitted with incorrect dates.
- 16:46Speaker 1: These weren't the civilization-ending disasters that had been feared, though. Like,
- 16:51Speaker 1: they were just evidence that the problem was real. That
- 16:55Speaker 1: really played a big role. A serious risk doesn't have
- 16:58Speaker 1: to produce a worldwide catastrophe to have been worth investigating.
- 17:04Speaker 1: At the same time, The fact that a problem was
- 17:07Speaker 1: possible didn't mean that every dramatic prediction was reasonable. So
- 17:11Speaker 1: was Y2K the bug that almost ended the Earth?
- 17:16Speaker 2: No, not literally.
- 17:17Speaker 1: There's no evidence that the world was on the brink
- 17:20Speaker 1: of being destroyed by a single date formatting error, but
- 17:24Speaker 1: it was a real technological problem with the potential to
- 17:28Speaker 1: disrupt important systems. and the response to it became one
- 17:32Speaker 1: of the largest coordinated technology preparation efforts of this era.
- 17:37Speaker 1: The fact that the disaster didn't happen is not proof
- 17:40Speaker 1: that the problem was imaginary. It's also not proof that
- 17:44Speaker 1: every catastrophic prediction was correct. The truth sits somewhere more
- 17:49Speaker 1: complicated between those two extremes. This story is just, like,
- 17:54Speaker 1: so fascinating. Like, we usually imagine disasters... as events that
- 18:00Speaker 1: happen suddenly with alarms and everything falling apart at once,
- 18:04Speaker 1: but sometimes the most important part of a potential disaster
- 18:09Speaker 1: is the work that happens before anyone notices there's a problem.
- 18:13Speaker 1: The repairs, the late nights, the testing, the people who
- 18:16Speaker 1: catch something before it goes wrong. Y2K reminds everybody that
- 18:20Speaker 1: technology doesn't simply work because we expect it to. like
- 18:25Speaker 1: anything can happen. It works because people build it, maintain it,
- 18:29Speaker 1: test it, and have to fix mistakes. The next time
- 18:32Speaker 1: that somebody tells you that a major disaster never happened,
- 18:35Speaker 1: so the warnings must have been fake, remember the story.
- 18:39Speaker 1: Sometimes the best evidence of successful preparation is that nothing
- 18:44Speaker 1: dramatic happens at all. And that is the story of
- 18:47Speaker 1: the Y2K bug, the computer problem that became a global panic,
- 18:52Speaker 1: the midnight countdown that had the world watching, and the
- 18:55Speaker 1: technological challenge that taught us just how much of modern
- 19:00Speaker 1: civilization depends.
- 19:02Speaker 2: On, you know, things we just never think about.
- 19:04Speaker 1: If you enjoyed this episode, share it with someone who
- 19:08Speaker 1: remembers the year 2000 or someone who wasn't even born
- 19:11Speaker 1: yet because I wasn't around for this time.
- 19:14Speaker 2: I had no idea this.
- 19:16Speaker 1: Was a thing until I watched a video about it.
- 19:18Speaker 1: And I'll see you guys next time on The Unseen
- 19:21Speaker 1: with Adrienne.
- 19:40Speaker 2: Thank you.