Cloudflare

We are currently investigating a network latency issue in NRT

Cloudflare is aware of and investigating an increased number of errors from Durable Objects in Dallas, Texas, USA. More updates to follow.

Cloudflare is aware of and investigating an issue with Cloudflare Workers and Pages build failures which potentially impacts multiple customers. Further detail will be provided as more information becomes available.

Cloudflare is investigating issues with Network Performance in the APJC region. We are working to analyze and mitigate this problem. More updates to follow shortly.

Cloudflare is investigating an increased level of errors for Containers failing to start. We are working to analyse and mitigate this problem. More updates to follow shortly.

Cloudflare is investigating an issue affecting Cloudflare Gateway DNS-over-TLS (DoT) connections over IPv4. Affected customers may experience connection timeouts and failed DNS resolution. This issue is limited to DoT over IPv4. DoT over IPv6, DNS-over-HTTPS (DoH), and standard DNS over UDP/TCP are not affected. We are working to identify the cause and restore connectivity. Further updates will be provided as more information becomes available.

Some customers may see delays when deploying updates to Cloudflare Workers. Remediation is in progress.

Cloudflare is observing cache purge delay in Qingdao in Shandong, China. We are working to resolve this issue as soon as possible. More updates to follow.

Cloudflare is aware of, and investigating an issue with Browser Run which potentially impacts multiple customers. Customers may see intermittent 500 errors when trying to use Browser Run Quick Actions. We are currently investigating this issue.

Cloudflare is investigating elevated latency affecting R2 requests in Eastern Europe. We are actively investigating and will provide further updates as soon as more information becomes available.

Cloudflare has identified the cause of increased errors affecting Durable Objects and downstream services in the Eastern North America (ENAM) region. We are working to implement a fix.

Cloudflare is investigating an issue where customers are experiencing elevated errors for operations on Increased Durable Objects, D1 and Workflows.

We are currently investigating reports of increased HTTP 429 (Rate Limit Exceeded) errors impacting users accessing dash.cloudflare.com. This issue primarily affects legitimate users connecting via shared egress networks (such as Cloudflare One default egress IPs or external corporate proxies). Our engineering team is actively investigating the root cause and adjusting rate-limiting thresholds to restore normal dashboard access.

Cloudflare is investigating issues causing degraded availability and elevated error rates for Durable Objects in Eastern Europe (EEUR2 region). Customers using Durable Objects or dependent services may experience increased errors or latency. We are actively investigating and will provide further updates as soon as more information becomes available

Cloudflare is investigating an issue where success rates and SLIs for Workflows operations have been dipping since approximately 07:00 UTC. Customers may experience increased errors or failures when running workflows. Our team is actively investigating the root cause to restore normal service.

Cloudflare has identified an issue where customers are experiencing elevated 500 errors impacting Durable Objects, D1, Workflows, Workers Assets uploads and Cloudchamber.

Cloudflare is aware of and investigating an issue affecting Cloudflare Network Interconnect (CNI) 2.0 traffic in LAX (Los Angeles). Some CNI 2.0 customers with traffic in this location may observe increased errors and/or latency on their connections.

Cloudflare is investigating increased error rates and latency for R2 in ENAM region.

Cloudflare is aware of, and investigating an issue with Durable Objects and downstream services which potentially impacts multiple customers in the Eastern North America region. Durable Objects in the region may experience increased error rates, and elevated errors for storage operations. This may also affect downstream services such as D1, Queues and Workflows etc. We are currently investigating this issue.

Cloudflare is investigating network performance issues affecting our Ashburn (IAD) data center. Traffic routed through this location may experience elevated latency and/or 5xx errors. We are working to analyze and mitigate this problem. More updates to follow shortly.

Cloudflare is aware of, and investigating an issue with Durable Objects and downstream services which potentially impacts multiple customers in the Eastern North America region. Durable Objects are experiencing an elevated level of overload errors in the aforementioned region. This may also affect downstream services such as D1, Queues and Workflows etc. We are currently investigating this issue.

Beginning approximately 19:30 UTC, Network Error Logging (NEL) reports are not being processed. Reports received during this period will not appear in Network Error Logging analytics. Website traffic and other services are not affected. We are investigating and will provide an update as soon as possible.

The Cloudflare engineering team is investigating an elevated level of Access api errors. This may result in configuration update failing or being delayed. Authentication and policy enforcement are not impacted at this time.

We are currently investigating an issue that is causing intermittent failures in unsafe topic detection within AI Security for Apps.

Cloudflare Stream is investigating degraded playback of certain live broadcasts originating from Western Europe and long processing times for on-demand video uploads.

Some single-file cache purge requests (purge by URL) submitted through the Dashboard or API and routed through our EEUR purge queues are experiencing delays of up to 30 minutes. Cache invalidation for these requests may be delayed across our global network. This also affects Always Online. We are working to resolve the issue. As a temporary workaround, you may use Purge Everything, but this may cause a surge in traffic to your origin server(s) More updates to follow.

Cloudflare has identified an issue affecting customers whose traffic passes through an external vendor firewall. Customers may observe: ERR_TIMED_OUT on standard HTTPS websites ERR_EMPTY_RESPONSE on non-standard HTTPS ports (e.g., 8443) We're investigating to confirm the root cause and possible fixes.

Cloudflare has identified an issue impacting some Workers Builds customers where we would fail to deploy Workers with Containers. We are working to mitigate the problem. More updates to follow shortly.

