Gotlocked outmid-recoveryVendorsaid,“That’s notcovered”Confuseddev and prodenvironmentsPower cameback... andthen wentout againFoundcriticalsystem on apersonallaptopRan afailover,forgot thefirewall rulesOncallduring aholidayBackuptape wascorruptedHit restore,regrettedimmediatelyLoggedincident... tothe wrongteamFix requiredphysicalaccess (noone hadkeys)DBmigrationfailedWoke upmidnightto standbycallUnreachableDNSThe “hotsite” wasactuallycoldConflictingrecoveryinstructionsDidn’thave abackupExternalservicewentdown“Itworkedin dev”Misreada severityalertLogged intothe wrongcloudaccountDR planincluded aretiredemployeeNorunbookavailablePracticedfailoverDid apost-mortemDR testfailedCalledvendorsupport—hitvoicemailRealized youwererestoring thewrong day’sbackupForgotto testbackupBackupran... butdidn’t includethe databaseRestoredsuccessfully—into prodby mistakeStarted aDR drill—no oneshowed upCustomscriptfailed withno logsDiscoveredhalf the infrawas neverdocumentedDeployedduring amajorincidentAppliedthe wrongconfig toprodSaw amysteriouscron joblabeled “donot delete”AccidentallydeleteddataSomeoneunpluggedthe “do nottouch” serverLost proddata(even abit)AlertfatigueDependencyfailedsilentlyDR testpassed...because noone actuallytested anythingDiscoveredthe backupdrive wasfullCreateda backupstrategySearchedTeams/WhatsApp/Slackfor the DR stepsFound thebackup inthe wrongformatTestedDR... inprod byaccidentCloudregiondownRealized theDR testbrokesomethingelseAlertfalsepositiveFoundpasswordsin a stickynoteBackuppasswordwaschanged butnot sharedDeploymentbroke prodCouldn’treach theprimarycontactTeam usedfive differentdefinitions of“RTO”Wrote aDR planno onereadNetworkoutageRecoverytook >1dayRanchaos testin prodSystem alertmissedbecause alertrule was toospecificIgnored analert thatwas realthis timeRestoredfrombackupGot called mid-flight (tried totroubleshootover airplaneWi-Fi)Ran a DRstimulationgameGot calledduringdinnerSpent 2hoursdebugging—then found itwas a typoGotlocked outmid-recoveryVendorsaid,“That’s notcovered”Confuseddev and prodenvironmentsPower cameback... andthen wentout againFoundcriticalsystem on apersonallaptopRan afailover,forgot thefirewall rulesOncallduring aholidayBackuptape wascorruptedHit restore,regrettedimmediatelyLoggedincident... tothe wrongteamFix requiredphysicalaccess (noone hadkeys)DBmigrationfailedWoke upmidnightto standbycallUnreachableDNSThe “hotsite” wasactuallycoldConflictingrecoveryinstructionsDidn’thave abackupExternalservicewentdown“Itworkedin dev”Misreada severityalertLogged intothe wrongcloudaccountDR planincluded aretiredemployeeNorunbookavailablePracticedfailoverDid apost-mortemDR testfailedCalledvendorsupport—hitvoicemailRealized youwererestoring thewrong day’sbackupForgotto testbackupBackupran... butdidn’t includethe databaseRestoredsuccessfully—into prodby mistakeStarted aDR drill—no oneshowed upCustomscriptfailed withno logsDiscoveredhalf the infrawas neverdocumentedDeployedduring amajorincidentAppliedthe wrongconfig toprodSaw amysteriouscron joblabeled “donot delete”AccidentallydeleteddataSomeoneunpluggedthe “do nottouch” serverLost proddata(even abit)AlertfatigueDependencyfailedsilentlyDR testpassed...because noone actuallytested anythingDiscoveredthe backupdrive wasfullCreateda backupstrategySearchedTeams/WhatsApp/Slackfor the DR stepsFound thebackup inthe wrongformatTestedDR... inprod byaccidentCloudregiondownRealized theDR testbrokesomethingelseAlertfalsepositiveFoundpasswordsin a stickynoteBackuppasswordwaschanged butnot sharedDeploymentbroke prodCouldn’treach theprimarycontactTeam usedfive differentdefinitions of“RTO”Wrote aDR planno onereadNetworkoutageRecoverytook >1dayRanchaos testin prodSystem alertmissedbecause alertrule was toospecificIgnored analert thatwas realthis timeRestoredfrombackupGot called mid-flight (tried totroubleshootover airplaneWi-Fi)Ran a DRstimulationgameGot calledduringdinnerSpent 2hoursdebugging—then found itwas a typo

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