UnreachableDNSStarted aDR drill—no oneshowed upHit restore,regrettedimmediatelyCloudregiondownGotlocked outmid-recoveryExternalservicewentdownCreateda backupstrategyGot calledduringdinnerFix requiredphysicalaccess (noone hadkeys)Found thebackup inthe wrongformatDiscoveredhalf the infrawas neverdocumentedRestoredfrombackupGot called mid-flight (tried totroubleshootover airplaneWi-Fi)Backupran... butdidn’t includethe databaseCalledvendorsupport—hitvoicemailCustomscriptfailed withno logsDid apost-mortemTestedDR... inprod byaccidentDR testfailedFoundpasswordsin a stickynoteRealized theDR testbrokesomethingelseDeployedduring amajorincidentConfuseddev and prodenvironmentsBackuppasswordwaschanged butnot sharedRan a DRstimulationgameDiscoveredthe backupdrive wasfullBackuptape wascorruptedRecoverytook >1dayAppliedthe wrongconfig toprodConflictingrecoveryinstructionsNorunbookavailableFoundcriticalsystem on apersonallaptop“Itworkedin dev”AccidentallydeleteddataVendorsaid,“That’s notcovered”Team usedfive differentdefinitions of“RTO”Loggedincident... tothe wrongteamIgnored analert thatwas realthis timePower cameback... andthen wentout againDependencyfailedsilentlyDidn’thave abackupSomeoneunpluggedthe “do nottouch” serverSystem alertmissedbecause alertrule was toospecificSaw amysteriouscron joblabeled “donot delete”The “hotsite” wasactuallycoldSearchedTeams/WhatsApp/Slackfor the DR stepsAlertfalsepositiveLogged intothe wrongcloudaccountOncallduring aholidayRan afailover,forgot thefirewall rulesWrote aDR planno onereadDBmigrationfailedPracticedfailoverAlertfatigueMisreada severityalertLost proddata(even abit)Deploymentbroke prodSpent 2hoursdebugging—then found itwas a typoRanchaos testin prodForgotto testbackupNetworkoutageRealized youwererestoring thewrong day’sbackupDR testpassed...because noone actuallytested anythingWoke upmidnightto standbycallRestoredsuccessfully—into prodby mistakeDR planincluded aretiredemployeeCouldn’treach theprimarycontactUnreachableDNSStarted aDR drill—no oneshowed upHit restore,regrettedimmediatelyCloudregiondownGotlocked outmid-recoveryExternalservicewentdownCreateda backupstrategyGot calledduringdinnerFix requiredphysicalaccess (noone hadkeys)Found thebackup inthe wrongformatDiscoveredhalf the infrawas neverdocumentedRestoredfrombackupGot called mid-flight (tried totroubleshootover airplaneWi-Fi)Backupran... butdidn’t includethe databaseCalledvendorsupport—hitvoicemailCustomscriptfailed withno logsDid apost-mortemTestedDR... inprod byaccidentDR testfailedFoundpasswordsin a stickynoteRealized theDR testbrokesomethingelseDeployedduring amajorincidentConfuseddev and prodenvironmentsBackuppasswordwaschanged butnot sharedRan a DRstimulationgameDiscoveredthe backupdrive wasfullBackuptape wascorruptedRecoverytook >1dayAppliedthe wrongconfig toprodConflictingrecoveryinstructionsNorunbookavailableFoundcriticalsystem on apersonallaptop“Itworkedin dev”AccidentallydeleteddataVendorsaid,“That’s notcovered”Team usedfive differentdefinitions of“RTO”Loggedincident... tothe wrongteamIgnored analert thatwas realthis timePower cameback... andthen wentout againDependencyfailedsilentlyDidn’thave abackupSomeoneunpluggedthe “do nottouch” serverSystem alertmissedbecause alertrule was toospecificSaw amysteriouscron joblabeled “donot delete”The “hotsite” wasactuallycoldSearchedTeams/WhatsApp/Slackfor the DR stepsAlertfalsepositiveLogged intothe wrongcloudaccountOncallduring aholidayRan afailover,forgot thefirewall rulesWrote aDR planno onereadDBmigrationfailedPracticedfailoverAlertfatigueMisreada severityalertLost proddata(even abit)Deploymentbroke prodSpent 2hoursdebugging—then found itwas a typoRanchaos testin prodForgotto testbackupNetworkoutageRealized youwererestoring thewrong day’sbackupDR testpassed...because noone actuallytested anythingWoke upmidnightto standbycallRestoredsuccessfully—into prodby mistakeDR planincluded aretiredemployeeCouldn’treach theprimarycontact

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