Recoverytook >1dayCreateda backupstrategyIgnored analert thatwas realthis timeDR testfailedHit restore,regrettedimmediatelyWrote aDR planno onereadWoke upmidnightto standbycallTeam usedfive differentdefinitions of“RTO”TestedDR... inprod byaccidentForgotto testbackupLoggedincident... tothe wrongteamSearchedTeams/WhatsApp/Slackfor the DR stepsGotlocked outmid-recoveryLogged intothe wrongcloudaccountRealized youwererestoring thewrong day’sbackupOncallduring aholidayRestoredsuccessfully—into prodby mistakeCustomscriptfailed withno logsDBmigrationfailedRanchaos testin prodExternalservicewentdownDiscoveredthe backupdrive wasfullDid apost-mortemRealized theDR testbrokesomethingelseFoundpasswordsin a stickynoteCalledvendorsupport—hitvoicemailGot called mid-flight (tried totroubleshootover airplaneWi-Fi)UnreachableDNSBackupran... butdidn’t includethe databaseAlertfalsepositiveDidn’thave abackupThe “hotsite” wasactuallycoldFound thebackup inthe wrongformatLost proddata(even abit)AlertfatigueBackuppasswordwaschanged butnot sharedRestoredfrombackupNetworkoutageDiscoveredhalf the infrawas neverdocumentedGot calledduringdinnerDeploymentbroke prodDR testpassed...because noone actuallytested anythingRan a DRstimulationgamePracticedfailoverFoundcriticalsystem on apersonallaptopVendorsaid,“That’s notcovered”Backuptape wascorruptedDR planincluded aretiredemployeeSystem alertmissedbecause alertrule was toospecificFix requiredphysicalaccess (noone hadkeys)Started aDR drill—no oneshowed upSomeoneunpluggedthe “do nottouch” serverConflictingrecoveryinstructionsDeployedduring amajorincidentMisreada severityalert“Itworkedin dev”CloudregiondownAccidentallydeleteddataSpent 2hoursdebugging—then found itwas a typoPower cameback... andthen wentout againNorunbookavailableAppliedthe wrongconfig toprodDependencyfailedsilentlyConfuseddev and prodenvironmentsSaw amysteriouscron joblabeled “donot delete”Ran afailover,forgot thefirewall rulesCouldn’treach theprimarycontactRecoverytook >1dayCreateda backupstrategyIgnored analert thatwas realthis timeDR testfailedHit restore,regrettedimmediatelyWrote aDR planno onereadWoke upmidnightto standbycallTeam usedfive differentdefinitions of“RTO”TestedDR... inprod byaccidentForgotto testbackupLoggedincident... tothe wrongteamSearchedTeams/WhatsApp/Slackfor the DR stepsGotlocked outmid-recoveryLogged intothe wrongcloudaccountRealized youwererestoring thewrong day’sbackupOncallduring aholidayRestoredsuccessfully—into prodby mistakeCustomscriptfailed withno logsDBmigrationfailedRanchaos testin prodExternalservicewentdownDiscoveredthe backupdrive wasfullDid apost-mortemRealized theDR testbrokesomethingelseFoundpasswordsin a stickynoteCalledvendorsupport—hitvoicemailGot called mid-flight (tried totroubleshootover airplaneWi-Fi)UnreachableDNSBackupran... butdidn’t includethe databaseAlertfalsepositiveDidn’thave abackupThe “hotsite” wasactuallycoldFound thebackup inthe wrongformatLost proddata(even abit)AlertfatigueBackuppasswordwaschanged butnot sharedRestoredfrombackupNetworkoutageDiscoveredhalf the infrawas neverdocumentedGot calledduringdinnerDeploymentbroke prodDR testpassed...because noone actuallytested anythingRan a DRstimulationgamePracticedfailoverFoundcriticalsystem on apersonallaptopVendorsaid,“That’s notcovered”Backuptape wascorruptedDR planincluded aretiredemployeeSystem alertmissedbecause alertrule was toospecificFix requiredphysicalaccess (noone hadkeys)Started aDR drill—no oneshowed upSomeoneunpluggedthe “do nottouch” serverConflictingrecoveryinstructionsDeployedduring amajorincidentMisreada severityalert“Itworkedin dev”CloudregiondownAccidentallydeleteddataSpent 2hoursdebugging—then found itwas a typoPower cameback... andthen wentout againNorunbookavailableAppliedthe wrongconfig toprodDependencyfailedsilentlyConfuseddev and prodenvironmentsSaw amysteriouscron joblabeled “donot delete”Ran afailover,forgot thefirewall rulesCouldn’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. Recovery took >1 day
  2. Created a backup strategy
  3. Ignored an alert that was real this time
  4. DR test failed
  5. Hit restore, regretted immediately
  6. Wrote a DR plan no one read
  7. Woke up midnight to standby call
  8. Team used five different definitions of “RTO”
  9. Tested DR... in prod by accident
  10. Forgot to test backup
  11. Logged incident... to the wrong team
  12. Searched Teams/WhatsApp/Slack for the DR steps
  13. Got locked out mid-recovery
  14. Logged into the wrong cloud account
  15. Realized you were restoring the wrong day’s backup
  16. Oncall during a holiday
  17. Restored successfully—into prod by mistake
  18. Custom script failed with no logs
  19. DB migration failed
  20. Ran chaos test in prod
  21. External service went down
  22. Discovered the backup drive was full
  23. Did a post-mortem
  24. Realized the DR test broke something else
  25. Found passwords in a sticky note
  26. Called vendor support—hit voicemail
  27. Got called mid-flight (tried to troubleshoot over airplane Wi-Fi)
  28. Unreachable DNS
  29. Backup ran... but didn’t include the database
  30. Alert false positive
  31. Didn’t have a backup
  32. The “hot site” was actually cold
  33. Found the backup in the wrong format
  34. Lost prod data (even a bit)
  35. Alert fatigue
  36. Backup password was changed but not shared
  37. Restored from backup
  38. Network outage
  39. Discovered half the infra was never documented
  40. Got called during dinner
  41. Deployment broke prod
  42. DR test passed... because no one actually tested anything
  43. Ran a DR stimulation game
  44. Practiced failover
  45. Found critical system on a personal laptop
  46. Vendor said, “That’s not covered”
  47. Backup tape was corrupted
  48. DR plan included a retired employee
  49. System alert missed because alert rule was too specific
  50. Fix required physical access (no one had keys)
  51. Started a DR drill—no one showed up
  52. Someone unplugged the “do not touch” server
  53. Conflicting recovery instructions
  54. Deployed during a major incident
  55. Misread a severity alert
  56. “It worked in dev”
  57. Cloud region down
  58. Accidentally deleted data
  59. Spent 2 hours debugging—then found it was a typo
  60. Power came back... and then went out again
  61. No runbook available
  62. Applied the wrong config to prod
  63. Dependency failed silently
  64. Confused dev and prod environments
  65. Saw a mysterious cron job labeled “do not delete”
  66. Ran a failover, forgot the firewall rules
  67. Couldn’t reach the primary contact