Hosting / Edge platform / Cloudflare

Cloudflare

SEV 2 · BLEEDING · 2h 51m

Since Aug 2026 · 54 incidents · www.cloudflarestatus.com · checked just now

CompareStatus page
GradeFLast 90 days
FPRODBSHIP
Happening now
Oct 22, 2026ongoingSEV 2
Elevated error rates for Durable Objects in Western EuropeDurable Objects returned elevated errors in Western Europe for about half an hour; a fix was deployed and is being monitored.AI-graded · regional · Durable Objects +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Durable Objects had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Durable Objects returned elevated errors in Western Europe for about half an hour; a fix was deployed and is being monitored.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 17:51 UTC · 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. 18:19 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
Source
71 components affected30 major outage · 41 degradedAsia 26 · Latin America & the Caribbean 12 · Africa 8 · +5 more
All 71
  • Annaba, Algeria - (AAE)major outage
  • Cairo, Egypt - (CAI)major outage
  • Kinshasa, DR Congo - (FIH)major outage
  • Lilongwe, Malawi - (LLW)major outage
  • Anshun, China - (AVA)major outage
  • Bandar Seri Begawan, Brunei - (BWN)major outage
  • Bishkek, Kyrgyzstan - (FRU)major outage
  • Chongqing, China - (CKG)major outage
  • Johor Bahru, Malaysia - (JHB)major outage
  • Qingdao, China - (TAO)major outage
  • Shenzhen, China - (SZX)major outage
  • Thimphu, Bhutan - (PBH)major outage
  • Xiangyang, China - (XFN)major outage
  • Prishtine , Kosovo - (PRN)major outage
  • Saint Petersburg, Russia - (LED)major outage
  • Arica, Chile - (ARI)major outage
  • Campos dos Goytacazes, Brazil - (CAW)major outage
  • La Paz, Bolivia - (LPB)major outage
  • Palmas, Brazil - (PMW)major outage
  • Santiago de los Caballeros, Dominican Republic - (STI)major outage
  • St. George's, Grenada - (GND)major outage
  • Sulaymaniyah, Iraq - (ISU)major outage
  • Memphis, TN, United States - (MEM)major outage
  • Mexico City, Mexico - (MEX)major outage
  • Norfolk, VA, United States - (ORF)major outage
  • Omaha, NE, United States - (OMA)major outage
  • San Antonio, TX, United States - (SAT)major outage
  • Sioux Falls, SD, United States - (FSD)major outage
  • Canberra, ACT, Australia - (CBR)major outage
  • Hagatna, Guam - (GUM)major outage
  • Accra, Ghana - (ACC)degraded
  • Gaborone, Botswana - (GBE)degraded
  • Luanda, Angola - (LAD)degraded
  • Nairobi, Kenya - (NBO)degraded
  • Astana, Kazakhstan - (NQZ)degraded
  • Bangalore, India - (BLR)degraded
  • Bangkok, Thailand - (BKK)degraded
  • Baoji, China - (XIY)degraded
  • Chengdu, China - (CTU)degraded
  • Dhaka, Bangladesh - (DAC)degraded
  • Fuzhou, China - (FOC)degraded
  • Haikou, China - (HAK)degraded
  • Hengshui, China - (SJW)degraded
  • Jakarta, Indonesia - (CGK)degraded
  • Jinan, China - (TNA)degraded
  • Kaohsiung City - (KHH)degraded
  • Kolkata, India - (CCU)degraded
  • Kuala Lumpur, Malaysia - (KUL)degraded
  • Manila, Philippines - (MNL)degraded
  • Phnom Penh, Cambodia - (PNH)degraded
  • Yerevan, Armenia - (EVN)degraded
  • Audit Logsdegraded
  • Durable Objectsdegraded
  • Logsdegraded
  • Zero Trustdegraded
  • Istanbul, Turkey - (IST)degraded
  • Kyiv, Ukraine - (KBP)degraded
  • Tirana, Albania - (TIA)degraded
  • Vilnius, Lithuania - (VNO)degraded
  • Belo Horizonte, Brazil - (CNF)degraded
  • Bogotá, Colombia - (BOG)degraded
  • Panama City, Panama - (PTY)degraded
  • Porto Alegre, Brazil - (POA)degraded
  • Salvador, Brazil - (SSA)degraded
  • Santiago, Chile - (SCL)degraded
  • Baku, Azerbaijan - (GYD)degraded
  • Dubai, United Arab Emirates - (DXB)degraded
  • Erbil, Iraq - (EBL)degraded
  • Manama, Bahrain - (BAH)degraded
  • Queretaro, MX, Mexico - (QRO)degraded
  • Sydney, NSW, Australia - (SYD)degraded

Overview

30d90d1y
Admitted uptimeTime not covered by a Sev 1 the provider posted itself. A best case.
100.000%Grade F
IncidentsEverything posted on the status page except scheduled maintenance.
540 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
1h 13m
LongestLongest single incident, start to resolved.
55d 20h
Since lastTime since the last counted incident was resolved.
ongoing

By area

