Cloudflare, a key provider of internet security and performance services, encountered a global network outage on November 18, 2025, affecting numerous websites and users worldwide.
The disruption caused users to face issues such as spinning wheels, error messages, and other failures, including infinite loops in human verification processes. Cloudflare’s own support portal was also affected, making it difficult for IT administrators to submit tickets. Users reported common errors, including 502 and 504 Bad Gateway messages, across thousands of affected websites.
The irony of the situation was not lost on users, as Downdetector.com, a popular site for reporting service disruptions, relies on Cloudflare for bot protection. Attempts to access Downdetector resulted in a blank white screen and an error message, further complicating efforts to report the issue. The error message stated: “Please unblock https://www.google.com/url?sa=E&source=gmail&q=challenges.cloudflare.com to continue,” stemming from a failed challenge loaded from challenges.cloudflare.com, a service central to Cloudflare’s bot mitigation.
Cloudflare’s official status page, Cloudflarestatus.com, confirmed the problem at 11:48 UTC on November 18, 2025, with an update reading: “Cloudflare Global Network experiencing issues. Investigating – Cloudflare is aware of, and investigating an issue which potentially impacts multiple customers. Further detail will be provided as more information becomes available.”
The outage coincided with scheduled maintenance in several data centers, including LAX (Los Angeles), MIA (Miami), GUA (Guatemala City), ATL (Atlanta), and ORD (Chicago). While Cloudflare typically reroutes traffic during maintenance to minimize impact, the scale of simultaneous updates across these locations indicated a possible complication during the process or a separate incident.
Users in or routed through these regions experienced higher latency due to rerouting. However, the widespread nature of the errors pointed to a broader issue affecting the entire global network, beyond the specific maintenance sites. For those impacted, the issue was server-side, originating from Cloudflare’s infrastructure.
Recommendations for affected users included avoiding actions such as clearing caches, cookies, or restarting routers, as these would not resolve failures in challenges.cloudflare.com. Users were advised to wait, noting that Cloudflare engineers typically progress from “Investigating” to “Identified” and “Fixing” within minutes to an hour. The event underscored Cloudflare’s extensive role in supporting a large portion of the internet’s security and speed functions, with reports emerging around noon UTC as the company actively probed the cause.
