Cloudflare Outage History

Cloudflare experienced a 56-minute incident where some visitors were unable to pass security challenges, preventing access to protected websites. Users reported being unable to access various sites during this period. The issue was resolved with a implemented fix and Cloudflare monitored the results to ensure stability.

Cloudflare's R2 storage service experienced increased HTTP 500 errors at the KIX (Osaka, Japan) location for 15 minutes. The incident affected R2 customers accessing services through the Osaka data center. Cloudflare investigated and worked to mitigate the issue.

Cloudflare experienced an HTTP analytics issue where some US customers observed inaccurate metrics in the dashboard, with 0.05% of customers seeing analytics delayed by up to 6 hours. The issue was later identified to primarily affect a small number of customers with custom metadata boundaries, with no data loss occurring. A fix was implemented after 54.8 hours and the team monitored the results, while all traffic and security services remained fully operational throughout the incident.

Cloudflare experienced a 4-hour issue where customers encountered errors when making inference requests to the @cf/baai/bge-m3 model through Workers AI. The problem affected Cloudflare Sites and Services along with the Workers AI platform. A fix was implemented and the service was restored to normal operation with monitoring in place.

Cloudflare experienced intermittent DNS resolution failures for .co domains, affecting Cloudflare Sites and Services and Recursive DNS for 4.2 hours. The issue required coordination with the .co ccTLD operator to resolve. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced increased API errors and latency affecting their Sites and Services and API components for 15 minutes. The issue impacted multiple APIs across their platform, causing degraded performance for users attempting to access Cloudflare services. A fix was implemented and the service was restored to normal operation with ongoing monitoring.

Cloudflare experienced increased errors affecting customers connecting through their Seattle data center and those using Argo Smart Routing that routed traffic through Seattle. The incident impacted the North America Seattle, WA location and lasted approximately 1.9 hours. The service was classified as a minor incident with customers potentially experiencing elevated error rates during this period.

Cloudflare experienced elevated 502 errors from some locations, affecting their Sites and Services, CDN/Cache, R2, and Workers KV components. The incident lasted 29 minutes before a fix was implemented and monitoring began.

Cloudflare experienced DNS errors affecting sites with .co domain extensions, causing intermittent access issues for these websites and recursive DNS services. The incident lasted 4.8 hours before a fix was implemented and deployed. Cloudflare identified the root cause and resolved the issue through monitoring and mitigation efforts.

Cloudflare experienced an issue where Digital Experience Monitoring (DEX) analytics showed missing overtime data for CF1 client devices, affecting Cloudflare Sites and Services, Zero Trust, and DEX components. The incident lasted 11.8 hours and was classified as minor severity. The issue was identified and tracked, impacting device analytics visibility for affected users.