Didn’thave abackupGotlocked outmid-recoveryMisreada severityalertLogged intothe wrongcloudaccountWoke upmidnightto standbycallBackupran... butdidn’t includethe databaseOncallduring aholidayThe “hotsite” wasactuallycoldRestoredsuccessfully—into prodby mistakeGot called mid-flight (tried totroubleshootover airplaneWi-Fi)Ignored analert thatwas realthis timeLoggedincident... tothe wrongteamDiscoveredhalf the infrawas neverdocumentedCouldn’treach theprimarycontactSearchedTeams/WhatsApp/Slackfor the DR stepsTeam usedfive differentdefinitions of“RTO”Confuseddev and prodenvironmentsExternalservicewentdownRanchaos testin prodRealized youwererestoring thewrong day’sbackupRan afailover,forgot thefirewall rulesTestedDR... inprod byaccidentDR planincluded aretiredemployeeFix requiredphysicalaccess (noone hadkeys)Someoneunpluggedthe “do nottouch” serverSpent 2hoursdebugging—then found itwas a typoStarted aDR drill—no oneshowed upForgotto testbackupAppliedthe wrongconfig toprodNetworkoutageFoundpasswordsin a stickynoteGot calledduringdinnerBackuptape wascorruptedRealized theDR testbrokesomethingelseRan a DRstimulationgame“Itworkedin dev”AccidentallydeleteddataDR testpassed...because noone actuallytested anythingCloudregiondownSystem alertmissedbecause alertrule was toospecificAlertfatiguePower cameback... andthen wentout againDiscoveredthe backupdrive wasfullWrote aDR planno onereadCustomscriptfailed withno logsCreateda backupstrategyRecoverytook >1dayFoundcriticalsystem on apersonallaptopFound thebackup inthe wrongformatDid apost-mortemNorunbookavailableUnreachableDNSCalledvendorsupport—hitvoicemailRestoredfrombackupLost proddata(even abit)DependencyfailedsilentlyBackuppasswordwaschanged butnot sharedConflictingrecoveryinstructionsHit restore,regrettedimmediatelyAlertfalsepositiveDeploymentbroke prodDR testfailedDBmigrationfailedPracticedfailoverDeployedduring amajorincidentVendorsaid,“That’s notcovered”Saw amysteriouscron joblabeled “donot delete”Didn’thave abackupGotlocked outmid-recoveryMisreada severityalertLogged intothe wrongcloudaccountWoke upmidnightto standbycallBackupran... butdidn’t includethe databaseOncallduring aholidayThe “hotsite” wasactuallycoldRestoredsuccessfully—into prodby mistakeGot called mid-flight (tried totroubleshootover airplaneWi-Fi)Ignored analert thatwas realthis timeLoggedincident... tothe wrongteamDiscoveredhalf the infrawas neverdocumentedCouldn’treach theprimarycontactSearchedTeams/WhatsApp/Slackfor the DR stepsTeam usedfive differentdefinitions of“RTO”Confuseddev and prodenvironmentsExternalservicewentdownRanchaos testin prodRealized youwererestoring thewrong day’sbackupRan afailover,forgot thefirewall rulesTestedDR... inprod byaccidentDR planincluded aretiredemployeeFix requiredphysicalaccess (noone hadkeys)Someoneunpluggedthe “do nottouch” serverSpent 2hoursdebugging—then found itwas a typoStarted aDR drill—no oneshowed upForgotto testbackupAppliedthe wrongconfig toprodNetworkoutageFoundpasswordsin a stickynoteGot calledduringdinnerBackuptape wascorruptedRealized theDR testbrokesomethingelseRan a DRstimulationgame“Itworkedin dev”AccidentallydeleteddataDR testpassed...because noone actuallytested anythingCloudregiondownSystem alertmissedbecause alertrule was toospecificAlertfatiguePower cameback... andthen wentout againDiscoveredthe backupdrive wasfullWrote aDR planno onereadCustomscriptfailed withno logsCreateda backupstrategyRecoverytook >1dayFoundcriticalsystem on apersonallaptopFound thebackup inthe wrongformatDid apost-mortemNorunbookavailableUnreachableDNSCalledvendorsupport—hitvoicemailRestoredfrombackupLost proddata(even abit)DependencyfailedsilentlyBackuppasswordwaschanged butnot sharedConflictingrecoveryinstructionsHit restore,regrettedimmediatelyAlertfalsepositiveDeploymentbroke prodDR testfailedDBmigrationfailedPracticedfailoverDeployedduring amajorincidentVendorsaid,“That’s notcovered”Saw amysteriouscron joblabeled “donot delete”

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