FProduction
40INCIDENTS
55d 22hAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Oct 10, 2026 · 5d 5hElevated Errors in China Network Colos
SEV 2Oct 12, 2026 · 32h 48mElevated errors in Los Angeles (LAX)
SEV 2Oct 14, 2026 · 19h 53mCloudflare Workers - Cron Trigger Activation Issues
Most hit
Network7
Cloudflare Sites and Services - Network7
Durable Objects6
Cloudflare Sites and Services - Durable Objects6
Worse. 40 in the last 6 months, 0 in the 6 before.
BShipping
13INCIDENTS
32h 03mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 2Oct 15, 2026 · 2h 23mIncreased Errors for Durable Objects
SEV 3Oct 13, 2026 · 8h 51mCloudflare Workers - Cron Trigger Activation Issues
SEV 3Oct 9, 2026 · 7h 19mCloudflare API service issues
Most hit
Workers4
Cloudflare Sites and Services - Workers4
DNS Updates2
Cloudflare Sites and Services - DNS Updates2
Worse. 13 in the last 6 months, 0 in the 6 before.
CleanSev 3–4Sev 1–2No data

What it costs

One small production web app, per month512 MB app on all month, 1M requests, 100 GB out, commercial use, one seat. Cheapest plan that runs it.
Workers Paid0 of 8 cheaper
BEST VALUE~$5/mo
Workers Paid minimum (10M requests included)$5

Workers has no egress charges. Assumes CPU time fits the included 30M CPU-ms; serverless, so memory isn't reserved. developers.cloudflare.com · checked Oct 22, 2026 · Wrong price?

Trend, last 12 months

Worse. 54 in the last 6 months, 0 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down35
Sev 3 · Can't shipCan't deploy, build or manage it10
Sev 4 · PapercutDocs, status page, slow dashboard9

When it breaks

Start times, last 12 months, UTC.

What breaks

Workers7 incidents
Cloudflare Sites and Services - Workers7 incidents
Network7 incidents
Cloudflare Sites and Services - Network7 incidents
Durable Objects6 incidents
Cloudflare Sites and Services - Durable Objects6 incidents

Communication

Updates eachStatus page updates per incident, on average.
3.0Last 12 months
Update gapMedian time between status page updates during an incident.
41mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 35Sev 1–2

Incident history

Oct 22, 2026ongoingSEV 2
Elevated error rates for Durable Objects in Western EuropeDurable Objects returned elevated errors in Western Europe for about half an hour; a fix was deployed and is being monitored.AI-graded · regional · Durable Objects +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Durable Objects had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Durable Objects returned elevated errors in Western Europe for about half an hour; a fix was deployed and is being monitored.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 17:51 UTC · 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. 18:19 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
Source
Oct 22, 2026ongoingSEV 4
Delayed audit log delivery for WARP and Zero Trust servicesAudit log delivery was delayed or missing for some customers after a PDX pipeline capacity problem; a fix is in place and being monitored.AI-graded · some customers · Audit Logs +3
Why this grade
  1. RULES · SEV 3
    Sev 3 because Audit Logs had a partial outage
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE
    Audit log delivery was delayed or missing for some customers after a PDX pipeline capacity problem; a fix is in place and being monitored.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 17:32 UTC · 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 toward full recovery.
  2. 17:50 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
Source
Oct 22, 202630mSEV 2
Elevated errors for some requests in Ashburn, VirginiaHTTP 502 errors hit some requests served from the Ashburn data center for about 30 minutes; other locations were not described as affected.AI-graded · one location · Ashburn, VA, United States - (IAD) +5
Why this grade
  1. RULES · SEV 2
    Sev 2 because CDN/Cache had degraded performance
  2. CLAUDE · SEV 2 · LOCAL · HIGH CONFIDENCE
    HTTP 502 errors hit some requests served from the Ashburn data center for about 30 minutes; other locations were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 17:01 UTC · 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. 17:31 UTC · resolved
    This incident has been resolved.
Source
Oct 22, 2026ongoingSEV 4
Network Error Log Processing UnavailableNetwork Error Logging report processing stopped, so new reports do not appear in analytics; website traffic and other services are unaffected.AI-graded · Logs +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Logs had a partial outage
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    Network Error Logging report processing stopped, so new reports do not appear in analytics; website traffic and other services are unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 16:30 UTC · 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.
Source
Oct 22, 202643mSEV 3
Cloudflare Workers API LatencyWorkers API and dashboard configuration were slow for about 40 minutes; running production Workers were unaffected.AI-graded · Workers +1
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Workers API and dashboard configuration were slow for about 40 minutes; running production Workers were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 15:33 UTC · identified
    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.
  2. 16:04 UTC · monitoring
    We are continuing to monitor for any further issues.
  3. 16:15 UTC · resolved
    This incident has been resolved.
Source
Oct 22, 20261h 46mSEV 2
Network congestion in Portland and Seattle, USNetwork congestion in the Portland and Seattle data centres degraded traffic for users routed there for about 105 minutes; other locations were unaffected.AI-graded · one location · Portland, OR, United States - (PDX) +3
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Network congestion in the Portland and Seattle data centres degraded traffic for users routed there for about 105 minutes; other locations were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 00:23 UTC · investigating
    Cloudflare is experiencing network congestion in Portland and Seattle, US. We are working to mitigate impact to Internet users in this region.
  2. 01:08 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 02:09 UTC · resolved
    This incident has been resolved.
