Amazon Details Root Cause of Previous AWS Outage

Amazon Details Root Cause of Previous AWS Outage
Above: An illustration photo shows the Amazon logo in a smartphone in Suqian, Jiangsu, China on Oct. 20, 2025. Image credit: CFOTO/Future Publishing/Getty Images

The Facts

  • Amazon has revealed that a software bug in Amazon Web Services' (AWS) automated DNS management system for DynamoDB triggered a condition that deleted IP addresses for the regional endpoint in the US-EAST-1 region, preventing connections to the database service — resulting in a widespread service disruption earlier this week.
  • The outage began at 11:48 p.m. PDT on Monday and involved three distinct periods of disruption, including increased API error rates for DynamoDB and connection errors for Network Load Balancer in the Northern Virginia region.
  • Services dependent on DynamoDB experienced failures, such as EC2 instance launches that returned insufficient capacity errors due to timed-out leases in the DropletWorkflow Manager subsystem after the database disruption.

Sources Split


The Spin


Narrative A

AWS fixed that DynamoDB bug in hours, showing that its infrastructure deftly handles massive scale and keeps the digital world humming. Outages like this are rare blips that highlight smart moves like multi-region redundancy to bounce back fast. Betting on AWS drives innovation without the hassle of building everything from scratch.

Narrative B

Handing the internet's backbone to AWS and a couple of giants invites chaos, as this outage crippled services worldwide from one faulty region. Locking into these providers traps businesses in high-risk dependency that demands breaking free with multi-cloud strategies and sovereign infrastructure. Spreading out to edge computing slashes vulnerabilities and secures true digital independence.


Go Deeper

© 2026 Improve the News Foundation. All rights reserved.Version 7.18.2

© 2026 Improve the News Foundation.

All rights reserved.

Version 7.18.2