Cloudflare Outage History

Cloudflare's Log Explorer experienced performance issues for 1.8 hours, causing slower than usual query responses for some customers. The issue was identified and a fix was implemented, with monitoring confirming the resolution.

Cloudflare Access experienced availability issues in limited geographic locations for 14.7 hours, causing customers to encounter errors when using the service. The incident affected Cloudflare Sites and Services along with the Access component. Cloudflare identified the root cause and implemented a fix, then monitored the results to ensure resolution.

Cloudflare experienced degraded network performance issues affecting users in the Dallas, Texas area for 30 minutes. The incident impacted Cloudflare Sites and Services in the North America region, specifically at the Dallas (DFW) data center. A fix was identified and implemented, with monitoring confirming the resolution.

Cloudflare experienced increased HTTP 5xx errors affecting sites and services in Sydney, NSW, Australia for 3.6 hours. The incident impacted Cloudflare's network infrastructure and services in the Sydney region. A fix was implemented and the service was restored to normal operation with monitoring in place.

Cloudflare experienced an issue where requests processed by Workers were not correctly enforcing rulesets rate limiting counts, affecting Cloudflare Sites and Services, Workers, and Rules components. The incident lasted 12.9 hours and was resolved with a fix implementation, followed by monitoring to ensure the rate limiting accuracy was restored.

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 connectivity issues with WARP and Zero Trust services, primarily affecting users in the Dallas, TX region who encountered degraded internet performance and connection problems. The incident lasted approximately 69 hours before being resolved. Cloudflare monitored the situation after impact ended at 06:45 UTC on April 20th, 2026.

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.