Source
Oct 21, 202645mSEV 2
Elevated Error Rate for Durable Objects in LisbonDurable Objects had elevated error rates in Cloudflare's Lisbon facility for about 45 minutes; other locations were not reported affected.AI-graded · one location · Lisbon, Portugal - (LIS) +3
Why this grade
  1. RULES · SEV 2
    Sev 2 because Durable Objects had degraded performance
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Durable Objects had elevated error rates in Cloudflare's Lisbon facility for about 45 minutes; other locations were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 23:50 UTC · investigating
    We are currently investigating an issue where we are observing higher than usual error rates for Durable Objects in our Lisbon (LIS) facility.
  2. 00:35 UTC · resolved
    This incident has been resolved.
Source
Oct 21, 20262h 07mSEV 2
Elevated Errors for R2 and Durable Objects in ENAMR2 and Durable Objects showed elevated errors for some customers in Eastern North America for about three minutes; other regions were not reported affected.AI-graded · regional · Durable Objects +3
Why this grade
  1. RULES · SEV 1
    Sev 1 because Durable Objects had a partial outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    R2 and Durable Objects showed elevated errors for some customers in Eastern North America for about three minutes; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 19:05 UTC · resolved
    Cloudflare has resolved an issue affecting R2 and Durable Objects in the Eastern North America region. Some customers may have seen elevated errors between approximately 19:02 and 19:05 UTC on October 21, 2026.
  2. 21:21 UTC · resolved
    This incident has been resolved.
Source
Oct 21, 20263h 15mSEV 2
Increased Latency in IndiaCDN requests in India saw increased latency for some traffic over about three hours; other regions were not reported affected.AI-graded · regional · CDN/Cache +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because CDN/Cache had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    CDN requests in India saw increased latency for some traffic over about three hours; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 16:42 UTC · investigating
    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.
  2. 18:51 UTC · monitoring
    We have identified and implemented a fix for this issue and are currently monitoring the results.
  3. 19:57 UTC · resolved
    This incident has been resolved.
Source
Oct 20, 202641mSEV 4
Issue with Bot management traffic categorization for verified botsBot Management misclassified a limited number of verified bots as automated traffic for about 40 minutes.AI-graded · some customers · Bot Management +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE
    Bot Management misclassified a limited number of verified bots as automated traffic for about 40 minutes.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 19:35 UTC · investigating
    Cloudflare is investigating issues with our Bot Management feature. Customers may observe a limited number of verified bots incorrectly identified as automated traffic
  2. 20:16 UTC · resolved
    This incident has been resolved.
Source
Oct 20, 20263h 12mSEV 2
Cloudflare Zero Trust connectivityTraffic through Cloudflare One Gateway failed when identity policies were present, affecting all onramps. Access logins and the Access API saw elevated errors and latency. The dashboard was also impacted. A fix was deployed around 04:44 UTC, and the incident was resolved at 06:32 UTC.AI-graded · some customers · Dashboard +3
Why this grade
  1. RULES · SEV 3
    Sev 3 because Dashboard had a major outage
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Cloudflare Gateway traffic using identity policies failed across all onramps, and Access logins and the Access API were degraded; dashboard was also impacted.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
9 updates
  1. 03:20 UTC · investigating
    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.
  2. 03:47 UTC · investigating
    We are continuing to investigate the issue.
  3. 04:09 UTC · investigating
    We are continuing to investigate the issue.
  4. 04:22 UTC · investigating
    We are continuing to investigate the issue.
  5. 04:40 UTC · identified
    The issue has been identified and a fix is being implemented.
  6. 04:44 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  7. 05:46 UTC · monitoring
    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 continue to monitor these services.
  8. 06:14 UTC · monitoring
    The Cloudflare Access API has been fully restored, with error rates and latency returning to normal levels. We continue to monitor these services.
  9. 06:32 UTC · resolved
    This incident has been resolved.
Source
Oct 19, 202626h 17mSEV 4
Cloudflare Secure Web Gateway and DLP enforcement issues for Google GeminiGateway application controls and DLP inspection failed for some Google Gemini traffic for about 26 hours; customer apps were not described as affected.AI-graded · some customers · Data Loss Prevention (DLP) +3
Why this grade
  1. RULES · SEV 1
    Sev 1 because the provider reported data loss or exposure
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE
    Gateway application controls and DLP inspection failed for some Google Gemini traffic for about 26 hours; customer apps were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 20:30 UTC · identified
    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. 23:46 UTC · identified
    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. 22:46 UTC · resolved
    This incident has been resolved.
Source
Oct 19, 202623mSEV 3
DNS Update DelaysCloudflare reported delays in propagating DNS record updates from 11:28 to 11:50 UTC on 2026-10-19. A fix was applied and monitored, and the incident was resolved. The cause was not stated and the number of affected customers was not given.AI-graded · DNS Updates +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because DNS Updates had degraded performance
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    DNS record updates were delayed in propagation for about 22 minutes; the text does not say how many customers were affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 11:28 UTC · investigating
    Cloudflare is investigating delays in propagation of updates to DNS records. More updates to follow shortly.
  2. 11:35 UTC · identified
    We are continuing to work on a fix for the issue.
  3. 11:39 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 11:50 UTC · resolved
    This incident has been resolved.
