Cloudflare had 208 outages in the last 2 years totaling 134h 32m of downtime — averaging 8.5 incidents per month.
There were 208 Cloudflare outages since April 3, 2026 totaling 134h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.
For some users, sampled Logs and Suspicious Activity were not available in the Security analytics dashboard between 16:48:31 UTC on 21st April 2026 and 09:04 UTC on 22nd April 2026. No data loss occurred, and all graphs and visualizations were restored once the issue was resolved. The GraphQL API and Logpush remained fully functional throughout this period.
Cloudflare is experiencing delays in activating customer sites. This does not impact existing active sites already in production. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is observing issues with Cloudflare Gateway HTTP Logs service that may delay log ingestion.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare has identified an issue with customers creating/updating Page Rules with the Host Header Override setting. Other settings are not impacted. We are working to mitigate the problem, more updates to follow shortly.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating reports of degraded Realtime service in the Mumbai region.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare has identified and mitigated issues with network performance in Seattle. We have implemented a fix and are currently monitoring
This incident has been resolved.
Cloudflare is aware of and investigating an issue with Cloudflare Pages builds which potentially impacts multiple customers. Users may not be able to push changes to their repos, or pushed changes may fail to or be delayed in propagating to Cloudflare Pages. These changes may not be deployed, or may be delayed. This issue only impacts new changes, existing sites and traffic to those sites are not affected.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is investigating issues with Log Explorer. Some customers may be seeing slower queries in Log Explorer than usual. More updates to follow shortly.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is investigating issues with Cloudflare Access in a limited number of geographic locations. Customers using Cloudflare Access can experience a small number of errors. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is investigating issues with Network Performance in Dallas, Texas. We are working to analyze and mitigate this problem. More updates to follow shortly.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is investigating an increased level of HTTP 5xx errors in Sydney, NSW, Australia - (SYD). We are working to analyse and mitigate this problem. More updates to follow shortly.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Cloudflare is aware of, and investigating an issue where some requests processed by workers may not be correctly enforcing rulesets rate limiting counts.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is aware that some visitors are currently unable to pass challenges. We are investigating the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is investigating reports of HTTP 500 responses for R2 services in the KIX (Osaka) location. We are working to mitigate this, more updates to follow shortly.
This incident has been resolved.
Some customers in US may observe inaccurate HTTP analytics metrics being shown in the Cloudflare Dashboard. All Cloudflare traffic and security services remain operational and unimpacted. We are working to mitigate this problem. More updates to follow shortly.
We identified that a small percentage of customers may see http analytics delayed by up to about 6 hours before being shown in the Cloudflare Dashboard. All Cloudflare traffic and security services remain operational and unimpacted. Remediation is in progress
We identified that 0.05% of customers may see http analytics delayed by up to about 6 hours before being shown in the Cloudflare Dashboard. All Cloudflare traffic and security services remain operational and unimpacted. Remediation is in progress
We are continuing to work on a fix for this issue. Current impact is restricted to a small number of customers with custom metadata boundaries. There has not been any data loss in Analytics.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare has identified an issue whereby customers might experience errors from inference requests to @cf/baai/bge-m3 model using Workers AI. We are working to mitigate this problem. More updates to follow shortly.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is aware of DNS resolution intermittently failing for domains using .co ccTLD. We are trying to reach the ccTLD operator to resolve this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is aware of an increase of errors and latency across a number of APIs. We are working to analyse and mitigate this problem. More updates to follow shortly.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Customers connecting in Seattle or who have Argo Smart Routing enabled that is routing them through Seattle may be seeing increased errors.
This incident has been resolved.
Elevated 502 errors returned from some locations
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is aware of and investigating problems with Cloudflare sites with .co ccTLDs intermittently returning DNS errors. We are working to mitigate this problem. More updates to follow shortly.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The DEX analytics overtime data for CF1 client devices may show missing data.
This incident has been resolved.
Cloudflare is aware of and has mitigated an issue which impacted Workers script uploads between 14:51 UTC to 15:00 UTC on 16th April 2026 This did not impact Workers traffic.