Cloudflare Outage History

Cloudflare experienced dashboard login issues where authentication attempts were silently failing, particularly affecting SSO-based logins. The incident impacted the Cloudflare Dashboard and Sites and Services components for 1.4 hours. The issue was under investigation with no resolution details provided in the available updates.

Cloudflare experienced issues with their Dashboard and API services for 27 minutes, causing request failures and error displays for customers trying to access these management interfaces. The incident did not impact CDN file serving or edge security features, so end-user website performance remained unaffected. A fix was implemented and the service was restored to normal operation.

Cloudflare R2 customers experienced incomplete assets and broken connections when receiving 206 (partial content) responses, affecting Cloudflare Sites and Services and R2 storage. The issue was identified after approximately 2 hours of investigation, and a fix was implemented and rolled out. The incident lasted 11.3 hours total before resolution.

Cloudflare Analytics experienced degraded performance in the US region for 7.5 hours, affecting users' ability to access certain datasets through the GraphQL API. The issue caused delays in data availability and impacted Cloudflare Sites and Services along with Analytics components. The problem was identified and a fix was implemented to resolve the service disruption.

Cloudflare experienced increased HTTP 520 errors specifically affecting HEAD requests for 4.2 hours. The issue was identified and a fix was implemented to resolve the problem.

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.