Source
Oct 18, 202650mSEV 2
Network Performance Issues in Virginia and Ohio United StatesCustomers in Ashburn and Columbus saw increased latency and timeouts for 50 minutes after peering route withdrawals.AI-graded · regional
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Customers in Ashburn and Columbus saw increased latency and timeouts for 50 minutes after peering route withdrawals.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 08:50 UTC · resolved
    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 restoration of prefix advertisements.
Source
Oct 16, 20261h 13mSEV 2
Cloudflare Fedramp Dashboard and AccessCloudflare's FedRAMP Dashboard and Cloudflare Access were impaired, so logins to FedRAMP dashboards and apps protected by FedRAMP Access failed from 17:56 to 19:09 UTC on October 16. CDN caching and other edge security were not affected. Cloudflare identified the issue, implemented a fix, and resolved the incident.AI-graded · some customers · Access +3
Why this grade
  1. RULES · SEV 2
    Sev 3 because FedRamp Dashboard had a partial outage, raised to Sev 2 for security
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Access logins to FedRAMP dashboards and Access-protected apps failed for about 73 minutes; CDN serving and edge security were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 17:56 UTC · investigating
    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.
  2. 18:15 UTC · investigating
    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.
  3. 18:47 UTC · identified
    The issue has been identified and a fix is being implemented.
  4. 19:02 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  5. 19:09 UTC · resolved
    This incident has been resolved.
Source
Oct 16, 20265mSEV 2
Increased HTTP 5xx Errors AshburnElevated HTTP 5xx errors at the Ashburn (IAD) location for about five minutes; other locations were not mentioned as affected.AI-graded · one location
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Elevated HTTP 5xx errors at the Ashburn (IAD) location for about five minutes; other locations were not mentioned as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 13:03 UTC · resolved
    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.
Source
Oct 16, 20261h 09mSEV 4
Cloudflare Dashboard sign up issuesSome users were unable to sign up for the Cloudflare Dashboard from about 10:15 to 11:24 UTC on October 16, 2026. Cloudflare identified the issue, worked on a fix, monitored, and resolved it. No other impact was described.AI-graded · some customers · Dashboard +1
Why this grade
  1. RULES · SEV 4
    Sev 4 because Dashboard had degraded performance
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE
    Some users could not sign up for the Cloudflare Dashboard for about 70 minutes; existing accounts and running services were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 10:15 UTC · investigating
    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. 10:46 UTC · identified
    We are continuing to work on a fix for the issue.
  3. 11:12 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 11:24 UTC · resolved
    This incident has been resolved.
Source
Oct 16, 202638mSEV 3
Cloudflare Access Availability IssuesCloudflare Access had issues with login for about 40 minutes on 16 October 2026. Cloudflare identified the problem, deployed a fix, monitored, and resolved the incident. The update does not state how many users were affected.AI-graded · Access +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Cloudflare Access login failed for about 40 minutes; the text does not say how many users were affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 09:20 UTC · investigating
    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. 09:21 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 09:41 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 09:59 UTC · resolved
    This incident has been resolved.
Source
Oct 16, 202642mSEV 2
Network Performance Issues in ThailandElevated response times and 5xx errors hit traffic in Bangkok for about 42 minutes; the rest of the network was not described as affected.AI-graded · one location · Network +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Network had degraded performance
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Elevated response times and 5xx errors hit traffic in Bangkok for about 42 minutes; the rest of the network was not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 07:30 UTC · resolved
    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.
Source
Oct 16, 202658mSEV 2
Network issues in Incheon (ICN)Increased latency for users downstream of KINX at the Seoul ICN-A data centre for about 58 minutes; other locations unaffected.AI-graded · one location · Network +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Network had degraded performance
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Increased latency for users downstream of KINX at the Seoul ICN-A data centre for about 58 minutes; other locations unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 02:11 UTC · resolved
    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 returned to normal baselines, and the issue is now fully resolved.
Source
Oct 16, 20261h 05mSEV 2
Workers Cron Triggers issuesSome Workers Cron Triggers were not invoked for about an hour; the text says only a subset of customers was affected.AI-graded · some customers · Workers +1
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Some Workers Cron Triggers were not invoked for about an hour; the text says only a subset of customers was affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 00:01 UTC · identified
    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. 00:54 UTC · monitoring
    We are continuing to monitor for any further issues.
  3. 01:06 UTC · resolved
    Workers Cron Triggers have stabilized
Source
Oct 15, 202650mSEV 2
Network Performance Issues in Eastern North AmericaElevated latency and errors for traffic through Ashburn and Newark facilities for about 50 minutes; other locations unaffected.AI-graded · regional · Ashburn, VA, United States - (IAD) +5
Why this grade
  1. RULES · SEV 1
    Sev 1 because Network had a partial outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Elevated latency and errors for traffic through Ashburn and Newark facilities for about 50 minutes; other locations unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 20:48 UTC · identified
    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.
  2. 21:24 UTC · monitoring
    Our engineering teams are continuing to remediate the issue. No customer impact is being seen at this time.
  3. 21:38 UTC · resolved
    This incident has been resolved.
