Cloudflare Outage History

Cloudflare experienced increased errors with R2 and Durable Objects in Eastern North America for 3.2 hours, also affecting Workflows, Queues, Cache Reserve, Cache Purge API, Worker uploads with R2 bindings, and Workflow instance creation. The service errors were resolved and systems returned to stable operation.

Cloudflare experienced a 13-minute incident where users were unable to edit existing Account level WAF rules, though zone level rules, new rule creation, and rule operation remained unaffected. The issue impacted Cloudflare Sites and Services and Rules components. A fix was implemented and monitoring confirmed the resolution.

Cloudflare Stream API experienced elevated error rates for 47 minutes, causing HTTP 503 errors when customers attempted to create or update videos and start/stop live broadcasts. Video playback remained unaffected throughout the incident. The issue was resolved after investigation and remediation efforts.

Cloudflare experienced issues with their Load Balancer API and dashboard, causing failed or delayed API requests and dashboard operation errors, along with delays in audit log delivery for some services. The incident affected multiple components including the API, dashboard, load balancing, monitoring, and audit logs, but did not impact cached content serving or edge security features. The service disruption lasted 39 minutes before being resolved.

Cloudflare experienced availability issues with their Browser Run API for 35 minutes. The service disruption affected users' ability to access the Browser Run API functionality. Cloudflare identified the root cause and implemented a fix to restore normal service operations.

Cloudflare experienced increased HTTP 502 errors affecting customers in the Hong Kong region for 21 minutes. The incident impacted Cloudflare Sites and Services and Network components. Cloudflare investigated and resolved the issue.

Cloudflare experienced issues with Email Sending via the Worker Binding where users received "Invalid email address: Invalid input" errors when the recipient list was formatted as an array. The problem affected email functionality for workers using array-formatted recipient lists over a 14.2 hour period. Cloudflare identified the root cause and implemented a fix, which is currently being monitored.

Cloudflare experienced increased HTTP 502 errors affecting customers in the San Jose, CA region for 8.2 hours. The incident impacted Cloudflare Sites and Services along with their network infrastructure. A fix was implemented and the service was restored to normal operation with monitoring in place.

A route leak at one of Cloudflare's upstream transit providers caused connection timeouts and errors for customers whose traffic traversed the affected network paths, impacting Cloudflare Sites and Services and R2 storage. The issue was identified and Cloudflare worked with the transit provider to implement a fix after 5.1 hours, with monitoring ongoing to ensure resolution.

Cloudflare experienced DNS resolver issues within their Gateway service at Chennai and Mumbai data centers, causing performance degradation and connectivity problems for users in those regions. Identity-based Gateway policies were not being enforced correctly during the incident. The issue was resolved after 20 minutes of investigation and mitigation efforts.