AlertfatigueIgnored analert thatwas realthis timeAlertfalsepositiveThe “hotsite” wasactuallycoldDeploymentbroke prodDiscoveredhalf the infrawas neverdocumentedFoundcriticalsystem on apersonallaptopRanchaos testin prodDidn’thave abackupDR planincluded aretiredemployeeFound thebackup inthe wrongformatDid apost-mortemDR testfailedCouldn’treach theprimarycontactRestoredsuccessfully—into prodby mistakeLost proddata(even abit)Saw amysteriouscron joblabeled “donot delete”DR testpassed...because noone actuallytested anythingCloudregiondownLoggedincident... tothe wrongteamFoundpasswordsin a stickynoteRestoredfrombackupHit restore,regrettedimmediatelyAppliedthe wrongconfig toprodPower cameback... andthen wentout againNorunbookavailableDiscoveredthe backupdrive wasfullTestedDR... inprod byaccidentDBmigrationfailedGot calledduringdinnerNetworkoutageMisreada severityalertSpent 2hoursdebugging—then found itwas a typoTeam usedfive differentdefinitions of“RTO”DependencyfailedsilentlyCustomscriptfailed withno logsCreateda backupstrategyLogged intothe wrongcloudaccountRecoverytook >1dayOncallduring aholidayUnreachableDNSRealized theDR testbrokesomethingelseGotlocked outmid-recoveryBackupran... butdidn’t includethe databaseWrote aDR planno oneread“Itworkedin dev”Confuseddev and prodenvironmentsSomeoneunpluggedthe “do nottouch” serverRan a DRstimulationgameAccidentallydeleteddataDeployedduring amajorincidentRealized youwererestoring thewrong day’sbackupRan afailover,forgot thefirewall rulesForgotto testbackupWoke upmidnightto standbycallExternalservicewentdownSearchedTeams/WhatsApp/Slackfor the DR stepsVendorsaid,“That’s notcovered”Started aDR drill—no oneshowed upBackuptape wascorruptedPracticedfailoverSystem alertmissedbecause alertrule was toospecificFix requiredphysicalaccess (noone hadkeys)Backuppasswordwaschanged butnot sharedCalledvendorsupport—hitvoicemailConflictingrecoveryinstructionsGot called mid-flight (tried totroubleshootover airplaneWi-Fi)AlertfatigueIgnored analert thatwas realthis timeAlertfalsepositiveThe “hotsite” wasactuallycoldDeploymentbroke prodDiscoveredhalf the infrawas neverdocumentedFoundcriticalsystem on apersonallaptopRanchaos testin prodDidn’thave abackupDR planincluded aretiredemployeeFound thebackup inthe wrongformatDid apost-mortemDR testfailedCouldn’treach theprimarycontactRestoredsuccessfully—into prodby mistakeLost proddata(even abit)Saw amysteriouscron joblabeled “donot delete”DR testpassed...because noone actuallytested anythingCloudregiondownLoggedincident... tothe wrongteamFoundpasswordsin a stickynoteRestoredfrombackupHit restore,regrettedimmediatelyAppliedthe wrongconfig toprodPower cameback... andthen wentout againNorunbookavailableDiscoveredthe backupdrive wasfullTestedDR... inprod byaccidentDBmigrationfailedGot calledduringdinnerNetworkoutageMisreada severityalertSpent 2hoursdebugging—then found itwas a typoTeam usedfive differentdefinitions of“RTO”DependencyfailedsilentlyCustomscriptfailed withno logsCreateda backupstrategyLogged intothe wrongcloudaccountRecoverytook >1dayOncallduring aholidayUnreachableDNSRealized theDR testbrokesomethingelseGotlocked outmid-recoveryBackupran... butdidn’t includethe databaseWrote aDR planno oneread“Itworkedin dev”Confuseddev and prodenvironmentsSomeoneunpluggedthe “do nottouch” serverRan a DRstimulationgameAccidentallydeleteddataDeployedduring amajorincidentRealized youwererestoring thewrong day’sbackupRan afailover,forgot thefirewall rulesForgotto testbackupWoke upmidnightto standbycallExternalservicewentdownSearchedTeams/WhatsApp/Slackfor the DR stepsVendorsaid,“That’s notcovered”Started aDR drill—no oneshowed upBackuptape wascorruptedPracticedfailoverSystem alertmissedbecause alertrule was toospecificFix requiredphysicalaccess (noone hadkeys)Backuppasswordwaschanged butnot sharedCalledvendorsupport—hitvoicemailConflictingrecoveryinstructionsGot called mid-flight (tried totroubleshootover airplaneWi-Fi)

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