Cloudflare Outage History

Cloudflare One Client users experienced device registration issues that required them to re-register their devices, affecting Cloudflare Sites and Services and Zero Trust components. The incident lasted 3.5 hours before a fix was implemented and monitoring began.

Cloudflare experienced increased HTTP 5xx errors affecting network performance for 3.8 hours. The issue impacted web services and applications relying on Cloudflare's infrastructure, causing server error responses for end users. Cloudflare identified the root cause and implemented a fix, then monitored the results to ensure resolution.

Cloudflare experienced elevated error rates and high latency for Durable Objects and R2 Buckets in the APAC region, affecting multiple services including Stream, Cache Reserve, Images, and Cloudflare Sites and Services. The incident lasted 3.2 hours before a fix was implemented and monitoring began.

Cloudflare experienced increased latency in Workers Builds via webhooks from git providers, causing longer wait times when building projects from git connections. The issue affected Cloudflare Sites and Services and Workers Builds components, while production Workers remained unaffected. The problem was identified and resolved with a fix implementation after 1.6 hours.

Cloudflare experienced billing subscription service issues that prevented customers from processing changes to their Argo Smart Routing subscriptions for 2.1 hours. The problem was isolated to billing functionality, with all other Cloudflare services operating normally. The incident was classified as minor and has since been resolved.

Cloudflare experienced delays in container scheduling that affected their sites, services, and container infrastructure for 3.5 hours. The issue impacted the deployment and management of containerized applications across Cloudflare's platform. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced an issue where Health Check Events analytics displayed incorrect round-trip time values, with users seeing abnormally large latency values on their dashboards. The actual health check functionality and monitoring continued to operate normally, with only the analytics data being affected. The incident lasted 24 minutes and was resolved.

Cloudflare experienced network congestion in Eastern America and EU regions that caused increased HTTP 5xx errors across Cloudflare sites and services. The incident affected users' ability to access websites and services routed through Cloudflare's network in these regions for 11.7 hours. Cloudflare implemented a fix to address the network congestion and continued monitoring to ensure service stability.

Cloudflare experienced a major incident affecting WARP device configuration changes and registrations, causing material delays for users trying to configure their devices. The issue impacted Cloudflare Sites and Services and Zero Trust components for 5.6 hours. Cloudflare identified the root cause, implemented a fix, and monitored the results to ensure service restoration.

Cloudflare experienced an issue affecting a subset of KV API requests, causing increased latency and timeouts, while Workers using Assets also encountered errors. The incident impacted Cloudflare Sites and Services, Workers, and Workers KV components for 19.5 hours. A fix was implemented and the service was being monitored for stability.