Cloudflare Workers Outage History

Cloudflare Workers experienced issues with subrequests returning 1006 errors, affecting Workers and Cloudflare Sites and Services for 2.3 hours. The problem was identified and a fix was implemented, with monitoring ongoing to ensure resolution.

Cloudflare Workers AI experienced availability issues affecting several AI models for approximately 1 hour. The incident impacted Cloudflare Sites and Services along with the Workers AI component. Cloudflare identified the root cause, implemented a fix, and restored service while monitoring for stability.

Cloudflare experienced an issue with the Workers Editor in their dashboard that prevented users from accessing the web-based code editor for 28 minutes. Customers could still deploy and update Worker code through alternative methods including Wrangler, Terraform, or the API during the outage. A fix was implemented and the service was restored to normal operation.

Cloudflare Workers experienced API failures that prevented customers from using the Workers API, though existing production Workers continued running normally. The incident affected Workers, Workers Builds, and Cloudflare Sites and Services for 28 minutes. A fix was implemented and monitoring confirmed the resolution.

Cloudflare Workers experienced slower build start times for 2.9 hours, with some Workers Builds users encountering increased build dequeue times. The issue affected Cloudflare Sites and Services along with Workers Builds components. A fix was identified and implemented, with monitoring confirming the resolution.

Cloudflare Workers experienced a service incident where some Workers Builds users encountered significantly increased build dequeue times, with some builds becoming stuck in a queued state indefinitely. The issue affected Cloudflare Sites and Services along with Workers Builds functionality. The incident was resolved after 1.7 hours.

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.