Loading story…
Amazon Web Services (AWS) experienced a significant outage originating in its US-East-1 region, which is one of the company's most critical data hubs. The incident began early Monday morning, with AWS reporting increased error rates and latency for multiple services, including EC2, Lambda, and DynamoDB. The root cause was identified as a Domain Name System (DNS) resolution failure affecting the DynamoDB API endpoint, which quickly cascaded to impact a wide array of dependent AWS services. As a result, dozens of major websites, applications, and online platforms worldwide became inaccessible or experienced severe slowdowns. Consumer-facing services such as Snapchat, Roblox, Fortnite, Zoom, Snapchat, Amazon Alexa, Ring, Robinhood, Max (HBO), Chime, Venmo, Epic Games, McDonald's, Lyft, Hulu, Disney+, Roku, Signal, and major telecom carriers like AT&T, Verizon, and T-Mobile were all affected. The outage also disrupted PC gaming platforms like Steam, online forums such as Reddit, and popular banking and financial apps, including Coinbase and Robinhood. Even Amazon's own services, including Amazon.com and Prime Video, suffered partial outages. The effects of the outage were not limited to North America; major banks in the UK and the European Union, such as Lloyds Banking Group, and some government sites also experienced downtime. AWS engineers worked on multiple parallel paths to accelerate recovery, applying initial mitigations and observing signs of service restoration within a few hours. The outage highlighted the critical dependency of the modern internet on AWS infrastructure, as disruptions in a single region can have global repercussions. AWS's service health dashboard confirmed that at least 28 separate AWS services were impacted during the incident. Customers were advised to retry failed requests and monitor for further updates as AWS continued to address the issue. The incident also affected global services or features that rely on US-East-1 endpoints, such as IAM updates and DynamoDB Global tables. Some AI services, including Perplexity, were also reported to be struggling during the outage. The event underscored the importance of DNS reliability and the potential for single points of failure within cloud infrastructure. AWS communicated regularly with customers throughout the incident, providing updates on the root cause and recovery progress. By the end of the morning, AWS announced that the outage had been resolved, and services were returning to normal operations. The widespread impact of this outage serves as a reminder of the interconnectedness of cloud services and the need for robust contingency planning for critical internet infrastructure.
See attribution, scope, and your downstream exposure.
6 events from the most recent confirmed update back to the earliest known activity.
On 2025-10-24, Amazon published its explanation of the outage, saying a major DNS failure and automation systems race condition created a single point of failure that triggered the widespread disruption. The post-mortem clarified the technical root cause behind the October 20 incident.
By 2025-10-21, follow-up coverage said the outage had affected more than 1,000 organizations and was being blamed on a DNS issue. The incident was also framed as evidence of concentration risk in cloud infrastructure.
AWS resolved the core technical problems by about 6:35 a.m. ET on 2025-10-20. Some customers and downstream services continued to experience aftereffects and backlogs even after the main fault was fixed.
AWS began mitigation around 5:22 a.m. ET as engineers worked to contain the DNS-related failure in US-EAST-1. Reporting indicated the company was actively restoring affected dependencies and service availability.
The AWS failure knocked offline or degraded numerous services, including Amazon properties, Prime Video, Fortnite, Roblox, Zoom, Snapchat, WhatsApp, ChatGPT, Venmo, Perplexity, and some UK government websites. Multiple reports described the event as a large-scale internet outage caused by heavy dependence on AWS infrastructure.
On 2025-10-20, Amazon Web Services suffered a major outage in its US-EAST-1 region. The disruption was tied to DNS resolution problems affecting DynamoDB API endpoints and quickly cascaded into broader service failures.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See attribution, scope, and whether this vendor sits anywhere in your supply chain.
17 references tracked. Mallory keeps watching after this page renders.
securityboulevard.com
Open sourcewired.com
Open sourcesecurityonline.info
Open sourcearstechnica.com
Open sourceeuronews.com
Open sourcezdnet.com
Open sourcehackread.com
Open sourcebleepingcomputer.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A series of high-profile cloud outages disrupted access to critical services across multiple sectors, affecting organizations such as Starbucks, crypto exchanges, and messaging platforms like Signal. The Amazon Web Services (AWS) outage, triggered by a software bug in DynamoDB, led to a 15-hour disruption in Northern Virginia data centers, while a subsequent Microsoft Azure outage was caused by a configuration error in Azure Front Door. These incidents exposed the fragility of digital infrastructure and raised concerns about the concentration of power among a few dominant cloud providers, prompting advocacy groups to call for increased regulatory scrutiny. The outages also underscored the essential role of DNS in business continuity, as failures in DNS resolution prevented customers and internal services from accessing critical database resources. Experts emphasized that DNS, as the foundational protocol for translating domain names to IP addresses, can create widespread disruptions when it fails, regardless of the underlying cause. The events reignited discussions about the need for greater resilience in both cloud and DNS infrastructure to mitigate the impact of future outages on businesses and the broader digital ecosystem.
Jul 3, 2026
Amazon confirmed that **drone strikes** physically damaged AWS facilities in the **Middle East (UAE) Region `me-central-1`** and the **Middle East (Bahrain) Region `me-south-1`**, triggering a prolonged outage affecting dozens of cloud services. AWS reported structural damage, disrupted power delivery, and in some cases fire-suppression activity that caused additional water damage; multiple Availability Zones remained impaired, including **`mec1-az2` and `mec1-az3`** in the UAE and a continuing localized power issue impacting **`mes1-az2`** in Bahrain. Amazon said it is restoring physical infrastructure while also pursuing software-based recovery paths and prioritizing tools that enable customers to back up and migrate workloads out of the impacted regions. Incident reporting on the outage described an “unusual physical incident” in `me-central-1` where external objects struck a data center, causing sparks and a fire that led authorities to require a full power shutdown (including backup generators), taking down **EC2 instances**, **EBS volumes**, and **RDS databases** in the affected zone. Customers also experienced significant impairment of **EC2 networking APIs** (including `AllocateAddress`, `AssociateAddress`, `DescribeRouteTable`, and `DescribeNetworkInterfaces`), with AWS using traffic-weighting and configuration changes to shift load and restore functionality, though some API recovery lagged and constrained actions like reassigning Elastic IPs. AWS advised impacted customers to back up data and migrate workloads to unaffected regions while recovery continued.
Jun 29, 2026
A widespread internet outage disrupted access to major online services including **Google Home**, **Spotify**, **Snapchat**, and **OpenAI**, with reports indicating that tens of thousands of users were affected. Coverage described broad service failures and error messages appearing across the internet, pointing to infrastructure problems that cascaded across multiple consumer and enterprise platforms rather than an isolated application failure. Reporting tied the disruption to **Cloudflare-related** infrastructure issues, underscoring how outages at a major internet delivery and security provider can quickly ripple across dependent services. The incident echoed other large-scale technology disruptions that have knocked major apps offline, highlighting the operational risk created when widely used digital platforms rely on a small number of critical backend providers.
Jul 12, 2026