Cloudflare Outage History

Cloudflare experienced increased HTTP 530 errors affecting websites with ".cloud" and ".tech" domains that were routed through the Atlanta (ATL) data center. The incident impacted traffic in the North America region for 26.3 hours. A fix was implemented and the service was restored to normal operation with monitoring in place.

Cloudflare experienced increased latency issues with their Workers API that affected Cloudflare Sites and Services and Workers components for 4.7 hours. The issue was identified and a fix was implemented, with API latency returning to normal levels. The team continued monitoring to ensure stability after resolution.

Cloudflare experienced network performance issues affecting customers in the Jakarta, Indonesia area for 21.6 hours. The incident impacted Cloudflare Sites and Services in the Jakarta (CGK) region. The issue was identified and a fix was implemented to resolve the performance problems.

Cloudflare Pages API experienced an increased error rate that affected the Workers & Pages section in the Cloudflare Dashboard and Workers Builds functionality. The incident lasted 5 minutes and impacted Pages, Workers, and Workers Builds components. Deployed Workers and Pages projects remained unaffected during the incident.

Cloudflare experienced an increased rate of HTTP 530 errors affecting traffic routed through their Atlanta (ATL) data center, impacting websites across a limited number of top-level domains. The incident lasted 4.4 hours and primarily affected users in the North America region accessing services through the Atlanta location. A fix was implemented and the service was restored to normal operation with monitoring in place.

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.