Cloudflare Outage History

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Reporting and analytics for the HttpRequestsAdaptiveGroups node is delayed. This will result in failures on dashboard for analytics. We are working to mitigate this problem. More updates to follow shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Cloudflare is investigating an increase in 5xx errors in Fuzhou and Foshan China. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Cloudflare is aware of, and investigating, an issue which potentially impacts multiple users in Tel Aviv that use 1.1.1.1 public resolver. Further detail will be provided as more information becomes available.

Cloudflare became aware of a brief period of reduced availability of the Realtimekit API, between the times 11:07 UTC and 11:13 UTC. This issue has recovered, and no further impact expected.

Availability has now been fully restored for all impacted R2 buckets, including the remaining objects uploaded through multipart uploads in ENAM.

Availability has been restored for nearly all impacted R2 buckets. A small number of objects uploaded through multipart uploads in ENAM between 14:52 and 17:02 UTC on August 7 remain unavailable. We are continuing to restore access and expect to be able to provide another update soon.

We are continuing to restore availability for impacted R2 buckets in ENAM. Recovery is progressing well, and we will provide status updates as they becomes available

We are continuing to work on a fix for this issue.

We have identified the cause and mitigated further impact. Writes to a small set of buckets in ENAM were impacted between 14:52-17:02 UTC. We are continuing to work to restore normal availability for these buckets.

Cloudflare is aware, and investigating an issue affecting availability in ENAM for a small number of R2 buckets.

This incident has been resolved.

We have lost dark fiber in the Istanbul region, we are working to follow up with our vendors to restore connectivity. More updates to follow shortly.

Cloudflare’s investigation has determined that Cloudflare services are operating normally. The observed connectivity issue is outside Cloudflare’s network, and we have contacted the relevant external network provider.

Cloudflare has identified a connectivity issue affecting access to some websites from certain networks in Egypt. We are working with external parties to restore network availability. More updates will follow.

Cloudflare is aware of, and investigating a connectivity issue which potentially impacts end-user connectivity in Egypt. More updates to follow shortly.

This incident has been resolved.

We have identified the root cause and reverted the impacted change. However, for the fix to apply to existing Workers utilizing Gradual Deployments, affected Workers must have their deployment traffic percentages adjusted or redeployed. As a workaround, if you are currently impacted, you can immediately resolve the issue for your service by modifying the traffic weights of your Gradual Deployment (for example, shifting your active deployment weights from 50%/50% to 40%/60%, or redeploying your Worker). We are actively working on an automated fix for all remaining affected customers and will provide another update once resolved.

Cloudflare is aware, and investigating reports where a subset of customers are not seeing logs in the Workers Observability dashboard after deploying a new version of a Worker. Affected Workers continue to run and serve traffic normally. Metrics remain available.

This incident has been resolved.

Cloudflare is investigating issues with network performance in Chicago. We are working to analyse and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Cloudflare is investigating issues with configuration changes for Cloudflare Web Analytics and rum beacon not taking effect or showing errors. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

Cloudflare is aware of and investigating an issue whereby customers using Gateway email lists in their DNS policies are not being enforced. No other impact is implied. More updates to follow shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Cloudflare is investigating an issue where uploads for Pages and Workers Assets have reduced availability. We are working to analyse and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue. This may impact customers using China Network outside of China.

Cloudflare is investigating an increased Managed Challenge errors for China Network. We are working to analyse and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Cloudflare is aware of, and investigating an issue with elevated R2 error rates and latency for R2 buckets located in Oceania

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Cloudflare is investigating elevated 502 errors around Singapore, Jakarta and Bangkok. Further detail will be provided as more information becomes available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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-dependent logic began computing against 1970 — for example, tokens minted with an issue time of 0 and an expiry in 1970, incorrect TTLs, or incorrect date arithmetic. No error is raised when this happens.

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.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Cloudflare is aware that deploying Workers that the nodejs_compat compatibility flag and a compatibility date on or after 2026-08-04 is being disallowed. This is impacting Workers and Workers for Platforms. We are working on relaxing this assertion. To avoid this error, remove the nodejs_compat compatibility flag from your Worker.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Wrokers builds are no longer failing, users may experience delays with builds.

The issue has been identified and a fix is being implemented.

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.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

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.

We have identified and mitigated an issue affecting RealtimeKit socket connections, which caused slowness and meeting join failures for some users. Customers were impacted from 13:10 UTC to 14:15 UTC All services have been restored, and we are continuing to monitor system performance to ensure stability.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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.

This incident is now resolved.

A fix has been implemented and we are currently monitoring the results.

The cause of this issue has been identified and a fix is being implemented.

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.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

Cloudflare is aware that this is also impacting on Pages and Worker builds. We are continuing to investigate.

We are continuing to investigate this issue.

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.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

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.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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.

This incident has been resolved.

We are continuing to monitor for any further issues.

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.

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.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

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.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Cloudflare is observing possible network congestion between Singapore and Tokyo. We are working to mitigate impact to Internet users in this region.

Cloudflare had identified a network performance issue in Singapore from 11:33 UTC to 11:57 UTC.

This incident has been resolved.

We are continuing to monitor for any further issues.

A subset of customers using Cloudflare Tunnel may have experienced tunnel connectivity issues, including being unable to access private resources and services routed through Cloudflare Tunnel. Customers who are still experiencing issues should restart their cloudflared connectors to restore normal tunnel connectivity. This issue does not affect any other Cloudflare services.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

Investigating Cloudflare Tunnel availability issues. Multiple customers reporting tunnels degraded or fully down, including inability to access private resources behind Tunnel. Tunnel engineering team being engaged. No root cause identified yet.

Between 14:29 UTC and 14:55 UTC on July 28, 2026, Cloudflare experienced issues with Durable Objects in the WNAM region. The issue has been resolved now.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Cloudflare is aware of Network Performance issues in Istanbul, Türkiye. We are working to analyse and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Cloudflare is aware of, and investigating, reports of an error when viewing, editing or creating security rules in the dashboard. Customers may see an error 410 from the dashboard. This has no impact on the operation of those rules.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently experiencing an issue with the Snippets API, which is returning errors for direct API calls. As a result, users are unable to create, modify, delete, or retrieve snippet code and rules. Existing snippets continue to be served correctly from the edge. Our engineering team is actively investigating the issue, and we will provide updates as soon as possible.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

Customers are unable to review their CSP Security rules in the dashboard. Although the policies are unchanged and working.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Cloudflare is investigating a delay in our ability to send emails. This includes password reset, mFA token emails. We are working to resolve the issue. More updates to follow shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Cloudflare is investigating issues with rate limit errors in the analytics dashboards

This incident has been resolved.

An infrastructure partner has implemented a fix and we are monitoring the results

Cloudflare is investigating partner network instability over shared interconnections in Western North America

Cloudflare is investigating issues with Network Performance in Western North America We are working to analyze and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

We are continuing to investigate this issue.

Cloudflare is aware of and investigating Workers AI experiencing degraded availability in some models. Impacted models: - @cf/moonshotai/kimi-k2.6 - @cf/moonshotai/kimi-k2.7-code

We are currently investigating this issue.