Cloudflare Outage History

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.

Cloudflare experienced an issue affecting Workers invocations where customers encountered 1003/403 errors when making fetch() calls inside Workers. The problem impacted Cloudflare Sites and Services along with the Workers platform for 7.8 hours. A fix was identified and implemented, with most customers seeing resolution and a continued rollout for remaining affected users.

Cloudflare experienced network performance issues in Phoenix, AZ that caused errors and degraded performance for customers whose traffic was routed through that location. The incident affected Cloudflare Sites and Services in the Phoenix area for 22 minutes before being resolved.

Cloudflare experienced elevated error rates for R2 storage buckets in the APAC region, affecting customer access to their stored data and associated sites and services. The incident lasted 1.7 hours while Cloudflare investigated and resolved the connectivity issues. The problem impacted customers attempting to access their R2 buckets during the outage period.

Cloudflare experienced increased upload failures for Workers Assets over 5.2 hours, preventing customers from successfully uploading new assets. The serving of existing Workers Assets traffic remained unaffected throughout the incident. The issue was identified and resolved with a implemented fix, followed by monitoring to ensure stability.

Cloudflare experienced intermittent 500 errors affecting their Realtime APIs for 5.7 hours, while RealtimeKit meetings continued to function normally. The incident did not impact CDN file serving or edge security features, and Cloudflare investigated the API issues throughout the duration.