Cloudflare reports multiple service issues

Workers Cron Triggers have stabilized

We are continuing to monitor for any further issues.

This incident has been resolved.

Cloudflare is investigating issues with Workers Cron Triggers. A subset of customers may not being their cron get invoked. We are working to mitigate this problem. More updates to follow shortly.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

Our engineering teams are continuing to remediate the issue. No customer impact is being seen at this time.

We are continuing to monitor for any further issues.

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

Cloudflare has identified an issue with network performance affecting our Ashburn (IAD) and Newark (EWR) facilities. Customers may observed elevated latency and/or errors for traffic handled by these facilities until the issue is resolved. We are working on a fix for this issue and will have more updates shortly.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

We are working to mitigate impact to Internet users in this region. Cloudflare has identified the issue and is implementing a fix.

Cloudflare is aware of and is investigating reports that pages.dev subdomains are not available in Norway. Pages sites that use Custom Domains are not impacted. We will update this as more information become available.

Cloudflare resolved an incident where we observed network performance issues in our Kuala Lumpur (KUL) facility. Customers may have observed elevated error rates and/or increased latency today, 2026-10-15, between approximately 16:10 and 16:15 UTC.

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

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

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

Cloudflare is investigating issues causing an increase of errors for Durable Objects and downstream services in DEN. We are working to analyse and mitigate this problem. More updates to follow shortly.

Cloudflare is investigating delays in propagation of updates to DNS records in multiple regions. More updates to follow shortly.

We are continuing to monitor for any further issues.

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

Cloudflare is investigating an increased level of HTTP 502 errors. We are working to analyse and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

Cloudflare is investigating issues causing an increase of errors for Durable Objects and downstream services in Western Europe from 09:00 UTC. This is currently recovering. More updates to follow shortly.

We are continuing to monitor for any further issues.

Cloudflare has identified an issue whereby customers might experience errors from inference requests to certain models using Workers AI. These are the list of impacted model: @cf/deepseek-ai/deepseek-v4-flash-0731 @cf/deepseek-ai/deepseek-v4-pro-0813 @cf/zai-org/glm-5.2 @cf/zai-org/glm-5.3 @cf/zai-org/glm-5.3-flash We are working to mitigate this problem. More updates to follow shortly.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

Cloudflare is investigating an issue causing degraded performance for Browser Run. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

Workers Cron Trigger backlogs have cleared and appear healthy. Cron Trigger schedules should be executing as expected. Some schedule redeploys may be required for a small fraction of Workers who were impacted during the incident.

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

This incident has been resolved.

Cloudflare has implemented a fix and is currently monitoring for exceptions. We will update the status once the issue is resolved.

Cloudflare is aware of, and has resolved, an increased level of HTTP errors in London (LHR), between 07:43 UTC and 07:51 UTC. Services have resumed normal operation after this time.

We are continuing to monitor for any further issues.

A fix has been identified and is underway

Cloudflare is investigating issues with Workers Cron Triggers. Customers who have recently created or modified a Cron Trigger schedule may find that the schedule is not executing as expected. Pre-existing Cron Trigger schedules that have not been recently modified are not affected. We are working to identify the cause and mitigate this problem. More updates to follow shortly.

Cloudflare observed possible network congestion in Dallas, TX, United States (DFW) between 14th October 03:02–03:30 UTC. The issue has fully resolved, and we are monitoring for stability.

For about 30 minutes there was reduced availability for customers using the OBS API. This has been identified, and we are back to normal for now.

This incident has been resolved.

We are continuing to monitor for any further issues.

This incident has been resolved.

Cloudflare is investigating issues with network performance in LAX. 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 investigating issues with Workers Cron Triggers. Customers who have recently created or modified a Cron Trigger schedule may find that the schedule is not executing as expected. Pre-existing Cron Trigger schedules that have not been recently modified are not affected. We are working to identify the cause and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

We are continuing to monitor for any further issues.

Vendor has updated to say that their maintenance window will be extended till 13:00 UTC. Customers should continue to expect normal network behaviour and performance through the maintenance window.

Since 2026-10-12 at 16:57:24 UTC, audit logs from multiple Cloudflare products are not ingested into the audit logs v2 database anymore. V1 audit logs are not affected

Impact observed 06:33 - 06:41 UTC when we observe the vendor restoring the impacted capacity. We believe they temporarily affected all remaining capacity during the restoration and are following up with them. At this point all capacity has been restored and we are monitoring

We have identified the issue to be related to third-party circuit maintenance, have mitigated the impact that affected traffic, and customers should expect normal network behaviour and performance through the maintenance window. We will update when the maintenance is complete, expected at 10:00 GMT today (2026-10-13).

We have taken measures to address any impact and are closely monitoring the situation.

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

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

Cloudflare is investigating issues with network performance in Ashburn, US (IAD). We are working to analyse and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

This incident has been resolved.

Between 12:54 and 21:06 UTC on October 12, 2026, Cloudflare experienced an issue that affected network performance in Seattle. During this time, customers may have experienced degraded network performance. This incident has been resolved.

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

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

Cloudflare is investigating issues with Workers Cron Triggers. Customers who have recently created or modified a Cron Trigger schedule may find that the schedule is not executing as expected. Pre-existing Cron Trigger schedules that have not been recently modified are not affected. We are working to identify the cause and mitigate this problem. More updates to follow shortly.

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

Cloudflare is investigating intermittent performance issues affecting some data centers. Customers may experience errors or increased latency when accessing websites and services proxied through Cloudflare. We are working to mitigate this issue.

We have identified that increased latency and 5xx errors affecting certain China Network colos are caused by cross-border routing instability in the China network. We are actively working to mitigate impact for affected customers by adjusting traffic routing, and are continuing to work with our network partners on a resolution. Customers experiencing issues may contact Cloudflare Support.

Customers reaching Los Angeles (LAX) colo may see an elevate number of errors. Our team is investigating and working on mitigating the issue.

We are investigating reports of degraded performance for traffic traversing the public internet between certain cities and provinces in mainland China and origin servers located outside the region. The impact is being reported across multiple ISPs and manifests as slower speeds or intermittent timeouts. While this congestion occurs upstream of Cloudflare's network, our engineering team is actively working to mitigate the effects. Intermittent 524 timeout errors is expected to continue due to ongoing congestion. While there is no fixed timeline for full resolution, as there are dependencies outside our network, we are taking steps to reduce customer impact.

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

We are investigating a spike in errors observed in our China colos.

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

Cloudflare is investigating an issue where Cloudflare One Client customers are incorrectly challenged while visiting some websites.