Loading story…
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.
See attribution, scope, and your downstream exposure.
3 events from the most recent confirmed update back to the earliest known activity.
Following the October outages, advocacy groups including Public Citizen and the Tech Oversight Project called on the U.S. Federal Trade Commission to scrutinize cloud market concentration and assess systemic risks tied to dominant providers such as Amazon. Their appeal framed hyperscaler dependence as a resilience and accountability issue.
An AWS outage began on 2025-10-19 and disrupted large portions of the internet, affecting hundreds of organizations and millions of users. Amazon attributed the incident to a software bug in DynamoDB and subsequent repair actions.
A later October 2025 Microsoft Azure outage disrupted internet services and was attributed by Microsoft to an inadvertent tenant configuration change in Azure Front Door. The incident was cited alongside the AWS outage as another major hyperscaler failure with broad downstream impact.
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.
3 references tracked. Mallory keeps watching after this page renders.
infoworld.com
Open sourcecyberscoop.com
Open sourceblogs.infoblox.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.
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.
Jun 29, 2026
Microsoft experienced a widespread outage impacting Azure, Microsoft 365, and related services, affecting customers and organizations worldwide. The disruption began around 16:00 UTC and was attributed to DNS issues, resulting in degraded availability for services such as Azure Front Door, the Azure Portal, Intune, Exchange admin center, and authentication services. Major companies and sectors, including payroll providers, healthcare organizations, and the Dutch railway system, reported significant operational impacts, with users unable to log in or access critical business platforms. Microsoft acknowledged the outage, provided mitigation advice such as using programmatic access methods and failover strategies, but did not immediately offer an estimated time for resolution. The outage's effects were felt across a broad spectrum of industries, with reports of internal workflow disruptions and delays in essential services like payroll processing. Microsoft advised customers to consider implementing failover strategies using Azure Traffic Manager and to monitor the Azure status page for updates. The incident highlighted the critical dependency of global businesses on Microsoft's cloud infrastructure and the cascading impact of DNS-related failures on authentication and service availability.
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