Source
Oct 15, 202613mSEV 2
Network Performance Issues in LondonNetwork performance degraded at Cloudflare's London (LHR) location for about 13 minutes; the text does not describe other regions.AI-graded · one location · London, United Kingdom - (LHR) +7
Why this grade
  1. RULES · SEV 1
    Sev 1 because Durable Objects had a partial outage
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Network performance degraded at Cloudflare's London (LHR) location for about 13 minutes; the text does not describe other regions.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 17:33 UTC · identified
    We are working to mitigate impact to Internet users in this region. Cloudflare has identified the issue and is implementing a fix.
  2. 17:46 UTC · resolved
    This incident has been resolved.
Source
Oct 15, 20264h 44mSEV 2
Pages.dev sites experiencing availability issues in Norwaypages.dev subdomains were not reachable from Norway starting 16:42 UTC on 2026-10-15. Pages sites on Custom Domains were not impacted. Cloudflare identified the issue, monitored, and resolved it at 21:26 UTC. The provider gave no cause in the updates.AI-graded · regional · Pages +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    pages.dev subdomains were unavailable in Norway for about five hours; Custom Domains were not affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 16:42 UTC · investigating
    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. 20:52 UTC · identified
    We are continuing to work on a fix for the issue.
  3. 21:15 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 21:26 UTC · resolved
    This incident has been resolved.
Source
Oct 15, 20265mSEV 2
Network Performance Issues in Kuala LumpurElevated errors and latency at Cloudflare's Kuala Lumpur facility for about five minutes; other locations were not reported affected.AI-graded · one location
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Elevated errors and latency at Cloudflare's Kuala Lumpur facility for about five minutes; other locations were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 16:10 UTC · resolved
    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.
Source
Oct 15, 20262h 23mSEV 2
Increased Errors for Durable ObjectsDurable Objects and downstream services returned elevated errors from the DEN location for about two and a half hours.AI-graded · one location · AI Search +13
Why this grade
  1. RULES · SEV 2
    Sev 2 because Durable Objects had degraded performance
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Durable Objects and downstream services returned elevated errors from the DEN location for about two and a half hours.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 15:37 UTC · investigating
    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. 16:12 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 18:00 UTC · resolved
    This incident has been resolved.
Source
Oct 15, 20262h 46mSEV 3
DNS Update DelaysCloudflare saw delays propagating DNS record updates across multiple regions from about 15:33 to 18:19 UTC on October 15, 2026. A fix was implemented and monitored before the incident was resolved. The provider did not describe customer traffic being down.AI-graded · regional · DNS Updates +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because DNS Updates had degraded performance
  2. CLAUDE · SEV 3 · REGIONAL · MEDIUM CONFIDENCE
    DNS record update propagation was delayed in multiple regions for about three hours; the text does not say serving traffic failed.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 15:33 UTC · investigating
    Cloudflare is investigating delays in propagation of updates to DNS records in multiple regions. More updates to follow shortly.
  2. 16:13 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 16:27 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 18:19 UTC · resolved
    This incident has been resolved.
Source
Oct 15, 20269h 52mSEV 2
Increased HTTP 502 ErrorsCloudflare saw increased HTTP 502 errors across its CDN and network services from 10:47 to 20:39 UTC on 15 October 2026. The updates do not describe the scope or the cause, and the incident was marked resolved after monitoring.AI-graded · CDN/Cache +3
Why this grade
  1. RULES · SEV 2
    Sev 2 because CDN/Cache had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Increased HTTP 502 errors on Cloudflare CDN and network for about 10 hours; the update text does not say how many requests or regions were hit.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 10:47 UTC · investigating
    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. 11:27 UTC · identified
    We are continuing to work on a fix for the issue.
  3. 11:41 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 20:39 UTC · resolved
    This incident has been resolved.
Source
Oct 15, 202644mSEV 2
Increased Errors for Durable Objects and Downstream Services in Western EuropeDurable Objects and downstream services showed increased errors in Western Europe for about an hour; other regions were not mentioned.AI-graded · regional · Durable Objects +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Durable Objects had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Durable Objects and downstream services showed increased errors in Western Europe for about an hour; other regions were not mentioned.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 09:18 UTC · monitoring
    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. 10:02 UTC · resolved
    This incident has been resolved.
Source
Oct 15, 20262h 26mSEV 2
Cloudflare Workers AI IssuesInference requests to five specific Workers AI models returned errors for about two and a half hours; other models were not named as affected.AI-graded · some customers · Workers AI +1
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Inference requests to five specific Workers AI models returned errors for about two and a half hours; other models were not named as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 07:10 UTC · investigating
    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.
  2. 07:57 UTC · monitoring
    We are continuing to monitor for any further issues.
  3. 09:37 UTC · resolved
    This incident has been resolved.
Source
Oct 15, 202649mSEV 2
Degraded performance for Cloudflare Browser RunCloudflare Browser Run had degraded performance starting at 05:57 UTC on 2026-10-15 and resolved at 06:46 UTC. The updates do not describe the cause or the scope of affected customers, and the fix is not described beyond monitoring after the work was completed.AI-graded · Browser Run +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Browser Run had degraded performance for about 50 minutes; the text does not say how many customers or regions were hit.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 05:57 UTC · investigating
    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. 06:37 UTC · identified
    We are continuing to work on a fix for the issue.
  3. 06:44 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 06:46 UTC · resolved
    This incident has been resolved.
