Y2K: The Bug That Didn't End the World
Two missing digits, more than $300 billion in repairs and a New Year's Eve the whole world held its breath for.
By the InterStalgia history desk · November 14, 2026
For decades, programmers saved space by storing years as two digits. 1985 was just 85. It made sense when memory was expensive and the year 2000 felt far away. The problem was simple: when the date rolled over from 99 to 00, a lot of software might decide it was 1900.
The warning
Experts had known about the issue for years, but in 1993 Peter de Jager wrote a three-page article for Computerworld called "Doomsday 2000." The New York Times later compared it to Paul Revere's midnight ride. Over the rest of the decade, governments and companies worked through their old code looking for two-digit dates.
The estimates got big fast. Some companies predicted that fixing the bug worldwide would cost between $400 billion and $600 billion. The total spent on Y2K preparation likely passed $300 billion.
Close calls in testing
Testing caused its own scares. On February 8, 1999, a technician at the Peach Bottom nuclear power plant in Pennsylvania, testing a system that monitored the reactor's control rods, accidentally changed the time on the plant's live computer instead of the test machine. There were also worries about September 9, 1999. Written as 9/9/99, it could be confused with 9999, a value many old programs used to mean an unknown date.
Midnight
When January 1, 2000, arrived, the problems were minor. In Japan, ticket machines at 13 train stations stopped working for a short time. Some systems displayed the year as 1900. Most of the world's computers simply kept working.
Because so little went wrong, some people decided the whole thing had been overhyped. The people who worked on it argued the opposite: nothing happened because thousands of programmers spent years making sure nothing would. It's hard to prove a disaster you prevented, which may be the most Y2K thing about Y2K.