Cloudflare

Affected: CDN/Cache

1. investigating 2026-10-21 16:42 UTC

   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.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Bot Management

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-20 19:35 UTC

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

2. resolved 2026-10-20 20:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Dashboard, Zero Trust

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 03:20 UTC

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

2. investigating 2026-10-20 03:47 UTC

   We are continuing to investigate the issue.

3. investigating 2026-10-20 04:09 UTC

   We are continuing to investigate the issue.

4. investigating 2026-10-20 04:22 UTC

   We are continuing to investigate the issue.

5. identified 2026-10-20 04:40 UTC

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

6. monitoring 2026-10-20 04:44 UTC

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

7. monitoring 2026-10-20 05:46 UTC

   The Cloudflare Access API continues to experience higher-than-normal error rates and increased latency. We are working to resolve the remaining API issues. Edge functionality, including Access logins and Cloudflare Secure Web Gateway connectivity, has been fully restored. We...

8. monitoring 2026-10-20 06:14 UTC

   The Cloudflare Access API has been fully restored, with error rates and latency returning to normal levels. We continue to monitor these services.

9. resolved 2026-10-20 06:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Data Loss Prevention (DLP), Gateway

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-19 20:30 UTC

   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.

2. identified 2026-10-19 23:46 UTC

   We are rolling out a fix to restore Secure Web Gateway application controls for Google Gemini. Work continues to restore DLP prompt logging and enforcement.

3. resolved 2026-10-20 22:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: DNS Updates

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-19 11:28 UTC

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

2. identified 2026-10-19 11:35 UTC

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

3. monitoring 2026-10-19 11:39 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-10-19 11:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-18 08:50 UTC

   Due to unexpected prefix withdrawals on peering links in IAD and CMH (Ashburn, Virginia and Columbus, Ohio, in the United States) on an external provider, customers experienced increased latency and timeouts from 08:00 to 08:50 UTC. Services have fully normalized following the...

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Access, FedRamp Dashboard

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-16 17:56 UTC

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

2. investigating 2026-10-16 18:15 UTC

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

3. identified 2026-10-16 18:47 UTC

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

4. monitoring 2026-10-16 19:02 UTC

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

5. resolved 2026-10-16 19:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-16 13:03 UTC

   Between 12:58 and 13:03 UTC, Cloudflare experienced an elevated rate of HTTP 5xx errors in Ashburn (IAD). The incident is now resolved, and systems are fully operational.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-16 10:15 UTC

   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.

2. identified 2026-10-16 10:46 UTC

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

3. monitoring 2026-10-16 11:12 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-10-16 11:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Access

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-16 09:20 UTC

   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.

2. identified 2026-10-16 09:21 UTC

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

3. monitoring 2026-10-16 09:41 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-10-16 09:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Network

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-16 07:30 UTC

   Cloudflare investigated and resolved issues with network performance in Bangkok, Thailand. There may have been elevated response times and an increase in 5xx errors between 06:48 and 07:30 UTC. This has been resolved and normal operations have resumed.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Network

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-16 02:11 UTC

   Between 01:13 AM and 02:11 AM UTC, network performance at our ICN-A colo in Seoul was impacted. Users downstream of KINX may have experienced increased latency (TTFB) and elevated Network Error Logging (NEL) metrics due to network path congestion. Performance metrics have since...

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Workers

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-16 00:01 UTC

   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.

2. monitoring 2026-10-16 00:54 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-10-16 01:06 UTC

   Workers Cron Triggers have stabilized

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Ashburn, VA, United States - (IAD), Newark, NJ, United States - (EWR), Network

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-15 20:48 UTC

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

2. monitoring 2026-10-15 21:24 UTC

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

3. resolved 2026-10-15 21:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: London, United Kingdom - (LHR), Durable Objects, R2, RealtimeKit

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-15 17:33 UTC

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

2. resolved 2026-10-15 17:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Pages

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 16:42 UTC

   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.

2. identified 2026-10-15 20:52 UTC

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

3. monitoring 2026-10-15 21:15 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-10-15 21:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-15 16:10 UTC

   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.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: AI Search, Artifacts, Containers, D1, Durable Objects, Workers Assets, Workflows

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 15:37 UTC

   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.

2. identified 2026-10-15 16:12 UTC

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

3. resolved 2026-10-15 18:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: DNS Updates

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 15:33 UTC

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

2. identified 2026-10-15 16:13 UTC

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

3. monitoring 2026-10-15 16:27 UTC

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

4. resolved 2026-10-15 18:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: CDN/Cache, Network

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 10:47 UTC

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

2. identified 2026-10-15 11:27 UTC

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

3. monitoring 2026-10-15 11:41 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-10-15 20:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Durable Objects

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-10-15 09:18 UTC

   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.

2. resolved 2026-10-15 10:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Workers AI

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 07:10 UTC

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

2. monitoring 2026-10-15 07:57 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-10-15 09:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Browser Run

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 05:57 UTC

   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.

2. identified 2026-10-15 06:37 UTC

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

3. monitoring 2026-10-15 06:44 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-10-15 06:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Network

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-14 07:51 UTC

   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.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Workers

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-14 05:36 UTC

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

2. identified 2026-10-14 07:23 UTC

   A fix has been identified and is underway

