Skip to main content

Multi-Region Failure Simulator

Pick your architecture, simulate a region failure, and see exactly what breaks, in what order — in plain English. A reasoning tool, not a live infrastructure test.

Try a Sample Scenario
Your Architecture
Risk Flags
Estimated Recovery Profile (RPO / RTO)
ComponentStatusRPO bandpotential data loss windowRTO bandestimated recovery timeWhy
These are illustrative qualitative bands reasoned from the topology, replication, routing, compute, and observability choices you selected above — not measured values from a real system, and not an SLA. Use them to compare architectures on paper, then confirm the real numbers with an actual failover test.
What Happens, Step by Step
This reasons through common patterns for the combination you selected — it does not touch, ping, or test any real infrastructure, and it isn't a substitute for an actual failover test. Use it to sanity-check a design or brief a team before you run the real thing.

Frequently Asked Questions

Does this simulator test my actual infrastructure?

No. It never connects to AWS, GCP, Azure, or any live system — it reasons through common failure patterns based on the architecture choices you select, entirely in your browser. Think of it as a napkin sketch for a conversation, not a substitute for a real game day or chaos engineering exercise.

What is split-brain and why does the simulator flag it?

Split-brain happens when a network partition leaves two regions individually healthy but unable to reach each other, and both keep accepting writes independently. If you select active-active topology with asynchronous replication and a network-partition failure, the simulator flags this because the two regions can silently drift into conflicting data that needs manual reconciliation once connectivity returns.

Why does my configuration show a data-loss risk even though I have replication?

Asynchronous replication ships writes to the other region after acknowledging them to the client, so there's always a small window — the replication lag — where a confirmed write hasn't reached the surviving region yet. Only synchronous replication, which confirms the write in both regions before acknowledging it, eliminates this window, at the cost of added write latency all the time, not just during a failure.

What do RTO and RPO mean, and where do they show up here?

RTO (recovery time objective) is how long the service can be down; RPO (recovery point objective) is how much recent data you can afford to lose. In this simulator, RTO is driven mainly by traffic routing and compute (DNS TTLs and health-check intervals, warm versus cold standby), and RPO by the replication mode: asynchronous replication means a non-zero RPO equal to the replication lag at failure, while synchronous replication can approach zero at the cost of write latency.

Which disaster recovery strategies does the topology setting represent?

The four strategies in the AWS Well-Architected reliability guidance: backup and restore, pilot light, warm standby and multi-site active-active, ordered by rising cost and falling recovery time. The Pilot Light, Active-Passive (warm standby) and Active-Active options correspond to three of them; Single Region means no disaster recovery.

Why is DNS failover not instant?

Resolvers and clients cache answers for the record's TTL and sometimes longer, health checks need several failed probes before declaring a region unhealthy, and long-lived connections do not re-resolve at all. Plan for minutes rather than seconds with DNS-only failover. Anycast and global load balancers shift traffic without waiting for caches to expire.