Ranchaos testin prodDBmigrationfailedHit restore,regrettedimmediatelyFoundcriticalsystem on apersonallaptopVendorsaid,“That’s notcovered”Forgotto testbackupAlertfalsepositiveSaw amysteriouscron joblabeled “donot delete”Ran a DRstimulationgameAlertfatigueDiscoveredthe backupdrive wasfullCloudregiondownPracticedfailoverCouldn’treach theprimarycontactExternalservicewentdownDR planincluded aretiredemployeeMisreada severityalertDeploymentbroke prodCustomscriptfailed withno logsConfuseddev and prodenvironmentsRestoredfrombackupWrote aDR planno onereadDid apost-mortemDiscoveredhalf the infrawas neverdocumentedTestedDR... inprod byaccidentSpent 2hoursdebugging—then found itwas a typoDR testfailedBackuptape wascorruptedConflictingrecoveryinstructionsDidn’thave abackupLoggedincident... tothe wrongteamAccidentallydeleteddataCalledvendorsupport—hitvoicemailWoke upmidnightto standbycallAppliedthe wrongconfig toprod“Itworkedin dev”Ignored analert thatwas realthis timeBackupran... butdidn’t includethe databaseGotlocked outmid-recoveryFix requiredphysicalaccess (noone hadkeys)System alertmissedbecause alertrule was toospecificSomeoneunpluggedthe “do nottouch” serverThe “hotsite” wasactuallycoldBackuppasswordwaschanged butnot sharedPower cameback... andthen wentout againStarted aDR drill—no oneshowed upNorunbookavailableUnreachableDNSNetworkoutageGot called mid-flight (tried totroubleshootover airplaneWi-Fi)Realized theDR testbrokesomethingelseFound thebackup inthe wrongformatDeployedduring amajorincidentFoundpasswordsin a stickynoteSearchedTeams/WhatsApp/Slackfor the DR stepsRan afailover,forgot thefirewall rulesRecoverytook >1dayRealized youwererestoring thewrong day’sbackupRestoredsuccessfully—into prodby mistakeLogged intothe wrongcloudaccountDependencyfailedsilentlyGot calledduringdinnerDR testpassed...because noone actuallytested anythingOncallduring aholidayTeam usedfive differentdefinitions of“RTO”Createda backupstrategyLost proddata(even abit)Ranchaos testin prodDBmigrationfailedHit restore,regrettedimmediatelyFoundcriticalsystem on apersonallaptopVendorsaid,“That’s notcovered”Forgotto testbackupAlertfalsepositiveSaw amysteriouscron joblabeled “donot delete”Ran a DRstimulationgameAlertfatigueDiscoveredthe backupdrive wasfullCloudregiondownPracticedfailoverCouldn’treach theprimarycontactExternalservicewentdownDR planincluded aretiredemployeeMisreada severityalertDeploymentbroke prodCustomscriptfailed withno logsConfuseddev and prodenvironmentsRestoredfrombackupWrote aDR planno onereadDid apost-mortemDiscoveredhalf the infrawas neverdocumentedTestedDR... inprod byaccidentSpent 2hoursdebugging—then found itwas a typoDR testfailedBackuptape wascorruptedConflictingrecoveryinstructionsDidn’thave abackupLoggedincident... tothe wrongteamAccidentallydeleteddataCalledvendorsupport—hitvoicemailWoke upmidnightto standbycallAppliedthe wrongconfig toprod“Itworkedin dev”Ignored analert thatwas realthis timeBackupran... butdidn’t includethe databaseGotlocked outmid-recoveryFix requiredphysicalaccess (noone hadkeys)System alertmissedbecause alertrule was toospecificSomeoneunpluggedthe “do nottouch” serverThe “hotsite” wasactuallycoldBackuppasswordwaschanged butnot sharedPower cameback... andthen wentout againStarted aDR drill—no oneshowed upNorunbookavailableUnreachableDNSNetworkoutageGot called mid-flight (tried totroubleshootover airplaneWi-Fi)Realized theDR testbrokesomethingelseFound thebackup inthe wrongformatDeployedduring amajorincidentFoundpasswordsin a stickynoteSearchedTeams/WhatsApp/Slackfor the DR stepsRan afailover,forgot thefirewall rulesRecoverytook >1dayRealized youwererestoring thewrong day’sbackupRestoredsuccessfully—into prodby mistakeLogged intothe wrongcloudaccountDependencyfailedsilentlyGot calledduringdinnerDR testpassed...because noone actuallytested anythingOncallduring aholidayTeam usedfive differentdefinitions of“RTO”Createda backupstrategyLost proddata(even abit)

Disasters Bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
  1. Ran chaos test in prod
  2. DB migration failed
  3. Hit restore, regretted immediately
  4. Found critical system on a personal laptop
  5. Vendor said, “That’s not covered”
  6. Forgot to test backup
  7. Alert false positive
  8. Saw a mysterious cron job labeled “do not delete”
  9. Ran a DR stimulation game
  10. Alert fatigue
  11. Discovered the backup drive was full
  12. Cloud region down
  13. Practiced failover
  14. Couldn’t reach the primary contact
  15. External service went down
  16. DR plan included a retired employee
  17. Misread a severity alert
  18. Deployment broke prod
  19. Custom script failed with no logs
  20. Confused dev and prod environments
  21. Restored from backup
  22. Wrote a DR plan no one read
  23. Did a post-mortem
  24. Discovered half the infra was never documented
  25. Tested DR... in prod by accident
  26. Spent 2 hours debugging—then found it was a typo
  27. DR test failed
  28. Backup tape was corrupted
  29. Conflicting recovery instructions
  30. Didn’t have a backup
  31. Logged incident... to the wrong team
  32. Accidentally deleted data
  33. Called vendor support—hit voicemail
  34. Woke up midnight to standby call
  35. Applied the wrong config to prod
  36. “It worked in dev”
  37. Ignored an alert that was real this time
  38. Backup ran... but didn’t include the database
  39. Got locked out mid-recovery
  40. Fix required physical access (no one had keys)
  41. System alert missed because alert rule was too specific
  42. Someone unplugged the “do not touch” server
  43. The “hot site” was actually cold
  44. Backup password was changed but not shared
  45. Power came back... and then went out again
  46. Started a DR drill—no one showed up
  47. No runbook available
  48. Unreachable DNS
  49. Network outage
  50. Got called mid-flight (tried to troubleshoot over airplane Wi-Fi)
  51. Realized the DR test broke something else
  52. Found the backup in the wrong format
  53. Deployed during a major incident
  54. Found passwords in a sticky note
  55. Searched Teams/WhatsApp/Slack for the DR steps
  56. Ran a failover, forgot the firewall rules
  57. Recovery took >1 day
  58. Realized you were restoring the wrong day’s backup
  59. Restored successfully—into prod by mistake
  60. Logged into the wrong cloud account
  61. Dependency failed silently
  62. Got called during dinner
  63. DR test passed... because no one actually tested anything
  64. Oncall during a holiday
  65. Team used five different definitions of “RTO”
  66. Created a backup strategy
  67. Lost prod data (even a bit)