Loading story…
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.
See attribution, scope, and your downstream exposure.
6 events from the most recent confirmed update back to the earliest known activity.
Follow-up reporting on 2025-11-19 and 2025-11-20 said the outage was traced to an automatically generated configuration file or related internal database process used for security management, which triggered the failure. The disclosures provided more technical detail on how an internal systems error cascaded into a global service disruption.
After service restoration, Cloudflare said it would conduct a thorough investigation and improve safeguards to prevent similar incidents. Coverage also noted the event's broader implications for resilience planning and dependence on centralized cloud and CDN providers.
By 2025-11-19, Cloudflare and subsequent reporting said there was no evidence of malicious activity behind the outage. The company attributed the disruption to an internal technical failure, variously described as a configuration error, software crash, or database-related issue.
Roughly three hours into the outage on 2025-11-18, Cloudflare implemented a fix and most impacted services were largely restored by about 10:00 a.m. ET. Some residual issues persisted as internet services gradually recovered.
As the outage spread on 2025-11-18, Cloudflare acknowledged a global network issue and began investigating. Reporting indicated the disruption also affected Cloudflare's own dashboard and API, underscoring the breadth of the incident.
On 2025-11-18, Cloudflare suffered a major global network outage that began around 11:48 UTC / before 7:00 a.m. ET, causing widespread 500 errors and knocking many services offline. Affected platforms reported to include X, ChatGPT, Spotify, Discord, Shopify, Coinbase, Canva, Grindr, and other major websites and apps.
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.
darkreading.com
Open sourcegovinfosecurity.com
Open sourcekrebsonsecurity.com
Open sourcedarkreading.com
Open sourcebleepingcomputer.com
Open sourcesecurityonline.info
Open sourcehelpnetsecurity.com
Open sourcescworld.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 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
Cloudflare experienced a significant outage that caused widespread 500 Internal Server Errors across numerous major websites, including LinkedIn, Zoom, Canva, and X. The disruption was traced to a change in Cloudflare's web application firewall (WAF), which was updated to mitigate a newly disclosed industrywide vulnerability in React Server Components. The outage also impacted Cloudflare's own dashboard and APIs, with users and service trackers like DownDetector reporting thousands of connection issues. Cloudflare confirmed that the incident was not the result of a cyberattack but rather an internal deployment intended to enhance security against potential exploitation of the React flaw. The outage, which began around 8:47 GMT, was quickly investigated and a fix was implemented, allowing affected services to come back online. This event underscores the risks associated with rapid security mitigations in complex, widely used infrastructure, as even well-intentioned updates can inadvertently disrupt global internet services. Cloudflare noted that this was the second outage in a month, though the causes were unrelated, highlighting the challenges faced by major service providers in balancing security and availability.
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