Region Down: Your SaaS on Someone Else's Cloud Outage
Technology tabletop exercise scenario · Cloud Outage
Your product is down, your engineers are staring at someone else's status page, and your customers don't care whose region failed — they bought from you. The cloud concentrated the internet's infrastructure, and in December 2021 the industry got a famous reminder of what that means when the busiest region in the world stumbles for hours.
This scenario runs SaaS leadership through the outage you can't fix: honest status communication about a dependency you don't control, the failover gamble — a DR region that exists but has never carried full load, against a provider estimate that keeps slipping — and the aftermath of SLA credits, enterprise trust, and a postmortem that has to own the architecture you chose. Because 'we're on the cloud' was the resilience plan. This exercise is about what the real one costs.
1 hr 30 minIntermediate
TechnologySOC 2
What this scenario tests
- How fast your team distinguishes your incident from your provider's
- Whether your status communication stays honest and useful about a failure you can't fix
- How you make the failover call: untested DR cutover versus a slipping provider estimate
- What your postmortem owns about the dependency — and what resilience you fund afterward
Who it's for
IT & Security Team · Executive / C-Suite · Communications / PR