Cloudflare Outage History

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.

Cloudflare experienced an issue with their IPv4 ranges page (https://www.cloudflare.com/ips-v4) where customers received HTTP 500 errors when attempting to view the published list of Cloudflare IPv4 ranges. The problem was isolated to this specific page on the marketing site and did not impact any production services including CDN, DNS, or security features. A fix was implemented after 1.4 hours and the service was restored to normal operation.

Cloudflare experienced network performance issues affecting their Johannesburg (JNB) data center in South Africa for 48 minutes. The issue was identified and a fix was implemented within approximately 15 minutes of initial detection. The service was then placed under monitoring to ensure the resolution was effective.

Cloudflare experienced an availability issue with Durable Objects in some regions, including the Middle East/Riyadh area, causing customers to encounter elevated error rates and timeouts when Workers attempted to invoke Durable Objects. The incident lasted 1.5 hours and affected Cloudflare Sites and Services. Cloudflare was actively investigating and working to mitigate the problem.