Cloudflare experienced widespread service disruptions for much of Tuesday, affecting a broad range of customers who rely on its global network for security, content delivery, and connectivity services. The company reported internal service degradation beginning shortly after midday UTC, with users across multiple regions seeing intermittent failures, elevated error rates, and difficulty accessing application services.
According to Cloudflare status updates, the incident was first logged at 12:03 UTC when engineers opened an investigation into what they described as an internal service issue. As the outage unfolded, the company noted that some services were recovering but customers would continue to observe higher than normal error rates while remediation efforts continued.
By early afternoon, the disruption had extended to Cloudflare Access and WARP, the company’s secure connectivity products. At 13:04 UTC, Cloudflare disabled WARP access in London as part of its attempts to stabilise the system. Users in the city were unable to connect to the Internet via WARP during this period. At 13:13 UTC, Cloudflare confirmed that Access and WARP had recovered to pre incident error levels and that WARP had been re enabled in London.
Cloudflare engineers identified the root cause at 13:09 UTC and began implementing a fix. Nonetheless, the company cautioned that application services customers might continue to experience difficulties as restoration work proceeded. Throughout the early afternoon, successive updates indicated that teams were still working to restore broader services.
At 14:34 UTC, Cloudflare reported that dashboard services had been restored, marking one of the first major components to return to normal operation. Eight minutes later, at 14:42 UTC, the company announced that it believed the incident had been resolved following the deployment of a fix. Cloudflare added that it would continue monitoring performance to ensure all systems had stabilised.
The multi hour outage highlights the significance of Cloudflare’s infrastructure, which supports millions of websites, applications, and organisations globally. While the company has not yet provided further detail on the cause of the degradation, it emphasised that engineering teams moved quickly to isolate the issue, implement fixes, and restore services progressively throughout the day.
