Availability · Difficulty 4 of 5 · 45 min
Failover that never fails over
Traffic keeps going to the primary region even though the standby is healthy and should have taken over. Health checks and routing rules exist, but nothing shifts when the primary fails. A second, near-identical set of records exists. The operations team keeps the expected configuration on a dashboard. Restore automatic failover.
Where the symptom shows: Route 53
Take this challenge on a live account
A live AWS account, already broken, and a clock. You fix it with the provider's own console and command line, then read a report of how you worked. We host the cloud account. Nothing lands on your bill.
More challenges
- AvailabilityThe fleet never replaces a dead nodeEC2 · 40 min · level 4
- AvailabilityPower loss in one availability zoneEC2 · 45 min · level 4
- AvailabilityContainers lose connectivity mid-requestElastic Load Balancing · 45 min · level 4
- AvailabilityOutbound traffic reaches nothingLambda · 45 min · level 4
- AvailabilityConnections drop when the writer changesRDS · 45 min · level 4
- AvailabilityCallers turned away at trivial trafficAPI Gateway · 20 min · level 3