Cloudflare Outage History

Cloudflare experienced DNS resolution issues for .de domains lasting 17.9 hours, caused by DNSSEC signing problems at DENIC (the .de domain registry). The incident affected Cloudflare Sites and Services and Recursive DNS, impacting users' ability to access German websites. Cloudflare resolved the issue by temporarily disabling DNSSEC validation for .de domains on their 1.1.1.1 resolver, allowing .de domains to resolve normally until DENIC fixed their signing problems.

Cloudflare experienced a 51-minute delay in processing network analytics across their L4 DDoS protection products, affecting Network Analytics dashboards and real-time alert delivery for Cloudflare Sites and Services, Magic Firewall, Magic Transit, Network, and Spectrum components. DDoS mitigation functionality remained unaffected throughout the incident. The issue was resolved after implementing a fix and monitoring the results.

Cloudflare experienced a major outage lasting 5.6 hours that disrupted Cloudflare Tunnel connections and Browser Isolation sessions due to internal service restarts across their edge infrastructure. The issue caused both new and existing connections to fail, forcing active tunnels and sessions to disconnect and attempt simultaneous re-establishment, resulting in elevated error rates and registration failures. The root cause was identified and a fix was implemented, with connection success rates returning to normal levels.

Cloudflare experienced a service incident where Workers Builds users encountered slower build start times due to increased build dequeue times. The issue affected Cloudflare Sites and Services along with Workers Builds for 2.9 hours. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced a 2-hour issue preventing customers from adding custom domains to their R2 storage service. The problem affected the domain configuration functionality but did not impact the ability to serve or upload R2 objects. The issue was identified and resolved with a fix that is currently being monitored.

Cloudflare's Bot Management feature experienced issues where detection rules 50331648 and 50331649 were unexpectedly matching and flagging legitimate traffic, causing customers to see an abnormal increase in bot detections starting April 1st, 2026. The affected Bot Management rules were disabled globally to prevent further impact, requiring a 326-hour resolution period for system stabilization. The detections were gradually re-enabled through a phased rollout after extensive monitoring confirmed system stability.

Cloudflare experienced network performance issues in their Ashburn, VA data center that affected Cloudflare Sites and Services in North America for 1.5 hours. The problem was identified as affecting a subset of Cloudflare Network Interconnects (CNI) 2.0 only. The issue was identified and a fix was implemented to resolve the performance degradation.

A network hardware failure in Cloudflare's Hong Kong data center caused reduced redundancy for approximately 5 hours, affecting Cloudflare Sites and Services in the Asia region and Cloud Network Interconnect services. The issue was identified and resolved with a fix that restored normal operations.

Cloudflare experienced an incident affecting Workers Builds where users encountered increased build dequeue times and some builds became stuck in a queued state indefinitely. The issue impacted Cloudflare Sites and Services along with Workers Builds functionality. The incident was resolved after 1.7 hours.

Cloudflare experienced an issue where a subset of Workers Analytics queries were returning 403 errors, affecting the Analytics component while leaving Analytics Engine event writing unimpacted. The incident was classified as minor and lasted 14 minutes. Cloudflare identified the problem and worked to mitigate it.