Cloudflare Workers Outage History

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

The Cloudflare Pages API experienced an increased error rate that affected the Workers & Pages section in the Cloudflare Dashboard and Workers Builds functionality. Deployed Workers and Pages projects continued to operate normally during the incident. The issue was resolved within 4 minutes.

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 an elevated number of 500 errors and build failures during this 28-minute incident. The issue has been identified and resolved.

Cloudflare Workers experienced an increased level of errors affecting customers running Workers scripts, which also impacted Cloudflare Sites and Services. The incident lasted 23.5 hours before Cloudflare identified and implemented a fix. The service is now being monitored to ensure the resolution is effective.

Cloudflare Workers AI services experienced elevated error rates, specifically increased timeout (408) errors affecting multiple AI models. The incident impacted Cloudflare Sites and Services along with Workers AI functionality for 1.6 hours. Engineering teams implemented a fix and continued monitoring the results.

Cloudflare Workers and Pages builds, along with the Pages API, experienced service disruption for 52 minutes starting at 20:22 UTC, causing 5xx errors and build failures. The issue affected Cloudflare Sites and Services, Pages, and Workers Builds components. Cloudflare identified and implemented a fix, with builds stabilizing by 21:12 UTC and remaining under monitoring.

Cloudflare Workers experienced an issue where users were unable to view logs in the Durable Objects dashboard, affecting Workers Observability functionality. The problem was identified after investigation and a fix was implemented. The incident lasted 3.3 hours with minor impact to service operations.