ConflictingrecoveryinstructionsBackuptape wascorruptedRan afailover,forgot thefirewall rulesSaw amysteriouscron joblabeled “donot delete”Foundpasswordsin a stickynoteWrote aDR planno onereadNorunbookavailableForgotto testbackupCreateda backupstrategyPracticedfailoverDeploymentbroke prodLost proddata(even abit)Oncallduring aholidayDiscoveredthe backupdrive wasfullRanchaos testin prodUnreachableDNSCloudregiondownIgnored analert thatwas realthis timeStarted aDR drill—no oneshowed upCouldn’treach theprimarycontactThe “hotsite” wasactuallycoldDeployedduring amajorincidentDiscoveredhalf the infrawas neverdocumentedRan a DRstimulationgameSomeoneunpluggedthe “do nottouch” serverDBmigrationfailed“Itworkedin dev”DR planincluded aretiredemployeeDid apost-mortemFix requiredphysicalaccess (noone hadkeys)Got calledduringdinnerHit restore,regrettedimmediatelySearchedTeams/WhatsApp/Slackfor the DR stepsConfuseddev and prodenvironmentsMisreada severityalertDR testpassed...because noone actuallytested anythingSpent 2hoursdebugging—then found itwas a typoTeam usedfive differentdefinitions of“RTO”Woke upmidnightto standbycallRestoredfrombackupGot called mid-flight (tried totroubleshootover airplaneWi-Fi)DR testfailedTestedDR... inprod byaccidentRestoredsuccessfully—into prodby mistakeNetworkoutageAccidentallydeleteddataBackupran... butdidn’t includethe databaseDidn’thave abackupVendorsaid,“That’s notcovered”Customscriptfailed withno logsPower cameback... andthen wentout againDependencyfailedsilentlyRealized youwererestoring thewrong day’sbackupSystem alertmissedbecause alertrule was toospecificExternalservicewentdownFoundcriticalsystem on apersonallaptopLoggedincident... tothe wrongteamGotlocked outmid-recoveryCalledvendorsupport—hitvoicemailAppliedthe wrongconfig toprodFound thebackup inthe wrongformatAlertfatigueRealized theDR testbrokesomethingelseBackuppasswordwaschanged butnot sharedAlertfalsepositiveLogged intothe wrongcloudaccountRecoverytook >1dayConflictingrecoveryinstructionsBackuptape wascorruptedRan afailover,forgot thefirewall rulesSaw amysteriouscron joblabeled “donot delete”Foundpasswordsin a stickynoteWrote aDR planno onereadNorunbookavailableForgotto testbackupCreateda backupstrategyPracticedfailoverDeploymentbroke prodLost proddata(even abit)Oncallduring aholidayDiscoveredthe backupdrive wasfullRanchaos testin prodUnreachableDNSCloudregiondownIgnored analert thatwas realthis timeStarted aDR drill—no oneshowed upCouldn’treach theprimarycontactThe “hotsite” wasactuallycoldDeployedduring amajorincidentDiscoveredhalf the infrawas neverdocumentedRan a DRstimulationgameSomeoneunpluggedthe “do nottouch” serverDBmigrationfailed“Itworkedin dev”DR planincluded aretiredemployeeDid apost-mortemFix requiredphysicalaccess (noone hadkeys)Got calledduringdinnerHit restore,regrettedimmediatelySearchedTeams/WhatsApp/Slackfor the DR stepsConfuseddev and prodenvironmentsMisreada severityalertDR testpassed...because noone actuallytested anythingSpent 2hoursdebugging—then found itwas a typoTeam usedfive differentdefinitions of“RTO”Woke upmidnightto standbycallRestoredfrombackupGot called mid-flight (tried totroubleshootover airplaneWi-Fi)DR testfailedTestedDR... inprod byaccidentRestoredsuccessfully—into prodby mistakeNetworkoutageAccidentallydeleteddataBackupran... butdidn’t includethe databaseDidn’thave abackupVendorsaid,“That’s notcovered”Customscriptfailed withno logsPower cameback... andthen wentout againDependencyfailedsilentlyRealized youwererestoring thewrong day’sbackupSystem alertmissedbecause alertrule was toospecificExternalservicewentdownFoundcriticalsystem on apersonallaptopLoggedincident... tothe wrongteamGotlocked outmid-recoveryCalledvendorsupport—hitvoicemailAppliedthe wrongconfig toprodFound thebackup inthe wrongformatAlertfatigueRealized theDR testbrokesomethingelseBackuppasswordwaschanged butnot sharedAlertfalsepositiveLogged intothe wrongcloudaccountRecoverytook >1day

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