Cloudflare Outage History

Cloudflare experienced an issue with RealtimeKit affecting Android users running version 1.6.0 and higher, impacting Cloudflare Sites and Services. Users were advised to downgrade to version 1.5.7 as a temporary workaround while Cloudflare identified and implemented a fix. The incident lasted 2.7 hours before being resolved.

Cloudflare Radar experienced response delays for 2 hours, affecting the Radar service and associated Cloudflare Sites and Services. While the services remained fully operational throughout the incident, users experienced slower response times. The issue was resolved and services returned to normal performance, with continued monitoring to ensure complete resolution.

Cloudflare experienced elevated latency affecting Durable Objects and R2 API requests in the Western North America region for 57 minutes. Users encountered timeouts and increased response times when accessing these services. The incident also impacted Cloudflare Sites and Services during this period.

Cloudflare experienced a dashboard display issue where Account API Tokens were incorrectly shown as User API Tokens, affecting the Cloudflare Dashboard interface. The issue was purely visual and did not impact existing API token functionality or API operations. The problem was identified and resolved within 34 minutes.

Cloudflare experienced CNI (Cloud Network Interconnect) performance issues affecting connectivity through the Newark, NJ data center, with customers using Equinix Cloud Connect experiencing intermittent connectivity or complete service loss. The incident impacted Cloudflare Sites and Services along with CNI services for 6.4 hours. The issue was identified and a fix was implemented to resolve the connectivity problems.

Cloudflare experienced a domain registration service outage that prevented customers from registering new domains for 2.6 hours. The issue affected the Registrar component along with general Cloudflare Sites and Services. The problem was identified and resolved with a fix implementation.

Cloudflare experienced an issue where WAF Challenge actions incorrectly forwarded challenge solve requests to origin servers instead of the original challenged requests, affecting customers globally. The incident impacted Cloudflare Sites and Services and Firewall components for 1.5 hours. The issue was under investigation with Cloudflare actively working on a resolution.

Cloudflare Pages experienced a 41-minute outage where builds failed to start or failed while running, affecting the Pages service and related Cloudflare Sites and Services. The issue prevented customers from successfully deploying their Pages projects during this period. Cloudflare implemented a fix and monitored the results to resolve the build failures.

Cloudflare experienced Gateway issues that impacted performance and connectivity for users accessing services through their Zero Trust Gateway. The incident affected both Cloudflare Sites and Services and the Gateway component specifically. A fix was implemented after 53 minutes of investigation and monitoring.

Cloudflare experienced performance degradation at their Paris, France data center (CDG) for 1.6 hours, causing some users in the region to encounter increased latency and timeouts. The incident affected Cloudflare Sites and Services, CDN/Cache functionality, and other Europe-based services. The service team investigated the issue and restored normal performance.