Woke upmidnightto standbycallDiscoveredthe backupdrive wasfullAppliedthe wrongconfig toprodDependencyfailedsilentlyFoundcriticalsystem on apersonallaptopCreateda backupstrategyRealized theDR testbrokesomethingelseMisreada severityalertAccidentallydeleteddataSaw amysteriouscron joblabeled “donot delete”Forgotto testbackupTeam usedfive differentdefinitions of“RTO”Did apost-mortemDeployedduring amajorincidentAlertfatigueCouldn’treach theprimarycontactSpent 2hoursdebugging—then found itwas a typoWrote aDR planno onereadNorunbookavailableDR testpassed...because noone actuallytested anythingFoundpasswordsin a stickynotePower cameback... andthen wentout againCalledvendorsupport—hitvoicemailLost proddata(even abit)Discoveredhalf the infrawas neverdocumentedCustomscriptfailed withno logsSystem alertmissedbecause alertrule was toospecificAlertfalsepositiveDR testfailedRestoredfrombackupSomeoneunpluggedthe “do nottouch” serverRecoverytook >1dayCloudregiondownDR planincluded aretiredemployeeRan afailover,forgot thefirewall rulesHit restore,regrettedimmediatelyConflictingrecoveryinstructionsFound thebackup inthe wrongformatDidn’thave abackupFix requiredphysicalaccess (noone hadkeys)TestedDR... inprod byaccidentRestoredsuccessfully—into prodby mistakeSearchedTeams/WhatsApp/Slackfor the DR steps“Itworkedin dev”Ignored analert thatwas realthis timeConfuseddev and prodenvironmentsGot calledduringdinnerBackuptape wascorruptedOncallduring aholidayGotlocked outmid-recoveryVendorsaid,“That’s notcovered”Logged intothe wrongcloudaccountExternalservicewentdownLoggedincident... tothe wrongteamPracticedfailoverStarted aDR drill—no oneshowed upDBmigrationfailedThe “hotsite” wasactuallycoldRan a DRstimulationgameBackuppasswordwaschanged butnot sharedRealized youwererestoring thewrong day’sbackupBackupran... butdidn’t includethe databaseGot called mid-flight (tried totroubleshootover airplaneWi-Fi)Deploymentbroke prodNetworkoutageUnreachableDNSRanchaos testin prodWoke upmidnightto standbycallDiscoveredthe backupdrive wasfullAppliedthe wrongconfig toprodDependencyfailedsilentlyFoundcriticalsystem on apersonallaptopCreateda backupstrategyRealized theDR testbrokesomethingelseMisreada severityalertAccidentallydeleteddataSaw amysteriouscron joblabeled “donot delete”Forgotto testbackupTeam usedfive differentdefinitions of“RTO”Did apost-mortemDeployedduring amajorincidentAlertfatigueCouldn’treach theprimarycontactSpent 2hoursdebugging—then found itwas a typoWrote aDR planno onereadNorunbookavailableDR testpassed...because noone actuallytested anythingFoundpasswordsin a stickynotePower cameback... andthen wentout againCalledvendorsupport—hitvoicemailLost proddata(even abit)Discoveredhalf the infrawas neverdocumentedCustomscriptfailed withno logsSystem alertmissedbecause alertrule was toospecificAlertfalsepositiveDR testfailedRestoredfrombackupSomeoneunpluggedthe “do nottouch” serverRecoverytook >1dayCloudregiondownDR planincluded aretiredemployeeRan afailover,forgot thefirewall rulesHit restore,regrettedimmediatelyConflictingrecoveryinstructionsFound thebackup inthe wrongformatDidn’thave abackupFix requiredphysicalaccess (noone hadkeys)TestedDR... inprod byaccidentRestoredsuccessfully—into prodby mistakeSearchedTeams/WhatsApp/Slackfor the DR steps“Itworkedin dev”Ignored analert thatwas realthis timeConfuseddev and prodenvironmentsGot calledduringdinnerBackuptape wascorruptedOncallduring aholidayGotlocked outmid-recoveryVendorsaid,“That’s notcovered”Logged intothe wrongcloudaccountExternalservicewentdownLoggedincident... tothe wrongteamPracticedfailoverStarted aDR drill—no oneshowed upDBmigrationfailedThe “hotsite” wasactuallycoldRan a DRstimulationgameBackuppasswordwaschanged butnot sharedRealized youwererestoring thewrong day’sbackupBackupran... butdidn’t includethe databaseGot called mid-flight (tried totroubleshootover airplaneWi-Fi)Deploymentbroke prodNetworkoutageUnreachableDNSRanchaos testin prod

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