Official incident history

  1. Increased error rate in Workflow Operations

    Started: · Duration: 44 min
    Provider updates (3)
    1. Investigating “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.”
    2. Monitoring “We are continuing to monitor for any further issues.”
    3. Resolved “This incident has been resolved.”
    Resolved
  2. Network Performance Issues in Ashburn

    Started: · Duration: 128 min
    Provider updates (3)
    1. Investigating “Cloudflare is investigating issues with Network Performance in Ashburn, VA. We are working to analyze and mitigate this problem. More updates to follow shortly.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved
  3. NBO (Nairobi) on 2026-10-23

    Started: · Duration: still open
    Provider updates (2)
    1. Scheduled “We will be performing scheduled maintenance in NBO (Nairobi) datacenter between 2026-10-23 22:45 and 2026-10-26 23:45 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting th…”
    2. In progress “Scheduled maintenance is currently in progress. We will provide updates as necessary.”
    Open
  4. ANC (Anchorage) on 2026-10-27

    Started: · Duration: still open
    Provider updates (1)
    1. Scheduled “We will be performing scheduled maintenance in ANC (Anchorage) datacenter on 2026-10-27 between 16:30 and 18:30 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this tra…”
    Planned
  5. Delayed, missed, and duplicated Workers Cron Triggers

    Started: · Duration: 310 min
    Provider updates (3)
    1. Investigating “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.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved
  6. TPA (Tampa) on 2026-10-26

    Started: · Duration: still open
    Provider updates (1)
    1. Scheduled “We will be performing scheduled maintenance in TPA (Tampa) datacenter on 2026-10-26 between 06:00 and 12:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic…”
    Planned
  7. GIG (Rio de Janeiro) on 2026-10-27

    Started: · Duration: still open
    Provider updates (1)
    1. Scheduled “We will be performing scheduled maintenance in GIG (Rio de Janeiro) datacenter on 2026-10-27 between 08:00 and 10:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting thi…”
    Planned
  8. Network connectivity issues affecting services in North America

    Started: · Duration: 176 min
    Provider updates (6)
    1. Investigating “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.”
    2. Identified “We have identified a connectivity provider outage causing network congestion and degraded performance for some customers in North America. Affected customers may experience increased latency, packet loss, and intermittent errors across multiple services. Our network team is rerouting traffic away from affected paths, and we are working directly with our provider on restoration.”
    3. Monitoring “A fix has been implemented and we are monitoring the results.”
    4. Identified “We are continuing to work on a fix for the issue.”
    5. Monitoring “Our network team has rerouted traffic around the impacted paths and we are no longer seeing packet drops. Our connectivity provider reports that its service has been restored, but some links are still being brought back, so we are keeping our traffic management changes in place.”
    6. Resolved “This incident has been resolved.”
    Resolved
  9. LHR (London) on 2026-10-27

    Started: · Duration: still open
    Provider updates (1)
    1. Scheduled “We will be performing scheduled maintenance in LHR (London) datacenter on 2026-10-27 between 02:00 and 05:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffi…”
    Planned
  10. EWR (Newark) on 2026-10-27

    Started: · Duration: still open
    Provider updates (1)
    1. Scheduled “We will be performing scheduled maintenance in EWR (Newark) datacenter on 2026-10-27 between 06:00 and 14:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffi…”
    Planned
  11. BNA (Nashville) on 2026-10-27

    Started: · Duration: still open
    Provider updates (1)
    1. Scheduled “We will be performing scheduled maintenance in BNA (Nashville) datacenter on 2026-10-27 between 06:00 and 12:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this tra…”
    Planned
  12. ICN (Seoul) on 2026-10-25

    Started: · Duration: still open
    Provider updates (1)
    1. Scheduled “We will be performing scheduled maintenance in ICN (Seoul) datacenter between 2026-10-25 22:00 and 2026-10-26 07:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this…”
    Planned
  13. Support Helpdesk Availability Issues

    Started: · Duration: 399 min
    Provider updates (4)
    1. Investigating “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.”
    2. Identified “Support portal, live chat support and emergency telephone line are still unavailable due to the ongoing helpdesk provider outage. Customers may experience issues submitting or viewing tickets/chats, and overall response times may be delayed. Customers with urgent issues should revert to using the support email address (backupsupport@cloudflare.com).”
    3. Monitoring “A fix has been implemented and we are monitoring the results.”
    4. Resolved “This incident has been resolved.”
    Resolved
  14. Cloudflare Access Availability Issues

    Started: · Duration: 21 min
    Provider updates (4)
    1. Investigating “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.”
    2. Identified “The issue has been identified and a fix is being implemented.”
    3. Monitoring “A fix has been implemented and we are monitoring the results.”
    4. Resolved “This incident has been resolved.”
    Resolved
  15. IAD (Ashburn) on 2026-10-27

    Started: · Duration: still open
    Provider updates (1)
    1. Scheduled “We will be performing scheduled maintenance in IAD (Ashburn) datacenter on 2026-10-27 between 06:00 and 10:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traff…”
    Planned
  16. Delayed audit log delivery for WARP and Zero Trust services

    Started: · Duration: 398 min
    Provider updates (3)
    1. Investigating “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 tow…”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved
  17. Elevated error rates for Durable Objects in Western Europe

    Started: · Duration: 378 min
    Provider updates (3)
    1. Investigating “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.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved
  18. HNL (Honolulu) on 2026-10-30

    Started: · Duration: still open
    Provider updates (1)
    1. Scheduled “We will be performing scheduled maintenance in HNL (Honolulu) datacenter on 2026-10-30 between 08:00 and 13:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traf…”
    Planned
  19. Network Error Log Processing Unavailable

    Started: · Duration: 330 min
    Provider updates (3)
    1. Investigating “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.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved
  20. Elevated errors for some requests in Ashburn, Virginia

    Started: · Duration: 30 min
    Provider updates (2)
    1. Investigating “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.”
    2. Resolved “This incident has been resolved.”
    Resolved

