Cloudflare Outage History

Cloudflare experienced increased latency in their Custom Hostname API for SaaS customers, causing slow responses when adding new R2 subscriptions. The incident affected Cloudflare Sites and Services and SSL for SaaS Provisioning components, while existing Custom Hostnames continued operating normally. After 65.5 hours and multiple fix attempts, the issue was resolved with monitoring confirming the solution's effectiveness.

Cloudflare experienced a 5.1-hour incident where users of the Secrets Store encountered increased errors when accessing secrets through Workers. The issue affected Cloudflare Sites and Services along with the Workers platform. The incident was classified as minor severity and required ongoing investigation to resolve the access errors.

Cloudflare experienced delays in HTTP request analytics and reporting rollups for 46 minutes, while edge services remained fully operational. The incident affected Cloudflare Sites and Services and Analytics components. The issue was resolved after investigation and mitigation efforts.

Cloudflare experienced an issue affecting Pages uploads where customers encountered 502 errors when attempting to upload content. The problem impacted a subset of Pages users and lasted approximately 29.4 hours. Cloudflare identified the root cause and applied a fix, then monitored the results to ensure the issue was resolved.

A network routing issue at Cloudflare's Anchorage, AK data center disrupted Cloudflare Tunnel connections from May 14-28, 2026, causing customers to experience HTTP 522 errors and connection timeouts when their traffic routed through that location. The problem persisted for an extended period because Cloudflare's automated path-optimization systems incorrectly identified the degraded path as functional, preventing automatic failover from triggering. The issue was resolved by manually rerouting affected traffic to healthy data centers.

Cloudflare Analytics experienced degraded performance for 6 hours, causing customers to encounter elevated error rates and increased latency when accessing analytics data through the Cloudflare API. The incident affected Cloudflare Sites and Services along with the Analytics component. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced an issue where AI Gateway prompts were not being properly scanned for Data Loss Prevention (DLP), affecting the AI Gateway and Cloudflare Sites and Services. The incident was classified as minor and lasted 6 minutes. Cloudflare investigated and resolved the DLP scanning functionality for AI gateway prompts.

Cloudflare Workers Builds experienced increased queue times and slow build start times for 1.2 hours, affecting Cloudflare Sites and Services. The issue was identified and a fix was implemented, with monitoring confirming the resolution.

Cloudflare experienced elevated error rates affecting API requests for 24.9 hours, causing customers to encounter failures when making API calls. The incident impacted Cloudflare Sites and Services along with the API component. A fix was implemented and the service was monitored for stability.

Cloudflare experienced a DNS resolver issue within Zero Trust Gateway that affected customers in the FedRAMP High environment for 14 minutes. Users with WARP experienced DNS lookup failures and were unable to reach sites through Gateway, while commercial Gateway customers remained unaffected. The issue was identified and resolved with a fix implementation, followed by monitoring to ensure stability.