Source
Oct 14, 20268mSEV 2
Increased HTTP Errors in London (LHR)Increased HTTP errors hit customer traffic at the London (LHR) point of presence for about 8 minutes, then recovered.AI-graded · one location · Network +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Network had degraded performance
  2. CLAUDE · SEV 2 · LOCAL · HIGH CONFIDENCE
    Increased HTTP errors hit customer traffic at the London (LHR) point of presence for about 8 minutes, then recovered.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 07:51 UTC · 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.
Source
Oct 14, 202619h 53mSEV 2
Cloudflare Workers - Cron Trigger Activation IssuesWorkers Cron Triggers that were recently created or modified did not execute as expected from October 14 to October 15, 2026. Pre-existing unchanged schedules were not affected. Cloudflare identified a fix, cleared the Cron Trigger backlogs, and said a small number of affected Workers may need their schedules redeployed.AI-graded · some customers · Workers +1
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Newly created or modified Workers Cron Triggers did not run as expected for about 19 hours; existing unchanged schedules were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 05:36 UTC · investigating
    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.
  2. 07:23 UTC · identified
    A fix has been identified and is underway
  3. 08:14 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 01:29 UTC · resolved
    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.
Source
Oct 14, 202625mSEV 2
Elevated errors in Los Angeles (LAX)Elevated errors for customers routed through the Los Angeles (LAX) data centre for about 25 minutes; mitigated.AI-graded · one location · Network +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Network had degraded performance
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Elevated errors for customers routed through the Los Angeles (LAX) data centre for about 25 minutes; mitigated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 05:20 UTC · resolved
    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.
Source
Oct 14, 20262h 05mSEV 2
Elevated number of 5XX errors in PDXElevated 5XX errors hit traffic served from Cloudflare's Portland, OR point of presence for about two hours; other locations were not reported affected.AI-graded · one location · Portland, OR, United States - (PDX) +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Elevated 5XX errors hit traffic served from Cloudflare's Portland, OR point of presence for about two hours; other locations were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 04:40 UTC · investigating
    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. 04:54 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 06:45 UTC · resolved
    Mitigations have been put in place to prevent recurrence.
Source
Oct 14, 202624mSEV 4
OBS API availabilityThe Observatory API had reduced availability for about 30 minutes; the text does not say how many customers were hit.AI-graded · Observatory +1
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    The Observatory API had reduced availability for about 30 minutes; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 04:12 UTC · resolved
    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.
Source
Oct 14, 202628mSEV 4
Possible Network Congestion in Dallas, TX, United States (DFW)Possible network congestion at Cloudflare's Dallas (DFW) location for about 28 minutes; the update gives no measured error rates.AI-graded · one location · Dallas, TX, United States - (DFW) +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · LOCAL · MEDIUM CONFIDENCE
    Possible network congestion at Cloudflare's Dallas (DFW) location for about 28 minutes; the update gives no measured error rates.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 03:30 UTC · resolved
    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.
Source
Oct 13, 20262h 07mSEV 3
Network Performance Issues in LAXNetwork performance degraded at the Los Angeles (LAX) point of presence for about two hours; other locations were not reported affected.AI-graded · one location · Los Angeles, CA, United States - (LAX) +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · LOCAL · MEDIUM CONFIDENCE
    Network performance degraded at the Los Angeles (LAX) point of presence for about two hours; other locations were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 20:37 UTC · identified
    Cloudflare is investigating issues with network performance in LAX. We are working to analyse and mitigate this problem. More updates to follow shortly.
  2. 22:44 UTC · resolved
    This incident has been resolved.
Source
Oct 13, 202628mSEV 2
Cloudflare Service IssuesNetwork performance issues in the IAD location raised errors and timeouts across Cloudflare services for about 28 minutes.AI-graded · one location
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Network performance issues in the IAD location raised errors and timeouts across Cloudflare services for about 28 minutes.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 17:07 UTC · resolved
    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.
Source
Oct 13, 20268h 51mSEV 3
Cloudflare Workers - Cron Trigger Activation IssuesCloudflare Workers Cron Triggers that were recently created or modified did not execute as expected from about 15:18 to 00:09 UTC on October 13-14. Pre-existing schedules were not affected. The provider identified the issue and implemented a fix, then monitored before resolving it.AI-graded · some customers · Workers +1
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Newly created or modified Workers Cron Triggers did not run as expected for about nine hours; existing schedules were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 15:18 UTC · investigating
    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.
  2. 15:19 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 23:10 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 00:09 UTC · resolved
    This incident has been resolved.
Source
Oct 13, 20262d 14hSEV 4
Audit Logs v2 ingestion is missing multiple Cloudflare products Audit log v2 entries from several Cloudflare products stopped being ingested for about three days; v1 logs and running services were unaffected.AI-graded · some customers · Audit Logs +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Audit Logs had degraded performance
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE
    Audit log v2 entries from several Cloudflare products stopped being ingested for about three days; v1 logs and running services were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 10:14 UTC · identified
    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. 11:45 UTC · monitoring
    We are continuing to monitor for any further issues.
  3. 00:36 UTC · resolved
    This incident has been resolved.
