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
Incident History
September 2026
Purchased domains from registrar not appearing in Cloudflare Dashboard
We are investigating reports of delays in the provisioning of newly purchased domains. Our engineering team is currently working to resolve these delays affecting domain registration.
Customers may experience intermittent connectivity issues when accessing services through our Canberra (CBR01) data center. Our team is actively working to restore normal service.
Elevated number of R2 503 errors in Eastern North America region
Cloudflare is aware of, and implementing a fix for individual device posture checks not showing on the Devices Page. Device posture checks in the meantime can be inspected through the Logs -> Posture Logs.
This is purely a dashboard visibility issue— firewall policies are not impacted.
A fix has been implemented and we are monitoring the results.
investigating
Cloudflare cache purging called via the Dashboard or API is returning errors, with the message "unable to purge. internal error". We are working to resolve this issue as soon as possible. More updates to follow.
Elevated number of R2 503 errors in Western North America 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 increased number of errors for Durable Objects in Western North America.
The suspected cause is a reduction in routing capacity due to a fibre cut. We are working to mitigate this issue, and update will follow.
The issue has been identified and a fix is being implemented.
investigating
Cloudflare is investigating an increased level of errors for customers running Workers scripts in Narita.
We are working to analyse and mitigate this problem. More updates to follow shortly.
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.
March 2026
Network Error Logging 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
As the fix is deployed, customers may notice an increase in NEL reports as data that was previously not forwarded is correctly reported.
investigating
Cloudflare has identified an issue causing intermittent data gaps within Network Error Logging (NEL).
Our engineering team has identified the root cause and is currently implementing a fix. There is no impact to customer traffic.
Issues passing Challenge Pages and Turnstile
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Visitors encountering Turnstile or Cloudflare Challenge Pages are encountering intermittent issues solving the challenge and may have to retry.
Network Performance Issues in Osaka, Japan datacenter (KIX)
minorSource not attested
Last archived state: resolved
View archived record details
identified
Cloudflare is investigating issues with Network Performance in Osaka, Japan datacenter (KIX).
We are working to analyze and mitigate this problem. More updates to follow shortly.
Cloudflare API service 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
The Cloudflare Workers and GraphQL API is experiencing increased errors and changes to Cron Triggers may be delayed. Already deployed Workers and existing Cron Triggers are unaffected.
investigating
We are continuing to investigate this issue.
investigating
The Cloudflare Workers API is experiencing increased errors and changes to Cron Triggers may be delayed. Already deployed Workers and existing Cron Triggers are unaffected.
Schema Validation Block Reason Not Displayed on Dashboard
minorSource not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
investigating
Customers may notice that when a request is blocked by schema validation, the associated reason or description is not being displayed within the dashboard.
Increase in AI Gateway errors
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, and investigating an issue which potentially impacts multiple customers. Customers may be seeing an increase of errors using AI Gateway.
We are working to identify the root cause and will provide updates as they become available.
Request Trace is failing for some requests
minorSource not attested
Last archived state: resolved
View archived record details
investigating
The request trace feature is failing for some cacheable assets. Failing requests are returning 400 Bad Request.
Increased HTTP 530 Errors in Atlanta (ATL)
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 investigating an increased rate of HTTP 530 errors specifically affecting ".cloud" and ".tech" traffic routed through our Atlanta (ATL) data center.
We are working to identify the root cause and will provide updates as they become available
Workers API increased latency
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Workers API latency has returned to normal levels. Team is continuing to monitor.
identified
The issue has been identified and a fix is being implemented.
investigating
Cloudflare is investigating an issue causing increased latency for the Workers API
Network Performance Issues in Jakarta
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are continuing to work on a fix for this issue.
identified
We are continuing for work on a fix for this issue
identified
We are continuing for work on a fix for this issue
identified
We are continuing for work on a fix for this issue
identified
The issue has been identified and a fix is being implemented.
investigating
Cloudflare is investigating issues with Network Performance for customers in the Jakarta area
We are working to analyze and mitigate this problem. More updates to follow shortly.
