Redazione RHC : 18 November 2025 16:10
November 18, 2025 – After hours of widespread disruptions , the incident affecting Cloudflare’s global network finally appears to be nearing resolution. The company announced it has implemented a fix and is now actively monitoring the situation, following a day of outages, intermittent errors, and issues with application and security services.
The incident, which began at 11:48 UTC , affected multiple components of Cloudflare’s infrastructure, causing slowdowns, timeouts, and crashes globally, also impacting the CDN, API, authentication, and management dashboard.
Below is the complete reconstruction of the day.
11:48 UTC – Start of the incident
Cloudflare reports an internal service degradation. Several services are globally unstable, and the issue is being investigated.
12:03 UTC – Investigation underway
Cloudflare confirms that some services continue to be affected by intermittent errors.
12:21 UTC – First evidence of partial recovery
Cloudflare sees improvements, but customers are still experiencing higher-than-usual errors.
12:37 UTC – Investigation still active
Widespread anomalies persist on the network.
12:53 UTC – Investigation still ongoing
Technicians continue to work without yet finding a definitive solution.
13:04 UTC – WARP access to London temporarily disabled
During mitigation efforts, Cloudflare disabled WARP in the London region. Local users were unable to connect to the service.
13:09 UTC – Problem identified
Cloudflare announces that it has identified the cause of the incident and has begun implementing a fix.
13:13 UTC – Partial restoration of Access and WARP
Cloudflare restores Access and WARP, bringing error levels back to normal.
WARP London is back online. Work continues on the remaining application services.
13:35 UTC – Problems still present
Application services have not yet been fully restored.
13:58 UTC – Work in progress
Work continues to bring the remaining services back online.
14:22 UTC – Dashboard reset
The Cloudflare dashboard is back up and running, although application services are still experiencing instability.
2.34pm UTC – Restoration work continues
The technical team is continuing with the necessary activities to restore all services.
2:42 PM UTC – Cloudflare: “Incident resolved, monitoring ongoing.”
Cloudflare announces it has implemented a permanent fix. All services should gradually return to normal, but post-incident monitoring remains active.
The incident had a significant global impact. Many websites served by Cloudflare (including redhotcyber.com) experienced slowdowns, unreachable pages, 502, 522, and 526 errors, as well as caching and routing issues.
Security and authentication services, such as Cloudflare Access and WARP, were severely impacted in the initial phase. In some regions, users were unable to authenticate or access protected resources.
Downdetector also showed signs of malfunction, making it difficult to monitor the extent of the incident and contributing to the perception of a widespread outage.
Cloudflare’s global infrastructure has experienced slowdowns and instability, with knock-on effects for services not directly hosted on the platform.
Cloudflare WARP is a service developed by Cloudflare with the goal of improving the security and performance of users’ internet connections . Unlike traditional VPNs, which primarily focus on providing anonymity by routing all traffic through remote servers, WARP is designed to make browsing faster, more stable, and more secure, without slowing down your connection.
WARP uses the WireGuard protocol, known for being lightweight, fast, and highly secure. Traffic is routed through Cloudflare’s global network, which acts as a “protective layer” between the user and the web. This allows for:
It doesn’t aim for complete anonymity like a traditional VPN, but focuses on security and connection stability.
Cloudflare offers two versions of the service:
According to the latest update, the fix has been successfully applied and services are returning to normal. Cloudflare is now actively monitoring the situation, and residual instability may occur in the coming hours as the network settles.
Redazione