Detailed breakdown of what happened with Amazon Web Services (AWS) - Outage

 



Here’s a detailed breakdown of what happened with Amazon Web Services (AWS) yesterday — the causes, the impact, and the deeper implications.


What happened

On October 20, 2025, early in the morning (around 07:11 UTC), AWS began experiencing a major outage in its key region US‑East‑1 (Northern Virginia).


The company reported “increased error rates and latencies for multiple AWS services in the US-East-1 region.”

The root issue was traced to an internal subsystem responsible for monitoring the health of network load balancers.

More specifically, there was a problem with DNS resolution of the API endpoint for Amazon DynamoDB in that region. DNS is the system that translates domain names (human‐friendly addresses) into IP addresses.

Because of how foundational that region and those services are, many downstream services suffered — including other AWS services as well as third‐party systems dependent on AWS.

The outage lasted for several hours; AWS reported that all the 142 services it had flagged as impacted were restored by around 18:53 ET that day.


What was impacted

Major apps & platforms: Snapchat, Signal, Fortnite, Reddit, Duolingo, Telegram (some reports) — among many others.

Financial services, telecoms, government services in multiple countries also reported disruption.

Smart-home / IoT devices and Amazon’s own internal services (including Amazon Alexa and Prime Video) took hits.


Why the cause is significant

The fact that a DNS resolution issue in one region cascaded into system-wide faults highlights how interconnected and brittle modern cloud infrastructure can be.

Even though AWS has many regions and redundant systems, a problem in a key region (US-East-1) that hosts foundational services can trigger broader failures. As one commentary put it:

“I thought that for companies like Amazon … multi region setup was standard. And yet, once us-east-1 is down, it's all over.”

This incident demonstrates a single point of systemic risk: many services (even those declared “multi-region”) depend on core control‐plane services located in US-East-1. When one of those fails, it brings down much more than that region alone.


Implications & lessons

For organizations using cloud services: This outage is a powerful reminder to evaluate dependencies not just at the customer layer but deeper (e.g., infrastructure layer, control plane, regional dependencies).

Multi-region isn’t a guarantee: You might distribute your front‐end across regions, but if core services (like DNS, load-balancer health monitoring, critical databases) still reference a single region or control plane, you’re vulnerable.

Risk of over-centralisation: The internet’s resilience is challenged when a small number of providers (AWS, Microsoft Corporation Azure, Google LLC Cloud) provide the backbone. The grouping of many critical services in one vendor’s region increases systemic risk.


Transparency and root‐cause clarity: AWS has reported the “potential root cause”, but detailed forensic reports may take time. For organizations, monitoring and governance of dependencies is more imperative.


What AWS reportedly is doing / what to watch

AWS has stated that they applied initial mitigations and are observing early signs of recovery.


They recommend customers retry failed requests and note some services might experience backlogs or latency even after restoration due to the accumulated load.


Going forward, one should watch for any formal AWS post-mortem (often published days/weeks later) that gives deeper insight into lessons learned, mitigations, and changes to prevent recurrence.

Comments

Popular posts from this blog

IBM goes big to keep quantum computers cold

IBM - avances en mantener adecuadamente fríos computadores cuánticos.

Estructura multinivel de los sistemas de agentes de IA