DBmigrationfailedCreateda backupstrategySomeoneunpluggedthe “do nottouch” serverNorunbookavailableRanchaos testin prodDependencyfailedsilentlyGot called mid-flight (tried totroubleshootover airplaneWi-Fi)NetworkoutageAlertfatigueCloudregiondownStarted aDR drill—no oneshowed upPracticedfailoverDR testfailedTestedDR... inprod byaccidentThe “hotsite” wasactuallycoldCustomscriptfailed withno logsSystem alertmissedbecause alertrule was toospecificLost proddata(even abit)Fix requiredphysicalaccess (noone hadkeys)Did apost-mortemHit restore,regrettedimmediatelyCouldn’treach theprimarycontactDidn’thave abackupExternalservicewentdownLoggedincident... tothe wrongteamRealized theDR testbrokesomethingelseFoundpasswordsin a stickynoteSaw amysteriouscron joblabeled “donot delete”Team usedfive differentdefinitions of“RTO”ConflictingrecoveryinstructionsUnreachableDNSRestoredfrombackupRealized youwererestoring thewrong day’sbackupDR planincluded aretiredemployeeGot calledduringdinnerGotlocked outmid-recoveryBackupran... butdidn’t includethe databaseSpent 2hoursdebugging—then found itwas a typoDeploymentbroke prodFound thebackup inthe wrongformatSearchedTeams/WhatsApp/Slackfor the DR stepsBackuppasswordwaschanged butnot shared“Itworkedin dev”DR testpassed...because noone actuallytested anythingRestoredsuccessfully—into prodby mistakeWrote aDR planno onereadCalledvendorsupport—hitvoicemailRecoverytook >1dayAccidentallydeleteddataDiscoveredhalf the infrawas neverdocumentedMisreada severityalertBackuptape wascorruptedAppliedthe wrongconfig toprodForgotto testbackupConfuseddev and prodenvironmentsRan a DRstimulationgameOncallduring aholidayAlertfalsepositiveRan afailover,forgot thefirewall rulesWoke upmidnightto standbycallFoundcriticalsystem on apersonallaptopLogged intothe wrongcloudaccountIgnored analert thatwas realthis timeDiscoveredthe backupdrive wasfullVendorsaid,“That’s notcovered”Power cameback... andthen wentout againDeployedduring amajorincidentDBmigrationfailedCreateda backupstrategySomeoneunpluggedthe “do nottouch” serverNorunbookavailableRanchaos testin prodDependencyfailedsilentlyGot called mid-flight (tried totroubleshootover airplaneWi-Fi)NetworkoutageAlertfatigueCloudregiondownStarted aDR drill—no oneshowed upPracticedfailoverDR testfailedTestedDR... inprod byaccidentThe “hotsite” wasactuallycoldCustomscriptfailed withno logsSystem alertmissedbecause alertrule was toospecificLost proddata(even abit)Fix requiredphysicalaccess (noone hadkeys)Did apost-mortemHit restore,regrettedimmediatelyCouldn’treach theprimarycontactDidn’thave abackupExternalservicewentdownLoggedincident... tothe wrongteamRealized theDR testbrokesomethingelseFoundpasswordsin a stickynoteSaw amysteriouscron joblabeled “donot delete”Team usedfive differentdefinitions of“RTO”ConflictingrecoveryinstructionsUnreachableDNSRestoredfrombackupRealized youwererestoring thewrong day’sbackupDR planincluded aretiredemployeeGot calledduringdinnerGotlocked outmid-recoveryBackupran... butdidn’t includethe databaseSpent 2hoursdebugging—then found itwas a typoDeploymentbroke prodFound thebackup inthe wrongformatSearchedTeams/WhatsApp/Slackfor the DR stepsBackuppasswordwaschanged butnot shared“Itworkedin dev”DR testpassed...because noone actuallytested anythingRestoredsuccessfully—into prodby mistakeWrote aDR planno onereadCalledvendorsupport—hitvoicemailRecoverytook >1dayAccidentallydeleteddataDiscoveredhalf the infrawas neverdocumentedMisreada severityalertBackuptape wascorruptedAppliedthe wrongconfig toprodForgotto testbackupConfuseddev and prodenvironmentsRan a DRstimulationgameOncallduring aholidayAlertfalsepositiveRan afailover,forgot thefirewall rulesWoke upmidnightto standbycallFoundcriticalsystem on apersonallaptopLogged intothe wrongcloudaccountIgnored analert thatwas realthis timeDiscoveredthe backupdrive wasfullVendorsaid,“That’s notcovered”Power cameback... andthen wentout againDeployedduring amajorincident

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