Cloudflare Outage History

Cloudflare Access experienced an issue where customers were unable to upload custom block pages. The incident affected Cloudflare Sites and Services and Access components for 47 minutes. The service disruption was classified as minor and has been resolved.

Cloudflare experienced network performance issues in Frankfurt, Germany, causing some users to encounter increased latency or timeouts for 23 minutes. The issue was identified and a fix was implemented, with monitoring continuing to ensure resolution.

Cloudflare One Client users in the Texas region experienced performance degradation and increased latency for 49 minutes. The incident affected Cloudflare Sites and Services along with Zero Trust components. Cloudflare actively troubleshot and resolved the connectivity issues with their Texas datacenter region.

Cloudflare experienced a 14-minute incident where users were unable to access the settings page for Cloudflare Pages Projects, particularly affecting projects without connected repositories. The issue impacted Cloudflare Sites and Services and Pages components. Cloudflare investigated and resolved the access problem.

Cloudflare experienced elevated errors and latency for R2 storage services in the Western North American region, affecting customers using R2 and Cloudflare Sites and Services. The incident lasted 1.3 hours, during which users experienced increased response times and higher error rates when accessing R2 storage. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced issues with their Images service when transforming images from R2 buckets, causing errors for customers serving image transformations on free zones. The incident affected Cloudflare Sites and Services and the Images component for 31 minutes. A fix was implemented and the service was restored to normal operation.

Cloudflare's Analytics Engine API experienced increased 500 errors for 3 hours, preventing users from successfully querying analytics data. The issue also affected Cloudflare Sites and Services and API components. Cloudflare identified the root cause and implemented a fix, then monitored the results to ensure resolution.