Tutorial
Non-functional Application Requirements: Availability
DEV · By Oluwasegun Adedigba ·
The Brief
- On October 19, 2025 at 11:48 PM Pacific, two copies of the automation managing DynamoDB's DNS in us-east-1 raced each other.
- The race left the Regional DynamoDB endpoint with an empty DNS record.
- DNS was restored by 2:25 AM, but the outage continued after that.
Why it matters
A race condition in DNS automation can remove a regional endpoint entirely, so availability requirements need to account for failures in control-plane dependencies, not just application code.
Who’s affected
- Engineers writing availability requirements for cloud-hosted systems
- Teams relying on AWS us-east-1
At 11:48 PM Pacific on October 19, 2025, two copies of the automation that manages DynamoDB's DNS in us-east-1 raced each other and left the Regional endpoint with an empty DNS record. DNS was back by 2:25 AM, but the outage wasn't over. EC2's host-management system depends on…
Timeline
Two copies of the DynamoDB DNS management automation race each other, leaving the us-east-1 Regional endpoint with an empty DNS record
DNS is restored by 2:25 AM, while the wider outage continues
DEV Community: ai
Non-functional Application Requirements: Availability