Route 53 · ALB · Intermediate
DNS points to yesterday
Some clients reach a retired load balancer.
INITIAL ALERT
Some clients reach a retired load balancer.
You are primary on-call. Establish the failure domain, protect healthy capacity, and choose the safest next action.
The new load balancer is healthy and serves the expected release.
The decisive evidence and solution remain locked inside the simulation.WHAT THIS TESTS
Production judgment across Route 53 · ALB.
Networking failures often leave every individual component looking healthy. Strong responders compare the client path, control-plane configuration, and known-good traffic before changing production.
- 01Trace traffic across layered AWS controls
- 02Separate DNS, routing, and target failures
- 03Recover connectivity without creating drift
SIMULATION STRUCTURE
Four evidence layers. No answer shown here.
The full exercise unlocks each layer as you commit to decisions.
Alert
Confirm the reported symptom and customer impact.
Baseline
Compare the failing path with a known-good condition.
Finding
Identify the evidence that separates plausible causes.
Change
Choose a controlled recovery and a durable prevention step.
Can you make the call without seeing the solution?
Try three incidents free. Paid incidents unlock only after Stripe confirms lifetime access.