Disasters Bingo

Disasters Bingo Card
Preview

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

More like this:

CLIPP Bingo | CPS BINGO | TEM Bingo | TEM Bingo | Deploy Issues

Play Online

Share this URL with your players:

For more control of your online game, create a clone of this card first.

Learn how to conduct a bingo game.

Call List

Probabilities

With players vying for a you'll have to call about __ items before someone wins. There's a __% chance that a lucky player would win after calling __ items.

Tip: If you want your game to last longer (on average), add more unique words/images to it.