Gotlocked outmid-recoveryRestoredsuccessfully—into prodby mistakeAlertfalsepositiveFoundcriticalsystem on apersonallaptopOncallduring aholidayWrote aDR planno oneread“Itworkedin dev”Ran afailover,forgot thefirewall rulesDR testpassed...because noone actuallytested anythingCreateda backupstrategyBackuptape wascorruptedFix requiredphysicalaccess (noone hadkeys)Vendorsaid,“That’s notcovered”Started aDR drill—no oneshowed upGot called mid-flight (tried totroubleshootover airplaneWi-Fi)AccidentallydeleteddataSomeoneunpluggedthe “do nottouch” serverDependencyfailedsilentlyRanchaos testin prodSearchedTeams/WhatsApp/Slackfor the DR stepsRecoverytook >1dayTeam usedfive differentdefinitions of“RTO”CloudregiondownDid apost-mortemRan a DRstimulationgameUnreachableDNSConflictingrecoveryinstructionsBackuppasswordwaschanged butnot sharedAppliedthe wrongconfig toprodAlertfatigueDiscoveredthe backupdrive wasfullTestedDR... inprod byaccidentIgnored analert thatwas realthis timeConfuseddev and prodenvironmentsLost proddata(even abit)Deploymentbroke prodFoundpasswordsin a stickynotePracticedfailoverNetworkoutageGot calledduringdinnerPower cameback... andthen wentout againFound thebackup inthe wrongformatCouldn’treach theprimarycontactCalledvendorsupport—hitvoicemailNorunbookavailableRestoredfrombackupDR testfailedSaw amysteriouscron joblabeled “donot delete”Logged intothe wrongcloudaccountLoggedincident... tothe wrongteamDiscoveredhalf the infrawas neverdocumentedRealized theDR testbrokesomethingelseSpent 2hoursdebugging—then found itwas a typoDBmigrationfailedSystem alertmissedbecause alertrule was toospecificThe “hotsite” wasactuallycoldHit restore,regrettedimmediatelyExternalservicewentdownRealized youwererestoring thewrong day’sbackupDR planincluded aretiredemployeeWoke upmidnightto standbycallCustomscriptfailed withno logsForgotto testbackupBackupran... butdidn’t includethe databaseMisreada severityalertDeployedduring amajorincidentDidn’thave abackupGotlocked outmid-recoveryRestoredsuccessfully—into prodby mistakeAlertfalsepositiveFoundcriticalsystem on apersonallaptopOncallduring aholidayWrote aDR planno oneread“Itworkedin dev”Ran afailover,forgot thefirewall rulesDR testpassed...because noone actuallytested anythingCreateda backupstrategyBackuptape wascorruptedFix requiredphysicalaccess (noone hadkeys)Vendorsaid,“That’s notcovered”Started aDR drill—no oneshowed upGot called mid-flight (tried totroubleshootover airplaneWi-Fi)AccidentallydeleteddataSomeoneunpluggedthe “do nottouch” serverDependencyfailedsilentlyRanchaos testin prodSearchedTeams/WhatsApp/Slackfor the DR stepsRecoverytook >1dayTeam usedfive differentdefinitions of“RTO”CloudregiondownDid apost-mortemRan a DRstimulationgameUnreachableDNSConflictingrecoveryinstructionsBackuppasswordwaschanged butnot sharedAppliedthe wrongconfig toprodAlertfatigueDiscoveredthe backupdrive wasfullTestedDR... inprod byaccidentIgnored analert thatwas realthis timeConfuseddev and prodenvironmentsLost proddata(even abit)Deploymentbroke prodFoundpasswordsin a stickynotePracticedfailoverNetworkoutageGot calledduringdinnerPower cameback... andthen wentout againFound thebackup inthe wrongformatCouldn’treach theprimarycontactCalledvendorsupport—hitvoicemailNorunbookavailableRestoredfrombackupDR testfailedSaw amysteriouscron joblabeled “donot delete”Logged intothe wrongcloudaccountLoggedincident... tothe wrongteamDiscoveredhalf the infrawas neverdocumentedRealized theDR testbrokesomethingelseSpent 2hoursdebugging—then found itwas a typoDBmigrationfailedSystem alertmissedbecause alertrule was toospecificThe “hotsite” wasactuallycoldHit restore,regrettedimmediatelyExternalservicewentdownRealized youwererestoring thewrong day’sbackupDR planincluded aretiredemployeeWoke upmidnightto standbycallCustomscriptfailed withno logsForgotto testbackupBackupran... butdidn’t includethe databaseMisreada severityalertDeployedduring amajorincidentDidn’thave abackup

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