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