(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
Realized the DR test broke something else
Backup ran... but didn’t include the database
Vendor said, “That’s not covered”
Cloud region down
Deployment broke prod
Logged into the wrong cloud account
Ran a DR stimulation game
Deployed during a major incident
Network outage
Searched Teams/WhatsApp/Slack for the DR steps
Found critical system on a personal laptop
Ran chaos test in prod
Oncall during a holiday
DB migration failed
No runbook available
Unreachable DNS
Found passwords in a sticky note
DR plan included a retired employee
Conflicting recovery instructions
Fix required physical access (no one had keys)
Got called mid-flight (tried to troubleshoot over airplane Wi-Fi)
Ran a failover, forgot the firewall rules
Alert false positive
Found the backup in the wrong format
Didn’t have a backup
Tested DR... in prod by accident
Misread a severity alert
Got called during dinner
DR test passed... because no one actually tested anything
Created a backup strategy
Restored from backup
System alert missed because alert rule was too specific
External service went down
Did a post-mortem
Hit restore, regretted immediately
Practiced failover
Confused dev and prod environments
Backup password was changed but not shared
Ignored an alert that was real this time
Spent 2 hours debugging—then found it was a typo
Custom script failed with no logs
Woke up midnight to standby call
Discovered half the infra was never documented
Backup tape was corrupted
Accidentally deleted data
Power came back... and then went out again
Forgot to test backup
Wrote a DR plan no one read
Team used five different definitions of “RTO”
DR test failed
Couldn’t reach the primary contact
Got locked out mid-recovery
Logged incident... to the wrong team
Called vendor support—hit voicemail
Dependency failed silently
Alert fatigue
Restored successfully—into prod by mistake
Recovery took >1 day
Saw a mysterious cron job labeled “do not delete”
Lost prod data (even a bit)
“It worked in dev”
Discovered the backup drive was full
Started a DR drill—no one showed up
The “hot site” was actually cold
Realized you were restoring the wrong day’s backup
