Did apost-mortemWrote aDR planno onereadNorunbookavailableDependencyfailedsilentlySpent 2hoursdebugging—then found itwas a typoSearchedTeams/WhatsApp/Slackfor the DR stepsCloudregiondownDR planincluded aretiredemployeeSomeoneunpluggedthe “do nottouch” serverExternalservicewentdownRan a DRstimulationgameAlertfalsepositiveDeploymentbroke prodBackuppasswordwaschanged butnot sharedMisreada severityalertVendorsaid,“That’s notcovered”Saw amysteriouscron joblabeled “donot delete”AccidentallydeleteddataDidn’thave abackupLoggedincident... tothe wrongteamPower cameback... andthen wentout againDR testfailedTestedDR... inprod byaccidentGotlocked outmid-recoveryDR testpassed...because noone actuallytested anythingRanchaos testin prodThe “hotsite” wasactuallycoldDBmigrationfailedCustomscriptfailed withno logsRealized youwererestoring thewrong day’sbackupDiscoveredhalf the infrawas neverdocumented“Itworkedin dev”PracticedfailoverFoundpasswordsin a stickynoteConflictingrecoveryinstructionsFix requiredphysicalaccess (noone hadkeys)Got calledduringdinnerDeployedduring amajorincidentOncallduring aholidayRealized theDR testbrokesomethingelseCalledvendorsupport—hitvoicemailLost proddata(even abit)Got called mid-flight (tried totroubleshootover airplaneWi-Fi)Forgotto testbackupCouldn’treach theprimarycontactAppliedthe wrongconfig toprodBackupran... butdidn’t includethe databaseFound thebackup inthe wrongformatRecoverytook >1dayHit restore,regrettedimmediatelyConfuseddev and prodenvironmentsUnreachableDNSWoke upmidnightto standbycallRestoredsuccessfully—into prodby mistakeBackuptape wascorruptedAlertfatigueLogged intothe wrongcloudaccountSystem alertmissedbecause alertrule was toospecificStarted aDR drill—no oneshowed upFoundcriticalsystem on apersonallaptopIgnored analert thatwas realthis timeCreateda backupstrategyTeam usedfive differentdefinitions of“RTO”NetworkoutageDiscoveredthe backupdrive wasfullRan afailover,forgot thefirewall rulesRestoredfrombackupDid apost-mortemWrote aDR planno onereadNorunbookavailableDependencyfailedsilentlySpent 2hoursdebugging—then found itwas a typoSearchedTeams/WhatsApp/Slackfor the DR stepsCloudregiondownDR planincluded aretiredemployeeSomeoneunpluggedthe “do nottouch” serverExternalservicewentdownRan a DRstimulationgameAlertfalsepositiveDeploymentbroke prodBackuppasswordwaschanged butnot sharedMisreada severityalertVendorsaid,“That’s notcovered”Saw amysteriouscron joblabeled “donot delete”AccidentallydeleteddataDidn’thave abackupLoggedincident... tothe wrongteamPower cameback... andthen wentout againDR testfailedTestedDR... inprod byaccidentGotlocked outmid-recoveryDR testpassed...because noone actuallytested anythingRanchaos testin prodThe “hotsite” wasactuallycoldDBmigrationfailedCustomscriptfailed withno logsRealized youwererestoring thewrong day’sbackupDiscoveredhalf the infrawas neverdocumented“Itworkedin dev”PracticedfailoverFoundpasswordsin a stickynoteConflictingrecoveryinstructionsFix requiredphysicalaccess (noone hadkeys)Got calledduringdinnerDeployedduring amajorincidentOncallduring aholidayRealized theDR testbrokesomethingelseCalledvendorsupport—hitvoicemailLost proddata(even abit)Got called mid-flight (tried totroubleshootover airplaneWi-Fi)Forgotto testbackupCouldn’treach theprimarycontactAppliedthe wrongconfig toprodBackupran... butdidn’t includethe databaseFound thebackup inthe wrongformatRecoverytook >1dayHit restore,regrettedimmediatelyConfuseddev and prodenvironmentsUnreachableDNSWoke upmidnightto standbycallRestoredsuccessfully—into prodby mistakeBackuptape wascorruptedAlertfatigueLogged intothe wrongcloudaccountSystem alertmissedbecause alertrule was toospecificStarted aDR drill—no oneshowed upFoundcriticalsystem on apersonallaptopIgnored analert thatwas realthis timeCreateda backupstrategyTeam usedfive differentdefinitions of“RTO”NetworkoutageDiscoveredthe backupdrive wasfullRan afailover,forgot thefirewall rulesRestoredfrombackup

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