Daily provider-status observations and published incident history for Cloudflare.
Component incident
Cloudflare has an active component incident; no global outage is indicated. Verified .
Official provider source.
Looking for an update now? Check the current status, or follow Cloudflare for future changes.
0%of 50 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
0%
30
30
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 15Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Cloudflare continues to mitigate intermittent connectivity degradation for a small subset of customers caused by significant degradation of capacity in the region.
identified
The issue has been identified and a fix is being implemented.
investigating
Since September 21, 2026 at 02:20 UTC, multiple subsea cable outages have caused congestion between Tokyo and Singapore datacenters. We have rerouted traffic to reduce impact and are working with third-party vendors to restore capacity.
Elevated Errors with any / all in http_response_cache_settings
We have identified an issue causing unexpected errors when creating or updating configurations using any or all expressions in the http_response_cache_settings.
This issue strictly affects API operations; existing active configurations and live traffic are not impacted. A fix is currently being deployed, and we will provide an update once the rollout is complete.
A fix has been implemented and we are monitoring the results.
identified
A known issue affected authentication for a small percentage of requests to the API and R2.
The issue was identified on Sep 22 at 13:30 UTC, and major impact was mitigated at 19:00 UTC.
Our team is actively working to resolve the residual impact.
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
Cloudflare is aware of, and investigating an issue with Durable Objects which potentially impacts a subset of customers. Durable Objects are experiencing an elevated level of errors. We are currently investigating this issue.
Elevated number of R2 503 errors in Australian Eastern Coast region
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
Cloudflare is aware of, and investigating, an issue which impacts DNS over HTTPS requests to 1.1.1.1 for Families (1.1.1.2 and 1.1.1.3)
Authoritative DNS provided by Cloudflare is unaffected.
Further detail will be provided as more information becomes available.
Cloudflare One Clients are incorrectly challenged on some sites
We are currently investigating an issue where Bot Management configuration updates are not propagating to the edge. Our engineering team is aware of the issue and is actively working on a resolution. The running Bot Configuration at the Edge is not impacted. We will provide further updates as soon as we have more information.
A fix has been implemented and we are monitoring the results.
identified
Cloudflare is monitoring the restoration of Workers and Durable Objects analytics visibility for all Fedramp High customers. While the underlying data remains intact, affected datasets were not being correctly returned by our analytics dashboard and GraphQL API since June 11th. Services are currently recovering as we propagate the fix.
Legacy Incident Archive
385 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
April 2026
R2 customers may see an increase of HTTP 500s in KIX
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
WARP connectivity
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Impact ended at 06:45 UTC, and we are monitoring the situation.
investigating
We are continuing to investigate this issue.
investigating
Cloudflare is investigating issues with Cloudflare WARP and Cloudflare Zero Trust. Cloudflare WARP and Zero Trust users may experience connectivity issues or a degraded Internet experience.
HTTP Log Analytics Issue
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
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.
identified
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
identified
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
investigating
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.
Cloudflare Workers AI Issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
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.
DNS resolution intermittently failing for .co domains
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
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.
Increase in API errors and latency
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
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.
Increased errors in Seattle or Argo Smart Routing
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers connecting in Seattle or who have Argo Smart Routing enabled that is routing them through Seattle may be seeing increased errors.
Elevated 502 errors returned from some locations
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Elevated 502 errors returned from some locations
co ccTLD DNS errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
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.
CF1 Client DEX - Device analytics overtime gaps
minorSource not attested
Last archived state: resolved
View archived record details
identified
The DEX analytics overtime data for CF1 client devices may show missing data.