3. monitoring 2026-10-14 08:14 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-10-15 01:29 UTC

   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.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Network

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-14 05:20 UTC

   Customers reaching Los Angeles (LAX) colo may have seen an elevate number of errors during the time. The problem has been mitigated, and we are currently monitoring.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Portland, OR, United States - (PDX)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-14 04:40 UTC

   Cloudflare is investigating increased numbers of 5XX errors in PDX. We are working to analyse and mitigate this problem. More updates to follow shortly.

2. monitoring 2026-10-14 04:54 UTC

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

3. resolved 2026-10-14 06:45 UTC

   Mitigations have been put in place to prevent recurrence.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Observatory

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-10-14 04:12 UTC

   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.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Dallas, TX, United States - (DFW)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-14 03:30 UTC

   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.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Los Angeles, CA, United States - (LAX)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-13 20:37 UTC

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

2. resolved 2026-10-13 22:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-13 17:07 UTC

   Cloudflare saw issues with network performance in IAD that resulted in an increase in errors across Cloudflare services. Users may have experienced increases errors or timeouts reaching Cloudflare’s network or services.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Workers

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 15:18 UTC

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

2. identified 2026-10-13 15:19 UTC

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

3. monitoring 2026-10-13 23:10 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-10-14 00:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Audit Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-13 10:14 UTC

   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

2. monitoring 2026-10-13 11:45 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-10-16 00:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Ashburn, VA, United States - (IAD)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-13 04:00 UTC

   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.

2. identified 2026-10-13 04:52 UTC

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

3. identified 2026-10-13 04:52 UTC

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

4. monitoring 2026-10-13 05:00 UTC

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

5. monitoring 2026-10-13 05:09 UTC

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

6. monitoring 2026-10-13 06:57 UTC

   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

7. monitoring 2026-10-13 10:42 UTC

   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.

8. resolved 2026-10-13 14:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Workers

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-12 19:09 UTC

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

2. monitoring 2026-10-12 19:39 UTC

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

3. resolved 2026-10-12 22:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: CDN/Cache

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-12 16:22 UTC

   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.

2. identified 2026-10-12 17:13 UTC

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

3. resolved 2026-10-12 23:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Workers

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-12 13:32 UTC

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

2. monitoring 2026-10-12 13:42 UTC

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

3. resolved 2026-10-12 14:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Seattle, WA, United States - (SEA)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-12 21:06 UTC

   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.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Los Angeles, CA, United States - (LAX)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-12 08:52 UTC

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

2. identified 2026-10-12 21:41 UTC

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

3. resolved 2026-10-13 17:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: China Network

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-10 04:13 UTC

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

2. identified 2026-10-10 05:48 UTC

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

3. identified 2026-10-12 04:23 UTC

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

4. identified 2026-10-12 15:33 UTC

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

5. monitoring 2026-10-14 17:50 UTC

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

6. resolved 2026-10-15 09:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Cloudflare:

• Gamma: DNS resolution issue for some areas in Brazil

1. investigating 2026-10-09 18:52 UTC

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

2. identified 2026-10-09 20:58 UTC

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

3. monitoring 2026-10-09 21:10 UTC

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

4. resolved 2026-10-10 02:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Queretaro, MX, Mexico - (QRO), Network

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 18:50 UTC

   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.

2. monitoring 2026-10-09 18:51 UTC

   We have identified the cause of this issue and have applied a fix. We are currently monitoring the results.

3. resolved 2026-10-09 19:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Gateway, Singapore, Singapore - (SIN), Recursive DNS

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 14:41 UTC

   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.

2. investigating 2026-10-09 14:42 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-10-09 16:03 UTC

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

4. resolved 2026-10-09 19:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-08 22:31 UTC

   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.

2. resolved 2026-10-08 22:32 UTC

   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.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-08 17:00 UTC

   Cloudflare resolved an issue with network performance for our Kochi (COK) facility which occurred today, 2026-10-08, between approximately 14:00 and 17:00 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-08 14:00 UTC

   Cloudflare resolved an issue with network performance for our Kochi (COK) facility which occurred today, 2026-10-08, between approximately 14:00 and 17:00 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-07 14:41 UTC

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

2. monitoring 2026-10-07 14:55 UTC

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

3. resolved 2026-10-07 15:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Columbus, OH, United States - (CMH), Network

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 02:48 UTC

   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.

2. identified 2026-10-07 03:06 UTC

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

3. monitoring 2026-10-07 05:11 UTC

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

4. resolved 2026-10-07 11:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Network

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Knock-on incidents at other vendors that started during this one and name Cloudflare:

• Snowflake: INC20000263

1. investigating 2026-10-06 13:34 UTC

   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.

2. identified 2026-10-06 14:15 UTC

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

3. monitoring 2026-10-06 14:34 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-10-06 15:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Keyless SSL

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-06 08:22 UTC

   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.

2. monitoring 2026-10-06 08:55 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-10-06 09:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.

Affected: Cloudflare One Client

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-22 19:23 UTC

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

2. identified 2026-09-23 11:02 UTC

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

3. monitoring 2026-10-14 16:43 UTC

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

4. resolved 2026-10-14 16:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudflare's status page.