Cloudflare Outage History

Cloudflare Access experienced delays in creating, updating, and removing Access applications due to a configuration issue. Existing Access applications continued to function normally and were not affected during the incident. The issue was identified and resolved with a fix implementation, lasting approximately 1.6 hours.

Cloudflare experienced network performance issues in Amsterdam, Netherlands, affecting sites and services in the region for 47 minutes. The incident impacted the Amsterdam (AMS) network infrastructure and related Cloudflare services. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced elevated error rates and increased latency for R2 requests originating from India, affecting multiple services including R2, Cache Reserve, Images, Stream, and general Cloudflare Sites and Services. The incident was classified as minor and lasted 54 minutes. The issue was under investigation with Cloudflare working to resolve the connectivity problems impacting Indian users' access to R2 storage services.

Cloudflare experienced increased error rates affecting customers running Workers scripts, which also impacted Cloudflare Sites and Services. The incident lasted 23.6 hours before Cloudflare identified and implemented a fix. The company is currently monitoring the results to ensure the resolution is effective.

Cloudflare experienced analytics availability issues lasting 3.3 hours, causing customers to encounter elevated API error rates, increased latency when reading data, and delays in analytics data updates. The incident affected Cloudflare Sites and Services along with the Analytics component. A fix was implemented and the service was restored to normal operation with monitoring in place.

Cloudflare experienced intermittent API failures affecting Zero Trust Gateway for 4.5 hours, preventing customers from viewing or editing policies in the Zero Trust dashboard. Existing policies continued to function normally throughout the incident. The issue was identified and a fix was implemented to resolve the API failures.

Cloudflare experienced elevated error rates affecting Workers AI services, with users encountering increased timeout (408) errors across multiple AI models. The incident also impacted Cloudflare Sites and Services during the 1.7-hour outage. Engineering teams implemented a fix and continued monitoring to ensure service stability was restored.

Cloudflare experienced delays in SSL certificate provisioning, with new certificates taking up to 45 minutes to provision instead of the normal timeframe. Existing SSL certificates in production continued to operate normally and were not affected. The issue was identified and fixed within 26 minutes, with monitoring in place to ensure resolution.

Cloudflare experienced intermittent issues with their Dashboard and APIs for 1.9 hours, causing request failures and error displays for customers using these services. The CDN and edge security features remained unaffected throughout the incident. Cloudflare identified the root cause and implemented a fix, then monitored the results to ensure resolution.

Cloudflare experienced network performance issues affecting users in Russia for 30 minutes. The service degradation impacted connectivity and response times for Russian users accessing Cloudflare-protected websites and services. The incident was investigated and resolved within the 30-minute timeframe.