In the early hours of Monday, 20 October 2025, Amazon Web Services experienced a disruption that affected a considerable portion of the global internet infrastructure. The event originated in the region known as US East 1, located in Northern Virginia. A vast number of services, commercial applications, public websites and private systems rely upon it either directly or indirectly.
What failed
AWS later clarified that the source of the disruption could be traced to two internal faults that occurred in proximity. The first fault involved the Domain Name System resolution layer for the DynamoDB service endpoint. DNS serves as the directory of the internet that converts names into machine reachable network addresses. In this case, applications attempting to reach DynamoDB found themselves unable to locate the service. The second fault arose in the internal system responsible for monitoring the health of load balancers within the EC2 network fabric. When the health monitoring subsystem failed to relay correct signals, the system could not determine which targets were functional or available. When these two faults occurred together, the disruption intensified. The most severe phase of the disruption lasted approximately fifteen hours.
What it broke
Reports appeared regarding interruptions in banking applications, mobile payment services, e-commerce platforms and media streaming services. Popular consumer communication platforms encountered login failures. Enterprises reported delays in batch operations, order handling and internal service automation. Home automation products that depend upon continuous cloud connectivity also experienced disruption. This served as a reminder that the modern household, no less than the modern workplace, now depends upon cloud services in ways that are often invisible until failure occurs.
Lessons for architects and operators
Reduce concentration risk — do not allow a single region to anchor identity, control planes or critical storage. Design true multi-region behaviour, not just replication but address identity, session state, routing logic and write strategy. Plan graceful degradation by permitting read-only modes, fallback caches and deferred writes. Map dependencies and maintain a live inventory of upstream and downstream services. Monitor the invisible layers by tracking DNS response quality, resolver health, load balancer status and internal health signals in addition to user-facing metrics.
What to fix next
Teams should begin with an audit that names every dependency pointing into US East 1. For each item, document its alternate path. Where possible, separate reads and writes so that a loss of the write path does not remove the entire service. Introduce caching with clear timeouts and limits. Build a failover runbook that any trained engineer can follow. Practice on a schedule. The October 2025 AWS outage serves as a sober reminder that our networks run on layers that are often unseen until they fail. DNS and load balancer health signals do not call attention to themselves during normal hours, yet they hold much of the structure together. Map the system. Remove silent single points of failure. Teach the service to bend without breaking. Do the work before the next storm.