One regional dependency can become everyone’s outage.
What happened
A latent race condition in DynamoDB’s automated DNS management system produced an empty record for the regional endpoint. Customer and internal AWS services could no longer establish new DynamoDB connections.
The dependency chain extended into EC2 launches, Network Load Balancer, Lambda, ECS, EKS, Fargate, Connect, Redshift, authentication and even access to AWS support cases. Different effects started and recovered at different times during an event running from 23:48 PDT on 19 October to 14:20 PDT on 20 October 2025.
The boundary
This was not a global disappearance of AWS. Existing EC2 instances stayed healthy. DynamoDB global-table customers could reach replicas in other regions, although replication lag increased. Architecture still changed the outcome.
The point
A provider region contains many services, but their control and recovery paths may share dependencies. Count control planes, not availability-zone icons.
Read the AWS post-event summary.
More incident dossiers
- Your spare zone needs room for your failure — Google Cloud
- A cloud told 495 customers: restore from your own backups — IDC Frontier (IDCF Cloud)
- Two gateways. One shared way to fail. — Microsoft Azure
- One failed AI request became 48 more — Microsoft Azure
- One suspended account cut off three clouds — Google Cloud / Railway
- Multi-AZ did not survive the region — AWS
- Cloudflare went down, too — Cloudflare
- Azure’s global front door closed — Microsoft Azure
All cloud outage evidence → · Test your cloud exit readiness →