System alertmissedbecause alertrule was toospecificHit restore,regrettedimmediatelyLoggedincident... tothe wrongteamVendorsaid,“That’s notcovered”Appliedthe wrongconfig toprodNetworkoutageDiscoveredhalf the infrawas neverdocumentedRealized youwererestoring thewrong day’sbackupSomeoneunpluggedthe “do nottouch” serverIgnored analert thatwas realthis timeCouldn’treach theprimarycontactGot called mid-flight (tried totroubleshootover airplaneWi-Fi)AccidentallydeleteddataPracticedfailoverWoke upmidnightto standbycallRestoredfrombackupOncallduring aholidayGot calledduringdinnerSearchedTeams/WhatsApp/Slackfor the DR stepsExternalservicewentdownTeam usedfive differentdefinitions of“RTO”Deploymentbroke prodStarted aDR drill—no oneshowed upDR testfailedPower cameback... andthen wentout againConfuseddev and prodenvironmentsUnreachableDNSRecoverytook >1dayRealized theDR testbrokesomethingelseCalledvendorsupport—hitvoicemailDependencyfailedsilentlyDeployedduring amajorincidentNorunbookavailable“Itworkedin dev”DR testpassed...because noone actuallytested anythingRan a DRstimulationgameRestoredsuccessfully—into prodby mistakeFoundpasswordsin a stickynoteBackuptape wascorruptedLost proddata(even abit)AlertfatigueCreateda backupstrategyFoundcriticalsystem on apersonallaptopCustomscriptfailed withno logsConflictingrecoveryinstructionsLogged intothe wrongcloudaccountRan afailover,forgot thefirewall rulesSaw amysteriouscron joblabeled “donot delete”The “hotsite” wasactuallycoldTestedDR... inprod byaccidentWrote aDR planno onereadForgotto testbackupDBmigrationfailedDR planincluded aretiredemployeeMisreada severityalertBackuppasswordwaschanged butnot sharedDid apost-mortemDiscoveredthe backupdrive wasfullGotlocked outmid-recoverySpent 2hoursdebugging—then found itwas a typoBackupran... butdidn’t includethe databaseRanchaos testin prodDidn’thave abackupFound thebackup inthe wrongformatCloudregiondownFix requiredphysicalaccess (noone hadkeys)AlertfalsepositiveSystem alertmissedbecause alertrule was toospecificHit restore,regrettedimmediatelyLoggedincident... tothe wrongteamVendorsaid,“That’s notcovered”Appliedthe wrongconfig toprodNetworkoutageDiscoveredhalf the infrawas neverdocumentedRealized youwererestoring thewrong day’sbackupSomeoneunpluggedthe “do nottouch” serverIgnored analert thatwas realthis timeCouldn’treach theprimarycontactGot called mid-flight (tried totroubleshootover airplaneWi-Fi)AccidentallydeleteddataPracticedfailoverWoke upmidnightto standbycallRestoredfrombackupOncallduring aholidayGot calledduringdinnerSearchedTeams/WhatsApp/Slackfor the DR stepsExternalservicewentdownTeam usedfive differentdefinitions of“RTO”Deploymentbroke prodStarted aDR drill—no oneshowed upDR testfailedPower cameback... andthen wentout againConfuseddev and prodenvironmentsUnreachableDNSRecoverytook >1dayRealized theDR testbrokesomethingelseCalledvendorsupport—hitvoicemailDependencyfailedsilentlyDeployedduring amajorincidentNorunbookavailable“Itworkedin dev”DR testpassed...because noone actuallytested anythingRan a DRstimulationgameRestoredsuccessfully—into prodby mistakeFoundpasswordsin a stickynoteBackuptape wascorruptedLost proddata(even abit)AlertfatigueCreateda backupstrategyFoundcriticalsystem on apersonallaptopCustomscriptfailed withno logsConflictingrecoveryinstructionsLogged intothe wrongcloudaccountRan afailover,forgot thefirewall rulesSaw amysteriouscron joblabeled “donot delete”The “hotsite” wasactuallycoldTestedDR... inprod byaccidentWrote aDR planno onereadForgotto testbackupDBmigrationfailedDR planincluded aretiredemployeeMisreada severityalertBackuppasswordwaschanged butnot sharedDid apost-mortemDiscoveredthe backupdrive wasfullGotlocked outmid-recoverySpent 2hoursdebugging—then found itwas a typoBackupran... butdidn’t includethe databaseRanchaos testin prodDidn’thave abackupFound thebackup inthe wrongformatCloudregiondownFix requiredphysicalaccess (noone hadkeys)Alertfalsepositive

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