Loading story…
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.
See attribution, scope, and your downstream exposure.
3 events from the most recent confirmed update back to the earliest known activity.
A later Cloudflare outage again caused error messages across the internet, indicating a separate recurrence of broad service disruption. The reference points to this event as occurring in November 2025.
A major outage involving Cloudflare caused error messages and service problems across the internet, affecting platforms such as Google Home, Spotify, Snapchat, Google, and OpenAI. Multiple outlets reported tens of thousands of user outage reports during the disruption.
A Microsoft outage linked to the broader CrowdStrike incident shut down Starbucks' mobile order-ahead app, causing service disruption for customers. This was a separate major outage event from the later Cloudflare-related incidents.
See attribution, scope, and whether this vendor sits anywhere in your supply chain.
4 references tracked. Mallory keeps watching after this page renders.
theguardian.com
Open sourcecbsnews.com
Open sourcetheverge.com
Open sourcecbsnews.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 major outage at Cloudflare led to widespread internet disruptions, impacting numerous high-profile services including X (formerly Twitter), ChatGPT, Spotify, League of Legends, and Downdetector. Users around the world reported being unable to access these platforms, with outage tracking sites themselves also affected due to their reliance on Cloudflare's infrastructure. Cloudflare confirmed the issue as a global network problem and stated that they were actively investigating and working to restore services, though no immediate resolution timeline was provided. The outage was notable for its global reach and the number of critical internet services affected, highlighting the central role Cloudflare plays in web infrastructure. The incident drew comparisons to previous large-scale outages involving Cloudflare and other cloud service providers, raising concerns about the resilience of the internet's backbone services. As of the latest updates, Cloudflare teams continued efforts to remediate the issue and restore normal operations for all impacted customers.
Jun 29, 2026
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
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