Y2K — the year-2000 computer collapse

That two-digit date fields in legacy computer systems would fail at midnight on 1 January 2000 and cause cascading infrastructure collapse.

The Y2K bug was a genuine software issue that governments and industry spent an estimated hundreds of billions of dollars remediating in the 1990s. Rollover night saw scattered, minor failures — not the infrastructure collapse popularly forecast.

Popular press, IT commentators, survivalist media — rumor / popular framing.

Mainstream newspapers, network television, and best-selling paperbacks carried Y2K into every household through 1998–99. A parallel survivalist media ecosystem forecast bank runs, blackouts, and food shortages.

WHY IT RESONATEDThe underlying bug was real and widely reported; a large, well-funded remediation effort by governments and industry primed the public to expect systemic risk on rollover night.

On 1 January 2000, isolated failures were logged — slot machines in Delaware, a nuclear-plant clock in Japan, incorrect due dates on video rentals — but no cascading infrastructure failure occurred. Retrospectives from the US GAO and academic historians attribute the quiet outcome primarily to years of coordinated remediation.

The maximalist collapse forecasts extrapolated from a real, bounded software bug to open-ended societal failure without engineering evidence, and ignored the very remediation programmes their own reporting described.

• US GAO — Year 2000 Computing Challenge (retrospective)Reference work
• Year 2000 problem — remediation and outcome (overview, with sourced citations)Reference work

• Friday, December 21, 2012·Mostly a Meme
  'Mayan' 2012 prophecy — end of the b'ak'tun
• Saturday, May 21, 2011·Religious Interpretation
  Harold Camping — 21 May 2011 Rapture prediction

Browse every dated entry on record — end of the world predictions by year, from historical failed apocalypses to upcoming doomsday dates.