The “hotsite” wasactuallycoldDeploymentbroke prodCustomscriptfailed withno logsAppliedthe wrongconfig toprodFound thebackup inthe wrongformatPracticedfailoverOncallduring aholidayPower cameback... andthen wentout againRan afailover,forgot thefirewall rulesTeam usedfive differentdefinitions of“RTO”Ran a DRstimulationgameDeployedduring amajorincidentBackuptape wascorruptedWrote aDR planno onereadForgotto testbackupDependencyfailedsilentlySearchedTeams/WhatsApp/Slackfor the DR stepsRestoredsuccessfully—into prodby mistakeCalledvendorsupport—hitvoicemailRecoverytook >1dayMisreada severityalertCouldn’treach theprimarycontactGotlocked outmid-recoveryFoundpasswordsin a stickynoteGot called mid-flight (tried totroubleshootover airplaneWi-Fi)DR testfailedDidn’thave abackupFix requiredphysicalaccess (noone hadkeys)Backupran... butdidn’t includethe databaseCreateda backupstrategyRanchaos testin prodCloudregiondownBackuppasswordwaschanged butnot sharedSpent 2hoursdebugging—then found itwas a typoAlertfalsepositiveRestoredfrombackupLost proddata(even abit)AlertfatigueGot calledduringdinnerIgnored analert thatwas realthis timeConflictingrecoveryinstructionsRealized youwererestoring thewrong day’sbackupExternalservicewentdownNorunbookavailableNetworkoutageHit restore,regrettedimmediatelyDid apost-mortemSomeoneunpluggedthe “do nottouch” serverUnreachableDNSStarted aDR drill—no oneshowed upTestedDR... inprod byaccidentConfuseddev and prodenvironmentsVendorsaid,“That’s notcovered”Discoveredthe backupdrive wasfullDBmigrationfailedLoggedincident... tothe wrongteamDR planincluded aretiredemployeeWoke upmidnightto standbycallDiscoveredhalf the infrawas neverdocumentedLogged intothe wrongcloudaccountSaw amysteriouscron joblabeled “donot delete”System alertmissedbecause alertrule was toospecificAccidentallydeleteddata“Itworkedin dev”DR testpassed...because noone actuallytested anythingFoundcriticalsystem on apersonallaptopRealized theDR testbrokesomethingelseThe “hotsite” wasactuallycoldDeploymentbroke prodCustomscriptfailed withno logsAppliedthe wrongconfig toprodFound thebackup inthe wrongformatPracticedfailoverOncallduring aholidayPower cameback... andthen wentout againRan afailover,forgot thefirewall rulesTeam usedfive differentdefinitions of“RTO”Ran a DRstimulationgameDeployedduring amajorincidentBackuptape wascorruptedWrote aDR planno onereadForgotto testbackupDependencyfailedsilentlySearchedTeams/WhatsApp/Slackfor the DR stepsRestoredsuccessfully—into prodby mistakeCalledvendorsupport—hitvoicemailRecoverytook >1dayMisreada severityalertCouldn’treach theprimarycontactGotlocked outmid-recoveryFoundpasswordsin a stickynoteGot called mid-flight (tried totroubleshootover airplaneWi-Fi)DR testfailedDidn’thave abackupFix requiredphysicalaccess (noone hadkeys)Backupran... butdidn’t includethe databaseCreateda backupstrategyRanchaos testin prodCloudregiondownBackuppasswordwaschanged butnot sharedSpent 2hoursdebugging—then found itwas a typoAlertfalsepositiveRestoredfrombackupLost proddata(even abit)AlertfatigueGot calledduringdinnerIgnored analert thatwas realthis timeConflictingrecoveryinstructionsRealized youwererestoring thewrong day’sbackupExternalservicewentdownNorunbookavailableNetworkoutageHit restore,regrettedimmediatelyDid apost-mortemSomeoneunpluggedthe “do nottouch” serverUnreachableDNSStarted aDR drill—no oneshowed upTestedDR... inprod byaccidentConfuseddev and prodenvironmentsVendorsaid,“That’s notcovered”Discoveredthe backupdrive wasfullDBmigrationfailedLoggedincident... tothe wrongteamDR planincluded aretiredemployeeWoke upmidnightto standbycallDiscoveredhalf the infrawas neverdocumentedLogged intothe wrongcloudaccountSaw amysteriouscron joblabeled “donot delete”System alertmissedbecause alertrule was toospecificAccidentallydeleteddata“Itworkedin dev”DR testpassed...because noone actuallytested anythingFoundcriticalsystem on apersonallaptopRealized theDR testbrokesomethingelse

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