Cloudflare Outage History

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. The issue was identified and resolved with a fix implementation after 2.1 hours.

Cloudflare experienced elevated error rates for R2 storage buckets in Western North America, affecting multiple services including Cloudflare Sites, Cache Reserve, Images, R2, and Stream. The incident lasted 4.2 hours before a fix was implemented and monitoring confirmed resolution.

Cloudflare One clients experienced connectivity issues when using the MASQUE protocol, causing intermittent connectivity and degraded service for Zero Trust users. Users could restore stable service by temporarily switching to the Wireguard protocol as a workaround. The issue was identified and fixed after 4.8 hours, with Cloudflare monitoring the resolution.

Cloudflare experienced issues with Page Rules where HTTP redirects failed to trigger as expected on worker subrequests, affecting Cloudflare Sites and Services and Rules components. The incident lasted 29.7 hours before the issue was identified and a fix was implemented.

Cloudflare Web Analytics experienced processing delays that affected the timely delivery of customer analytics data. The incident impacted Cloudflare Sites and Services, Billing, and SSL Certificate Provisioning, while DNS and Rate Limiting analytics remained unaffected. The issue was resolved after 6 minutes.

Cloudflare experienced delayed analytics reporting for Durable Objects and D1 storage totals in their dashboard. The issue affected Cloudflare Sites and Services and Durable Objects components for 12.5 hours. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced issues with its Load Balancing Health Monitoring services for 4.3 hours, causing delays in responding to endpoint health changes. The incident affected Cloudflare Sites and Services along with Load Balancing and Monitoring components. A fix was implemented and the service was restored to normal operation.

Cloudflare's Data Loss Prevention (DLP) API experienced high latency that caused some DLP functionality to become unavailable for 11 minutes. The incident also affected Cloudflare Sites and Services. The service disruption was resolved after the latency issues were addressed.

Cloudflare Access experienced delayed processing of audit logs from April 28, 17:00 UTC through April 29, 19:00 UTC, affecting authentication log visibility while Access services remained fully operational. A fix was implemented on April 29 to prevent new log delays, and engineering ran a backlog processing operation to ingest all missing logs. No authentication data was lost during the incident, and log collection returned to normal after the fix.

Cloudflare experienced a major incident where duplicated values appeared in the X-Forwarded-For header, causing unexpected behavior for origin servers that depend on this header for client IP identification. The issue affected Cloudflare Sites and Services, CDN/Cache, and CDN Cache Purge components for 15.1 hours. After identifying the root cause, Cloudflare implemented a fix that was rolled out over several hours to resolve the header duplication problem.