Cloudflare Outage History

Cloudflare experienced network performance issues at their Osaka, Japan datacenter (KIX) that affected Cloudflare Sites and Services and Network components. The incident was classified as minor and lasted 22 minutes. Cloudflare investigated and worked to analyze and mitigate the performance problems during this period.

Cloudflare's Workers API and GraphQL API experienced increased errors for 13.7 hours, causing delays in Cron Trigger changes while leaving already deployed Workers and existing Cron Triggers unaffected. The incident also impacted Cloudflare Sites and Services, Analytics, and API components. A fix was implemented and the service was placed under monitoring.

Cloudflare experienced an issue where schema validation block reasons were not displaying in the dashboard when requests were blocked. This affected Cloudflare Sites and Services and API Shield components for 25.8 hours. The issue was identified and a fix was implemented to restore proper display of block reasons and descriptions in the dashboard.

Cloudflare experienced an issue with AI Gateway that caused an increase in errors for customers using the service. The incident affected AI Gateway and Cloudflare Sites and Services for 13 minutes. A fix was implemented and the service was restored to normal operation.

Cloudflare's request trace feature experienced failures for some cacheable assets, returning 400 Bad Request errors instead of successful traces. The incident affected Cloudflare Sites and Services and the Trace component. The issue was resolved after 2.5 hours.

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.