Source
Oct 13, 202610h 56mSEV 2
Network performance issues in Ashburn, US (IAD)Cloudflare's Ashburn (IAD) location had network performance issues caused by third-party circuit maintenance. Traffic was rerouted to mitigate impact. A vendor restoration briefly affected remaining capacity from 06:33 to 06:41 UTC. The incident was resolved at 14:56 UTC after the vendor maintenance window ended.AI-graded · one location · Ashburn, VA, United States - (IAD) +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Network performance degraded in the Ashburn (IAD) data centre for about 10 hours; mitigated traffic, with a brief impact spike around 06:33-06:41 UTC.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
8 updates
  1. 04:00 UTC · investigating
    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. 04:52 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 04:52 UTC · identified
    We are continuing to work on a fix for the issue.
  4. 05:00 UTC · monitoring
    We have taken measures to address any impact and are closely monitoring the situation.
  5. 05:09 UTC · 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).
  6. 06:57 UTC · monitoring
    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. 10:42 UTC · monitoring
    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. 14:56 UTC · resolved
    This incident has been resolved.
Source
Oct 12, 20263h 11mSEV 3
Cloudflare Workers - Cron Trigger Activation IssuesNewly created or modified Workers Cron Trigger schedules did not execute as expected for about three hours; pre-existing schedules were unaffected.AI-graded · some customers · Workers +1
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Newly created or modified Workers Cron Trigger schedules did not execute as expected for about three hours; pre-existing schedules were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 19:09 UTC · investigating
    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.
  2. 19:39 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 22:20 UTC · resolved
    This incident has been resolved.
Source
Oct 12, 20267h 28mSEV 2
Cloudflare Network Performance IssuesProxied sites saw intermittent errors and latency from some Cloudflare data centers for about seven hours.AI-graded · CDN/Cache +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because CDN/Cache had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Proxied sites saw intermittent errors and latency from some Cloudflare data centers for about seven hours.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 16:22 UTC · investigating
    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. 17:13 UTC · identified
    We are continuing to work on a fix for the issue.
  3. 23:49 UTC · resolved
    This incident has been resolved.
Source
Oct 12, 202633mSEV 3
Cloudflare Workers APIWorkers API and dashboard config returned 504s, blocking script deploys; already-running Workers were unaffected, for about 33 minutes.AI-graded · Workers +1
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Workers API and dashboard config returned 504s, blocking script deploys; already-running Workers were unaffected, for about 33 minutes.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 13:32 UTC · investigating
    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.
  2. 13:42 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 14:05 UTC · resolved
    This incident has been resolved.
Source
Oct 12, 20268h 12mSEV 2
Network Performance Issues in SeattleDegraded network performance for customers routed through Cloudflare's Seattle location for about eight hours; other locations were not described as affected.AI-graded · one location · Seattle, WA, United States - (SEA) +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Degraded network performance for customers routed through Cloudflare's Seattle location for about eight hours; other locations were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 21:06 UTC · 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.
Source
Oct 12, 202632h 48mSEV 2
Elevated errors in Los Angeles (LAX)Elevated errors for customers routed through Cloudflare's Los Angeles (LAX) data centre over about 33 hours; other locations were not described as affected.AI-graded · one location · Los Angeles, CA, United States - (LAX) +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Elevated errors for customers routed through Cloudflare's Los Angeles (LAX) data centre over about 33 hours; other locations were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 08:52 UTC · investigating
    Customers reaching Los Angeles (LAX) colo may see an elevate number of errors. Our team is investigating and working on mitigating the issue.
  2. 21:41 UTC · identified
    We are continuing to work on a fix for the issue.
  3. 17:40 UTC · resolved
    This incident has been resolved.
Source
Oct 10, 20265d 5hSEV 2
Elevated Errors in China Network ColosCloudflare saw spikes in errors and latency at some China network colos from October 10 to 15, 2026. Cross-border routing instability in China caused slow speeds and intermittent 524 timeouts for traffic to origins outside the region, across multiple ISPs. Cloudflare rerouted traffic and worked with network partners; a fix was implemented October 14 and the incident was resolved October 15.AI-graded · regional · China Network +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because China Network had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Elevated latency and 5xx errors hit traffic through certain China Network colos for several days; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
6 updates
  1. 04:13 UTC · investigating
    We are investigating a spike in errors observed in our China colos.
  2. 05:48 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 04:23 UTC · identified
    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.
  4. 15:33 UTC · identified
    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.
  5. 17:50 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  6. 09:28 UTC · resolved
    This incident has been resolved.
Source
Oct 9, 20267h 19mSEV 3
Cloudflare API service issuesCloudflare's dashboard and API requests failed or showed errors from about 18:52 to 02:12 UTC. Cached file serving and edge security were not affected. The provider identified the issue, deployed a fix, and resolved the incident. The text gives no scope or root cause.AI-graded · API +1
Why this grade
  1. RULES · SEV 2
    Sev 3 because API had degraded performance, raised to Sev 2 for security
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Cloudflare API requests failed or errored for about 9 hours; CDN serving and edge security were not affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 18:52 UTC · investigating
    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.
  2. 20:58 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 21:10 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 02:12 UTC · resolved
    This incident has been resolved.
