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