Cloudflare outage history

We are currently investigating an issue where customers that use Spamhaus for additional filtering of email downstream from the Cloudflare Email Security service are rejecting emails from IPs in the 134.195.26.0/23 block. This IP block should be allowed for all customer downstream systems to avoid treating the Email Security service as an originator of mail. We recommend all Cloudflare Email Security customers disable Spamhaus filtering in downstream systems.

We are continuing to investigate this issue.

We are continuing to investigate this issue. Customers using O365 will be impacted only if they have not completed the required setup. Please check your setup and ensure the connector includes all egress IPs: https://developers.cloudflare.com/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/#2-configure-enhanced-filtering

All IPs previously listed by Spamhaus are now clean. Monitoring the propagation of that change to downstream systems.

This incident is now resolved.

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.

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

This incident has been resolved.

Cloudflare is aware of, and has resolved, an issue within our London datacenter where some traffic may have seen reduced connectivity for a short time. This potential impact window for this was 12:58 UTC to 13:25 UTC. There is no ongoing impact.

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.

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 observed an increased level of HTTP 5xx errors in Singapore from 03:30 AM - 04:00 AM UTC. The issue is currently resolved.

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.

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 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.

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

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’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.

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.

This incident has been resolved.

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

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.

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

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

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.

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

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.

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.

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.

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.

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

This incident has been resolved.

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.

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

We are currently investigating this issue.

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

This incident has been resolved.

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.

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 Managed Challenge errors for China Network. We are working to analyse and mitigate this problem. More updates to follow shortly.

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

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, and investigating an issue with elevated R2 error rates and latency for R2 buckets located in Oceania

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

This incident has been resolved.

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

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 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.

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

This incident has been resolved.

Cloudflare is investigating issues with network performance in Bangalore, India (BLR). Customers routing through this location may experience request errors or failures. We are working to analyze 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.