Legend Mode
History's greatest outages,
as case files.
Every incident here is a real, publicly-documented event. Solve the case, then read the source: SEC filings, postmortems, news coverage.
Industry
Crowdstrike — 8.5M Windows machines bricked
~8.5M endpoints down · airlines grounded · hospitals scrambling
A content update for the Falcon sensor shipped a malformed channel file. The kernel driver dereferenced an invalid pointer, hitting BSOD on every boot. Because the driver loaded before users could even log in, recovery required physical access — a global airline-grounding, hospital-paging Friday.
Industry
Facebook — BGP withdrew the company from the internet
~6 hours · FB / IG / WhatsApp / internal tools offline
A routine maintenance command unintentionally withdrew the BGP routes that announced Facebook's DNS servers to the rest of the internet. DNS dying took down everything that depended on it — including the internal tools and badge readers needed to physically access the data centers and fix the problem.
Amazon
AWS S3 us-east-1 — typo took out half the internet
~4 hours down · S3, EC2, console, half the web
An engineer running a debugging playbook fat-fingered a parameter. A command intended to take a few servers offline took down a much larger set, including subsystems that powered S3's indexing in us-east-1. The cascade was visible across half the consumer web for hours.
Industry
GitLab — rm -rf'd the production database
6 hours data lost · 5 of 5 backup methods failed
An on-call engineer trying to fix replication accidentally ran the wipe command on the primary DB instead of the replica. Then came the discovery: none of the five backup mechanisms actually worked. The team live-streamed the recovery on YouTube while restoring from a 6-hour-old snapshot found by accident.
Industry
Knight Capital — $440M in 45 minutes
$440M lost in 45 min · firm bankrupt
A retired feature flag named 'Power Peg' was repurposed for a new SMARS router. Eight servers got the new code; one didn't. On market open, the unupdated server ran Power Peg's 9-year-old logic against live orders, blasting market-makers with errant trades. By the time the team isolated the bad server, Knight had eaten a $440M loss and would be sold inside a year.