• AWS confirms significant API errors and connectivity issues affecting its critical US-East-1 region
  • The outage has cascaded across major consumer apps, enterprise tools, and smart devices worldwide
  • DNS resolution failures with DynamoDB API endpoint identified as the root cause of the service disruption

Amazon Web Services confirmed a major outage in its US-East-1 region on October 20, 2025, triggering widespread service disruptions that affected everything from consumer applications to enterprise tools and smart home devices. The incident represents one of the most significant cloud infrastructure failures this year, highlighting the persistent risks of concentration in critical cloud regions.

According to people familiar with the matter, the outage began around midday Eastern Time when DNS resolution failures started affecting AWS's DynamoDB API endpoint. The problems quickly cascaded across multiple services, creating a domino effect that impacted platforms including Snapchat, Fortnite, Slack, Asana, Docker, and Ring smart home devices. Banking applications and financial services relying on the region also reported connectivity issues.

"We're experiencing elevated error rates for multiple AWS services in the US-East-1 Region," an AWS spokesperson confirmed in a statement. "We're working to resolve the issue as quickly as possible." The company's service health dashboard showed multiple services affected, though efforts to reach specific executives for additional comment were unsuccessful.

The US-East-1 region, centered in Northern Virginia, represents AWS's largest and most critical infrastructure hub, hosting a disproportionate share of global internet traffic. This concentration has amplified the outage's impact, with companies worldwide reporting service degradation even when their primary infrastructure resides in other regions.

One technical lead at a major e-commerce platform, who asked not to be named because they weren't authorized to speak publicly, described the situation as "cascading failure at scale." The source explained that "even services with multi-region architecture are feeling the impact because so many dependencies route through US-East-1."

This isn't the first time the US-East-1 region has experienced significant downtime. Similar outages occurred in 2017, 2020, and subsequent years, often stemming from single points of failure in core infrastructure components like DNS, S3, or DynamoDB. The recurrence pattern has raised questions about whether AWS's rapid expansion has outpaced its ability to ensure regional resilience.

As service restoration efforts continue, the incident has reignited debates about cloud concentration risk and the need for more robust multi-region and multi-cloud strategies. Several companies reported activating disaster recovery protocols, though many found their backup systems also depended on AWS services affected by the outage.

Correction: An earlier version of this article misstated the specific time the outage began. The issues started around midday Eastern Time, not in the morning.