incident_001.case
CASE FILE / 001SYSTEM_THREAD_EXCEPTIONGlobaloperational disruption+
CrowdStrike
The update that stopped the world.
A routine security update. A worldwide cascade of blue screens.
Open case file ↗CrashOS / museum edition ALL SYSTEMS: QUESTIONABLE
am I the bug?ORIGINAL CONCEPT ART / CLICK THE LITTLE WEIRDO
THE MUSEUM OF DIGITAL CATASTROPHESEverything is
Everything is
fine. on fire.
Real failures. Unbelievable consequences. Meet the bugs, bad calls, and broken assumptions that changed our digital world.
Open the archive ↗Not sure where to start? Follow a trail →$460 million.
45 minutes.Knight Capital / open the case file ↗
45 minutes.Knight Capital / open the case file ↗
12 REAL CASES / ZERO PERFECT SYSTEMSthat’s all folks
12source-linked case files
4curated reading trails
4hands-on rehearsals
Facts first. Lessons that last. How we build the archive ↗
CASE FILE 002 / KNIGHT CAPITAL
45 minutes.
$460 million gone.
Dormant code. An incomplete deployment. A trading system that wouldn’t stop. Follow the chain of failure—and the safeguards that were missing.
RECOVERED FILES / THE COLLECTION
Three more ways things broke.
incident_003.case
CASE FILE / 003UNIT_CONVERSION_FAILED1 spacecraftmission lost+
Mars Climate Orbiter
Lost in translation. Somewhere near Mars.
Two teams. Two unit systems. One spacecraft that never came home.
Open case file ↗incident_004.case
CASE FILE / 004RECOVERY_POINT_NOT_FOUND6 hoursdatabase data lost+
GitLab
The backup plan needed a backup plan.
A deleted production database revealed a much bigger recovery problem.
Open case file ↗THE DISASTER LAB / YOUR TURN
History repeats.
Practice first.
Choose your kind of trouble.
Rehearse a fictional incident, or examine the safeguards in your own system.
FICTIONAL INCIDENTS3–5 MIN
A safe place
for a very bad day.
The release is live. Something is wrong. What do you do next?
SCENARIO PREVIEW
09:41 Orders start behaving strangely.
09:43 The alerts keep coming.
Your next decision matters.
Choose a scenario→Make the calls→Get a debrief
Choose a rehearsal 4 scenarios · releases, recovery, commerce & dependencies
YOUR SYSTEM, YOUR EVIDENCE4 SAFEGUARDS
Find the cracks.
Make a plan.
Look beyond “we should be fine.” What have you actually tested?
- 01RecoveryCan you get your data back?
- 02ReleasesCan you contain a bad change?
- 03DependenciesWill your fallback really work?
- 04InterfacesDo both sides agree?
Leave with evidence gaps, next steps, and an editable action plan.
NO PRODUCTION ACCESS
Authored rehearsals and self-reported reviews. No scanning, no predictions, no live AI.
KEEP INVESTIGATING