Cloudflare, a key provider of internet security and performance services, encountered a global network outage on November 18, 2025. The disruption affected numerous websites, login portals, and support dashboards worldwide, leaving users facing spinning wheels, error messages, and other failures.
Users reported infinite loops in human verification processes, where browser checks to confirm humanity remained stuck. Cloudflare’s own support portal also experienced difficulties, preventing IT administrators from submitting tickets easily. Common errors included 502 and 504 Bad Gateway messages appearing across thousands of affected websites.
The outage created an irony for users seeking confirmation of the problem. 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 stating: “Please unblock https://www.google.com/url?sa=E&source=gmail&q=challenges.cloudflare.com to continue.” This issue stemmed from a failed challenge loaded from challenges.cloudflare.com, the 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. The update read: “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. Active or recently completed work occurred in 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, combined with the global alert, 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 is server-side, originating from Cloudflare’s infrastructure. Recommendations 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. Reports emerged around noon UTC, with the company actively probing the cause.
