2025 Cloudflare Global Access Outage

The 2025 Cloudflare Global Outage is a widespread network disruption that occurred on November 18, 2025, on the systems of internet infrastructure provider Cloudflare, affecting numerous online services worldwide.

The outage began with the detection of an “unusual traffic spike” in a portion of the traffic passing through Cloudflare’s network. According to Cloudflare’s statement, the incident caused errors and access issues for some services.

Cloudflare is an infrastructure provider that manages approximately 20% of global web traffic. The company helps websites and applications load faster while also providing protection against “distributed denial of service (DDoS)” attacks.

The outage caused service disruptions on platforms such as X (Twitter), ChatGPT, YouTube, e-Devlet, Shopify, Spotify, Zoom, Microsoft Teams, Visa, Vodafone, M&S, Asda, Canva, Indeed, Claude, and Truth Social.

Cloudflare confirmed that the incident had a global impact on the internet and announced that the issue had been “identified and is being fixed.” Company statements indicated that the problem was largely resolved within a few hours.

According to updates on Cloudflare’s status page, access issues gradually decreased, and the majority of systems returned to normal by the afternoon of the same day.

Social media applications (AA)

Start of the Outage and Timeline

The Cloudflare outage began affecting users globally on the morning of Tuesday, November 18, 2025. According to the company, the issue started around 11:20 UTC with the detection of an unusual traffic spike on one of its services. Cloudflare’s statement read: “At 11:20 UTC we observed an unusual traffic spike on one of our Cloudflare services. This caused some traffic passing through our network to encounter errors. Our entire team is on duty to ensure all traffic is delivered without error.”

By 11:48 UTC, Cloudflare announced an “internal service degradation.” In its statement at that time, the company reported that efforts were underway to restore services.

Between 12:03 and 12:53 UTC, the company shared status updates stating, “We are continuing to investigate this issue.” In the update at 12:21 UTC, it added: “We are seeing services stabilize, but customers may continue to experience higher-than-normal error rates as our remediation efforts continue.”

At 13:04 UTC, Cloudflare stated, “We have temporarily disabled WARP access in London.” Between 13:09 and 13:13 UTC, further statements confirmed: “The issue has been identified and a fix is being applied,” and “We have re-enabled WARP access in London.”

According to information reported by Business Insider, Cloudflare confirmed the internal service degradation at 6:48 a.m. ET. Approximately thirty minutes later, the company noted that some services had stabilized but added: “Customers may continue to observe higher-than-normal error rates as our remediation efforts continue.”

According to a report by The Guardian, Cloudflare engineers conducted scheduled maintenance activities on the same day at data centers in Tahiti, Los Angeles, Atlanta, and Santiago. It was not clarified whether these maintenance activities were directly related to the outage.

According to CNBC data, Cloudflare completed its system fix around 9:57 a.m. ET and stated: “We are continuing to monitor errors to ensure all services have returned to normal.” The incident was resolved within a few hours, and Cloudflare services returned to normal in the later part of the day.

Affected Services and Platforms

During the outage, numerous online platforms and services worldwide experienced access issues. According to sources including Downdetector, NetBlocks, Reuters, BBC, The Guardian, CNBC, and CNBC-e, the main platforms affected by the outage included X (Twitter), ChatGPT, YouTube, e-Devlet, Shopify, Indeed, Claude, Truth Social, Spotify, Zoom, Microsoft Teams, Canva, Visa, Vodafone, Asda, and Marks & Spencer (M&S).

Cause of the Outage

According to Cloudflare’s official statements, the exact cause of the outage has not yet been fully determined. The company reported that the incident resulted from an “unusual traffic spike.” A Cloudflare spokesperson stated: “We observed an unusual traffic spike directed at one of our Cloudflare services around 6:20 a.m.; this caused some traffic passing through our network to encounter errors. We do not yet know the cause of the unusual traffic spike. Our entire team is on duty to ensure all traffic is delivered without error.”

Financial Impact and Final Status

Following the Cloudflare outage, the company’s stock value experienced a decline. According to data from Reuters and CNBC-e, Cloudflare shares lost approximately 4 to 5 percent in pre-market trading. In its latest statement after the outage, the company reported that the system had largely recovered, but some users might experience brief errors accessing their control panels.