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 49 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 14Today
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.
August 2026
Cloudflare Workers Runtime API 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
Workers runtime: Temporal global exposed with an incorrect clock
Since 2026-07-30, the Workers runtime has exposed a global Temporal object that was not intended to be available. Its clock is wrong: Temporal.Now reports 1970-01-01 rather than the current time. Date and Date.now() are unaffected and report the correct time.
This can affect Workers that install a Temporal polyfill only when no native Temporal is detected. On those Workers, the polyfill stopped being installed and time-depende...
investigating
Cloudflare is aware of an issue with the latest Workers Runtime API release that exposes native Temporal with clock stuck at epoch 0. Updates to follow.
Cloudflare Workers build failures
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
Wrokers builds are no longer failing, users may experience delays with builds.
identified
The issue has been identified and a fix is being implemented.
investigating
Cloudflare is aware of and investigating an issue with Cloudflare Workers build failures which potentially impacts multiple customers. Further detail will be provided as more information becomes available.
Cloudflare Dedicated Egress in London
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, reports that customers who have dedicated IPv4 egress IPs homed in London may be unable to reach out to the public Internet.
July 2026
Increased HTTP Errors in London
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are currently monitoring the results.
identified
The cause of this issue has been identified and a fix is being implemented.
investigating
Cloudflare is investigating an increased level of HTTP errors affecting a subset of customers. We are working to analyze and mitigate this problem. More updates to follow shortly.
Network Performance Issues in Hamburg, Germany
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 investigating issues with network performance in
Hamburg, Germany (HAM). Customers routing through this location may
experience request errors or failures. We have identified the problem and are working on a fix.
Cloudflare API Availability Reduced Availability
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Cloudflare is aware that this is also impacting on Pages and Worker builds. We are continuing to investigate.
investigating
We are continuing to investigate this issue.
investigating
Cloudflare is investigating reduced availability with Cloudflare Dashboard and related APIs. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using the Dashboard / Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.
Increased HTTP 5xx Errors for us-east-1-aws
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 investigating an increased level of intermittent HTTP 5xx errors for customers using AWS region us-east-1-aws.
We are working to analyse and mitigate this problem. More updates to follow shortly.
Page Shield Email Notification Issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an issue where Page Shield email notifications are not containing the correct data for some customers. Our engineering team is currently working on a fix to restore accurate alert delivery. We will provide updates as soon as more information is available.
Possible Network Congestion in North America region
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
Cloudflare identified that the Network degradation was due to maintenance conducted by fiber providers. The congestion has been alleviated by rerouting traffic. We are currently monitoring the situation and will follow up with more updates shortly.
investigating
Cloudflare is observing possible network congestion in the North America region. Customers may see elevated latency and connectivity issues.
We are working to mitigate impact to Internet users in this region.
Sensitive Data Detection Configuration 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
The issue has been identified and a fix is being implemented.
investigating
Cloudflare is investigating an issue with the Sensitive Data Detection feature in the Cloudflare Dashboard. Customers may be unable to enable Sensitive Data Detection via the Security settings toggle. Other dashboard features and security services remain unaffected.
We are working to identify and mitigate this problem.
More updates to follow shortly.
