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