Cloudflare Outage History

Cloudflare experienced increased errors affecting customers attempting to update Queues via Terraform. The issue was classified as minor and lasted approximately 3.2 hours. Cloudflare identified the problem and worked on implementing a fix.

Cloudflare experienced an issue affecting Pages deployments of Pages Functions with R2 bindings, causing deployment failures for customers. The problem was identified and a fix was implemented within approximately 1.1 hours. Cloudflare continued monitoring to ensure no further issues occurred.

Cloudflare experienced WARP connectivity issues affecting Windows users who had upgraded to version 2026.3.846.0, impacting Cloudflare Sites and Services along with Access functionality. The incident lasted 56 minutes before a fix was implemented and monitoring began to ensure stability.

Cloudflare experienced elevated latency when uploading Workers Static Assets for 1.2 hours. The issue only affected new asset uploads, while existing Workers scripts continued to function normally. Cloudflare investigated and resolved the latency problem.

Cloudflare experienced an issue with Digital Experience Monitoring (DEX) that caused delays in DEX data for customers over a 1.5 hour period. The incident affected Cloudflare Sites and Services along with the DEX component specifically. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced issues with creating Managed Rules exceptions through their Dashboard, causing requests to fail and displaying errors for customers attempting to make these changes. The incident lasted 1.6 hours and only affected Dashboard functionality, while the API, CDN file serving, and other security features continued operating normally. A fix was implemented and deployed under monitoring to resolve the Dashboard issues.

Cloudflare experienced delays with single-file cache purging (purge by URL) functionality accessed through the Dashboard and API, affecting CDN services in Asia, particularly Tokyo, Japan. Users could work around the issue by using the "Purge Everything" feature, though this could increase traffic to origin servers. The incident was resolved after 19 minutes.

Cloudflare experienced a 1.4-hour outage affecting their AI Search service, where customers encountered 7001 and internal error messages when attempting to use the feature. The company investigated the issue and implemented a fix, then monitored the results to ensure service restoration.

Cloudflare experienced increased error rates for Workers scripts running in their Chicago data center, affecting customers using Cloudflare Sites and Services in that region. The incident lasted 21 minutes while Cloudflare investigated and worked to mitigate the problem. The service was classified as a minor incident impacting the Chicago, IL (ORD) location in North America.

Cloudflare experienced elevated latency affecting a small percentage of cache assets in Buenos Aires, Argentina. The issue impacted CDN/Cache services and Cloudflare Sites and Services in the Latin America & Caribbean region for 1.8 hours. Cloudflare investigated and resolved the latency problem affecting their Buenos Aires data center.