Cloudflare Outage History

Cloudflare experienced network performance issues affecting their Istanbul (IST) data center, impacting Cloudflare Sites and Services in the Europe region. The incident lasted 1.8 hours, during which users likely experienced degraded performance for websites and services routed through the Istanbul location. The issue was identified and a fix was implemented, with Cloudflare monitoring the results to ensure resolution.

Cloudflare experienced issues with their Turnstile challenge platform, causing users to encounter failed challenge solve attempts. The problem affected Cloudflare Sites and Services along with the Turnstile component for 58 minutes. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced network performance issues in Brazil lasting 26 minutes, causing increased disconnects and CNI tunnel degradation for customers. The incident affected Cloudflare Sites and Services along with the broader Network infrastructure. Cloudflare investigated and worked to analyze and mitigate the problem during the outage period.

Cloudflare WARP and Zero Trust users in Bulgaria experienced connectivity issues and degraded internet performance for 1.7 hours. The incident specifically affected the Sofia, Bulgaria datacenter and impacted users' ability to maintain stable connections through these services. Cloudflare identified the root cause and implemented a fix to resolve the connectivity problems.

Cloudflare experienced network performance issues in Miami that affected their sites, services, and network infrastructure. The incident impacted internet users in the Miami location with degraded connectivity and service performance. The issue was resolved within 4 minutes as Cloudflare actively worked to eliminate the performance problems.

Cloudflare experienced issues with health checks monitoring, alert notifications, and analytics that affected their sites and services for 7.9 hours. The problems impacted users' ability to monitor service health and receive proper notifications about their infrastructure status. The issue was identified and a fix was implemented to restore normal functionality.

Cloudflare experienced issues with their Dashboard and related APIs that caused incorrect error messages to display in the UI's bottom banner for 1.6 hours. The problem affected the Cloudflare Dashboard interface but did not impact CDN file serving or edge security features. The issue was identified and a fix was implemented to resolve the dashboard display problem.

A subset of Cloudflare Access customers experienced intermittent HTTP 500 errors on authentication requests beginning April 21, with impact limited to a small percentage of requests in specific geographies and service authentication requests seeing the highest error rates. The incident affected Cloudflare Sites and Services and Access components for 26.8 hours. Cloudflare engineering implemented a fix through a controlled rollout across impacted regions, with error rates decreasing as the deployment progressed.

Cloudflare Web Analytics experienced processing delays that affected the timely delivery of customer analytics data for 3.6 hours. The issue impacted Cloudflare Sites and Services and Analytics components, while DNS and Rate Limiting analytics remained unaffected. Cloudflare identified the root cause, implemented a fix, and monitored the resolution.

Cloudflare experienced issues with their Dashboard API that prevented R2 buckets from loading properly in the dashboard and caused increased API latency across their services. The incident affected Cloudflare Sites and Services, Dashboard, API, and R2 components for 1.2 hours. Cloudflare was actively investigating and working to mitigate the problem at the time of the last update.