We are currently investigating an issue where some customers may notice their Pages and/or workers builds are intermittently failing.

We are investigating reports that some Workers Cron Triggers are running late, being skipped, or running more than once. Affected customers may see scheduled Workers invocations that do not run on time or run more than once. We will post an update as we learn more.

Cloudflare is investigating increased delays running Workers builds. We are working to analyse and mitigate this problem. More updates to follow shortly.

Cloudflare is investigating issues causing an increase of errors for Workflow Operations. We are working to analyze and mitigate this problem. More updates to follow shortly.

Cloudflare is investigating issues with Network Performance in Ashburn, VA. We are working to analyze and mitigate this problem. More updates to follow shortly.

We are investigating degraded network performance affecting some traffic between our Ashburn and Atlanta data centers. Some customers may see increased latency, packet loss, or intermittent errors on Workers and other services in the Eastern US. Our network team is actively working on mitigation.

We are investigating reports that some Workers Cron Triggers are running late, being skipped, or running more than once. Affected customers may see scheduled Workers invocations that do not run on time or run more than once. We will post an update as we learn more.

Cloudflare is investigating issues with Cloudflare Access when using Microsoft Entra ID. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

Our helpdesk provider is currently experiencing issues, and as such customers might encounter errors while submitting or viewing tickets. Responses on customer inquiries may be delayed during this time.

We are investigating elevated error rates affecting Durable Objects in Western Europe. Customers may see errors when using Durable Objects and related services. We will post updates as we learn more.

We are investigating an issue affecting audit log delivery for WARP API. Audit logs for some customers may be delayed or not delivered, and some dependent services may also be affected. We have identified the cause as a capacity problem in a shared internal data pipeline in our PDX region. Mitigations are in place and the pipeline is partially recovered. We are continuing to monitor and work toward full recovery.

We are investigating elevated error rates (HTTP 502) for some requests handled by our Ashburn, Virginia data center. Some customers may see failed or intermittent responses for websites and applications, including Workers, served through this location. We are actively investigating and will provide updates as we learn more.

Since 20:19 UTC, new Network Error Logging (NEL) reports are not being processed. Reports received during this period will not appear in Network Error Logging analytics. Website traffic and other services are not affected. We are investigating and will provide an update as soon as possible.

Cloudflare is investigating an increased latency when interacting with Workers API and Workers configuration in the dashboard. Customers might experience longer wait times on Workers endpoints, particularly when deploying a script. Workers that are already running in production are not affected. More updates to follow shortly.

Cloudflare is experiencing network congestion in Portland and Seattle, US. We are working to mitigate impact to Internet users in this region.

We are currently investigating an issue where we are observing higher than usual error rates for Durable Objects in our Lisbon (LIS) facility.

We are investigating reports of increased latency affecting some traffic in India. Affected users may experience slower loading times. Our engineering teams are investigating, and we will provide an update as more information becomes available.

Cloudflare is investigating issues with our Bot Management feature. Customers may observe a limited number of verified bots incorrectly identified as automated traffic

Cloudflare is investigating an issue with traffic that goes through Cloudflare One Gateway when an identity policy is present in the policy decision. This impacts all onramps to Cloudflare One Gateway. Cloudflare One Gateway policies with no identity policy are unaffected. We are also seeing impact to the Cloudflare Dashboard and are investigating further.

Cloudflare has identified an issue affecting Gateway application controls and Data Loss Prevention (DLP) inspection for certain Google Gemini traffic. We are working on a fix and will provide further updates as more information becomes available.

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

Cloudflare is investigating issues with accessing the Cloudflare Fedramp Dashboard and related Cloudflare Access services. Logging into dashboards and applications protected by Fedramp Access is impacted. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Edge. Cloudflare has identified the issue and is working on a fix.

Cloudflare is aware of and investigating an issue where some users are unable to sign up to the Cloudflare Dashboard. We are working to mitigate the problem and will update shortly.

Cloudflare is investigating issues with Cloudflare Access after login. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

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.

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.

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

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

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.

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.

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.

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 is investigating increased numbers of 5XX errors in PDX. We are working to analyse and mitigate this problem. More updates to follow shortly.

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

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.

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

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.

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

Cloudflare is investigating 504s errors when interacting with Workers API and Workers configuration in the dashboard. Customers might experience some unavailability on Workers endpoints, particularly when deploying a script. Workers that are already running in production are not affected. More updates to follow shortly.

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 a spike in errors observed in our China colos.

Cloudflare is investigating issues with Cloudflare Dashboard 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 Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.

Cloudflare is investigating issues with Network Performance in our Queretaro (QRO) facility. We are working to analyze and mitigate this problem. More updates to follow shortly.

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

Cloudflare resolved an issue with network performance for our Sofia (SOF) facility which occurred today, 2026-10-08, from approximately 21:35 to 21:50 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.

Cloudflare is investigating issues with Cloudflare Dashboard 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 Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.

Cloudflare is investigating issues with Network Performance in Columbus, OH (CMH). We are working to analyze and mitigate this problem. More updates to follow shortly.

Cloudflare is aware of an issue with network routing to Microsoft Azure, which is causing errors for requests directed to origins hosted on that service. The team is actively working on remediation.

Cloudflare is aware of and is investigating an issue with Keyless SSL, which results in TLS handshake failures, only affecting RSA Keyless SSL with specific key backend configurations. We are working to resolve this. Updates to follow.