Source
Oct 9, 202620mSEV 2
Network Performance Issues in QueretaroNetwork performance degraded at Cloudflare's Queretaro facility for about 20 minutes; other locations were not described as affected.AI-graded · one location · Queretaro, MX, Mexico - (QRO) +3
Why this grade
  1. RULES · SEV 2
    Sev 2 because Network had degraded performance
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Network performance degraded at Cloudflare's Queretaro facility for about 20 minutes; other locations were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 18:50 UTC · investigating
    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. 18:51 UTC · monitoring
    We have identified the cause of this issue and have applied a fix. We are currently monitoring the results.
  3. 19:10 UTC · resolved
    This incident has been resolved.
Source
Oct 9, 20264h 49mSEV 2
Cloudflare DNS Resolver 1.1.1.1 and Gateway DNS are having issues in SINCloudflare's 1.1.1.1 public resolver and Gateway DNS had issues in Singapore (SIN) for multiple users, starting 14:41 UTC and resolved about five hours later. A fix was implemented and monitored before resolution. The cause was not stated in the updates.AI-graded · regional · Gateway +5
Why this grade
  1. RULES · SEV 2
    Sev 2 because Recursive DNS had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Cloudflare's 1.1.1.1 public resolver and Gateway DNS had issues for multiple users in Singapore for about five hours; other regions were not named.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 14:41 UTC · investigating
    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. 14:42 UTC · investigating
    We are continuing to investigate this issue.
  3. 16:03 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 19:30 UTC · resolved
    This incident has been resolved.
Source
Oct 8, 202657mSEV 2
Network Performance Issues in SofiaCloudflare's Sofia (SOF) facility had network performance problems from about 21:35 to 21:50 UTC on 2026-10-08. Customers may have seen elevated latency and error rates there. Cloudflare resolved the issue.AI-graded · one location
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Elevated latency and errors at Cloudflare's Sofia facility for about 15 minutes; other locations were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 22:31 UTC · investigating
    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. 22:32 UTC · resolved
    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.
Source
Sep 22, 202621d 21hSEV 3
Cloudflare One Clients are incorrectly challenged on some sitesCloudflare One Client users were incorrectly challenged while visiting some websites from September 22 to October 14, 2026. The provider identified the cause, deployed a fix, and resolved the incident after monitoring.AI-graded · some customers · Cloudflare One Client +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Cloudflare One Client users were incorrectly challenged on some websites for about three weeks; other traffic was unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 19:23 UTC · investigating
    Cloudflare is investigating an issue where Cloudflare One Client customers are incorrectly challenged while visiting some websites.
  2. 11:02 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 16:43 UTC · monitoring
    Cloudflare has implemented a fix and is currently monitoring for exceptions. We will update the status once the issue is resolved.
  4. 16:54 UTC · resolved
    This incident has been resolved.
Source
Aug 27, 202655d 20hSEV 4
Incorrect geo location for some Cloudflare WARP usersSome Cloudflare WARP and Zero Trust users were incorrectly geolocated by certain third-party services from August 27 to October 22, 2026. Cloudflare worked with third-party providers on a fix and marked the incident resolved after almost two months. The update text gives no further cause or detail.AI-graded · some customers · WARP +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE
    WARP and Zero Trust users were geolocated incorrectly by some third-party services for weeks; apps and core routing were not described as failing.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
9 updates
  1. 18:46 UTC · investigating
    Cloudflare is investigating issues with Cloudflare WARP and Cloudflare Zero Trust users being incorrectly geolocated by some third party services.
  2. 18:56 UTC · identified
    The issue has been identified and we are working with third party providers to fix it.
  3. 00:55 UTC · identified
    We are continuing to work on a fix for this issue.
  4. 11:30 UTC · identified
    We are continuing to work on a fix for this issue.
  5. 15:31 UTC · identified
    We are continuing to work on a fix for this issue.
  6. 15:51 UTC · identified
    We are continuing to work on a fix for this issue.
  7. 15:15 UTC · identified
    We are continuing to work on a fix for this issue.
  8. 08:29 UTC · identified
    We are continuing to work on a fix for this issue.
  9. 15:41 UTC · resolved
    This incident has been resolved.
Source

Peers, 90 days

Compare
HerokuGrade A+100.00% up0 incidentsMTTR –$7/moNetlifyGrade B100.00% up17 incidentsMTTR 34m~$20/moRenderGrade C100.00% up13 incidentsMTTR 1h 35m$21.25/moVercelGrade C100.00% up23 incidentsMTTR 47m~$20/moDigitalOceanGrade F100.00% up18 incidentsMTTR 4h 02m$6/moFly.ioGrade F99.38% up25 incidentsMTTR 44m$5.69/moCloudflareGrade F100.00% up54 incidentsMTTR 1h 13m~$5/moRailwayGrade F98.31% up27 incidentsMTTR 55m~$12/mo

README badge

Cloudflare's live grade, for your README.

Cloudflare grade badge
[![cloudflare on downagain.dev](https://downagain.dev/badge/cloudflare.svg)](https://downagain.dev/p/cloudflare)