Cloudflare Workers Outage History

Cloudflare Workers experienced an issue where some requests were not correctly enforcing rulesets rate limiting counts, affecting Cloudflare Sites and Services, Workers, and Rules components. The incident lasted 12.9 hours and was resolved with a fix that restored proper rate limiting enforcement.

Cloudflare Workers AI experienced issues where customers encountered errors when making inference requests to the @cf/baai/bge-m3 model. The problem affected Cloudflare Sites and Services and Workers AI components for 4 hours. Cloudflare identified the root cause, implemented a fix, and is monitoring the results.

Cloudflare Workers experienced elevated 502 errors from certain locations, affecting multiple services including Cloudflare Sites and Services, CDN/Cache, R2, and Workers KV. The incident lasted 28 minutes, with a fix implemented and monitoring initiated to ensure resolution.

Cloudflare Workers experienced increased API latency for 1.5 hours, specifically affecting Workers Builds via webhooks from git providers. Customers experienced longer wait times when building projects from git connections, while production Workers remained unaffected. The issue was identified and a fix was implemented to resolve the latency problem.

Cloudflare Workers experienced a 19.4-hour incident where KV API requests suffered increased latency and timeouts, and Workers using Assets encountered errors. The issue affected Cloudflare Sites and Services, Workers, and Workers KV components, though KV access through bindings remained unaffected. A fix was implemented and the service was placed under monitoring.

The Cloudflare Workers AI Gemma 4 model experienced health issues for 4.2 hours, causing users to encounter elevated error rates when attempting to use the Gemma 4 model. The incident affected Cloudflare Sites and Services along with Workers AI, and was resolved after the issue was identified and a fix was implemented.

Cloudflare Workers experienced an increased level of errors in the Chicago data center, affecting customers running Workers scripts in that region. The incident impacted Cloudflare Sites and Services in the North America region, specifically the Chicago, IL location. The issue was resolved after 20 minutes of investigation and mitigation efforts.

Cloudflare Workers experienced an issue causing 1003/403 errors when Workers performed fetch() calls, affecting some Workers invocations and Cloudflare Sites and Services. The problem was identified after approximately 23 minutes of investigation, and a fix was implemented and rolled out to most customers within about 2.5 hours, with continued rollout for remaining affected customers. The incident lasted 7.8 hours total before full resolution.

Cloudflare Workers AI experienced issues where customers encountered errors when making inference requests to the @cf/openai/gpt-oss-120b model. The problem affected Cloudflare Sites and Services and Workers AI components for 1.3 hours. A fix was implemented and the service was restored to normal operation with monitoring in place.

The Cloudflare Workers API experienced increased errors for 13.7 hours, causing delays in changes to Cron Triggers while already deployed Workers and existing Cron Triggers remained unaffected. The incident also impacted the GraphQL API and affected multiple components including Cloudflare Sites and Services, Analytics, and the main API. A fix was implemented and the service was being monitored for resolution.