Cloudflare Outage History

Cloudflare experienced network performance issues in Mumbai, India that caused increased latency and intermittent errors for a subset of users in the region. The incident affected the Asia, Mumbai, India (BOM) component and lasted 53 minutes. A fix was implemented and the service was restored to normal operation with monitoring in place.

Cloudflare experienced degraded processing of Load Balancing health events, causing delays in health monitoring notifications, analytics, and steering decisions for some customers. The issue affected Cloudflare Sites and Services along with Load Balancing and Monitoring components for 55 minutes. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced performance degradation at one of their Los Angeles POPs from 20:32 to 20:53 UTC, affecting CDN/cache services and sites in the North America region. The issue was mitigated and resolved within the 21-minute window.

Cloudflare experienced increased 300* errors affecting WAF challenges and Turnstile challenges for 1.8 hours. The issue impacted Cloudflare Sites and Services, Challenge Platform, and Turnstile components. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced an issue affecting the Pages API, Pages Builds, and Workers Builds from 20:22 to 20:50 UTC on March 18th, 2026. Customers encountered elevated 500 errors and build failures during this 28-minute incident. The issue has been identified and resolved.

Cloudflare experienced dashboard login issues where authentication attempts were silently failing, particularly affecting SSO-based logins. The incident impacted the Cloudflare Dashboard and Sites and Services components for 1.4 hours. The issue was under investigation with no resolution details provided in the available updates.

Cloudflare experienced issues with their Dashboard and API services for 27 minutes, causing request failures and error displays for customers trying to access these management interfaces. The incident did not impact CDN file serving or edge security features, so end-user website performance remained unaffected. A fix was implemented and the service was restored to normal operation.

Cloudflare R2 customers experienced incomplete assets and broken connections when receiving 206 (partial content) responses, affecting Cloudflare Sites and Services and R2 storage. The issue was identified after approximately 2 hours of investigation, and a fix was implemented and rolled out. The incident lasted 11.3 hours total before resolution.

Cloudflare Analytics experienced degraded performance in the US region for 7.5 hours, affecting users' ability to access certain datasets through the GraphQL API. The issue caused delays in data availability and impacted Cloudflare Sites and Services along with Analytics components. The problem was identified and a fix was implemented to resolve the service disruption.

Cloudflare experienced increased HTTP 520 errors specifically affecting HEAD requests for 4.2 hours. The issue was identified and a fix was implemented to resolve the problem.