What the provider published about this service, with the provider's own updates (wording quoted as published).

Evidence

Official
Cloudflare Status ↗ · Partial System Outage · Oct 25, 01:37 AM UTC
Korantix
HTTP 200 · 686 ms · Oct 25, 01:37 AM UTC

Why this assessment

  • Provider reports: “Partial System Outage”
  • Korantix reached the endpoint (HTTP 200, 686 ms). This only shows that the endpoint answered.
  • 686 ms is within this service's usual range (median 560 ms, p95 856 ms over 658 checks).

Rule set assess-1. The same evidence always gives the same result.

Evidence and freshness

Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.

SourceLast observedAgeUsed in assessment
Official1 min agoYes — recent
Korantix1 min agoYes — recent

Technical details

Affected components (provider)

  • Arica, Chile - (ARI) · Major outage
  • Annaba, Algeria - (AAE) · Major outage
  • Baku, Azerbaijan - (GYD) · Degraded
  • Bangalore, India - (BLR) · Degraded
  • Canberra, ACT, Australia - (CBR) · Major outage
  • Belo Horizonte, Brazil - (CNF) · Degraded
  • Bandar Seri Begawan, Brunei - (BWN) · Major outage
  • Hagatna, Guam - (GUM) · Major outage
  • Bogotá, Colombia - (BOG) · Degraded
  • Dubai, United Arab Emirates - (DXB) · Degraded
  • Erbil, Iraq - (EBL) · Degraded
  • Sydney, NSW, Australia - (SYD) · Degraded
  • Gaborone, Botswana - (GBE) · Degraded
  • Manama, Bahrain - (BAH) · Degraded
  • Curitiba, Brazil - (CWB) · Degraded
  • Luanda, Angola - (LAD) · Degraded
  • Mombasa, Kenya - (MBA) · Degraded
  • Nairobi, Kenya - (NBO) · Degraded
  • Fuzhou, China - (FOC) · Degraded
  • Istanbul, Turkey - (IST) · Degraded

Official status page ↗