Logged intothe wrongcloudaccountPracticedfailoverLoggedincident... tothe wrongteamRealized theDR testbrokesomethingelseSearchedTeams/WhatsApp/Slackfor the DR stepsRealized youwererestoring thewrong day’sbackupWrote aDR planno onereadGot calledduringdinnerCalledvendorsupport—hitvoicemailSaw amysteriouscron joblabeled “donot delete”Ran afailover,forgot thefirewall rulesIgnored analert thatwas realthis timeFoundcriticalsystem on apersonallaptopTestedDR... inprod byaccidentDependencyfailedsilentlyDidn’thave abackupCloudregiondownPower cameback... andthen wentout againSystem alertmissedbecause alertrule was toospecificDBmigrationfailedMisreada severityalertFix requiredphysicalaccess (noone hadkeys)Discoveredhalf the infrawas neverdocumentedConflictingrecoveryinstructionsDR testpassed...because noone actuallytested anythingDid apost-mortemExternalservicewentdownBackuppasswordwaschanged butnot sharedRestoredsuccessfully—into prodby mistakeHit restore,regrettedimmediatelySomeoneunpluggedthe “do nottouch” serverCreateda backupstrategyThe “hotsite” wasactuallycoldDeploymentbroke prodDiscoveredthe backupdrive wasfullBackupran... butdidn’t includethe databaseVendorsaid,“That’s notcovered”Couldn’treach theprimarycontactWoke upmidnightto standbycallFound thebackup inthe wrongformatRanchaos testin prodDR planincluded aretiredemployeeRecoverytook >1dayAlertfatigueOncallduring aholidayConfuseddev and prodenvironmentsAlertfalsepositiveBackuptape wascorruptedUnreachableDNSRestoredfrombackupRan a DRstimulationgameLost proddata(even abit)Customscriptfailed withno logsFoundpasswordsin a stickynoteAccidentallydeleteddataStarted aDR drill—no oneshowed upForgotto testbackupTeam usedfive differentdefinitions of“RTO”Networkoutage“Itworkedin dev”Deployedduring amajorincidentGot called mid-flight (tried totroubleshootover airplaneWi-Fi)Gotlocked outmid-recoverySpent 2hoursdebugging—then found itwas a typoDR testfailedAppliedthe wrongconfig toprodNorunbookavailableLogged intothe wrongcloudaccountPracticedfailoverLoggedincident... tothe wrongteamRealized theDR testbrokesomethingelseSearchedTeams/WhatsApp/Slackfor the DR stepsRealized youwererestoring thewrong day’sbackupWrote aDR planno onereadGot calledduringdinnerCalledvendorsupport—hitvoicemailSaw amysteriouscron joblabeled “donot delete”Ran afailover,forgot thefirewall rulesIgnored analert thatwas realthis timeFoundcriticalsystem on apersonallaptopTestedDR... inprod byaccidentDependencyfailedsilentlyDidn’thave abackupCloudregiondownPower cameback... andthen wentout againSystem alertmissedbecause alertrule was toospecificDBmigrationfailedMisreada severityalertFix requiredphysicalaccess (noone hadkeys)Discoveredhalf the infrawas neverdocumentedConflictingrecoveryinstructionsDR testpassed...because noone actuallytested anythingDid apost-mortemExternalservicewentdownBackuppasswordwaschanged butnot sharedRestoredsuccessfully—into prodby mistakeHit restore,regrettedimmediatelySomeoneunpluggedthe “do nottouch” serverCreateda backupstrategyThe “hotsite” wasactuallycoldDeploymentbroke prodDiscoveredthe backupdrive wasfullBackupran... butdidn’t includethe databaseVendorsaid,“That’s notcovered”Couldn’treach theprimarycontactWoke upmidnightto standbycallFound thebackup inthe wrongformatRanchaos testin prodDR planincluded aretiredemployeeRecoverytook >1dayAlertfatigueOncallduring aholidayConfuseddev and prodenvironmentsAlertfalsepositiveBackuptape wascorruptedUnreachableDNSRestoredfrombackupRan a DRstimulationgameLost proddata(even abit)Customscriptfailed withno logsFoundpasswordsin a stickynoteAccidentallydeleteddataStarted aDR drill—no oneshowed upForgotto testbackupTeam usedfive differentdefinitions of“RTO”Networkoutage“Itworkedin dev”Deployedduring amajorincidentGot called mid-flight (tried totroubleshootover airplaneWi-Fi)Gotlocked outmid-recoverySpent 2hoursdebugging—then found itwas a typoDR testfailedAppliedthe wrongconfig toprodNorunbookavailable

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