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, 1y
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, 1y
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

Show all 54
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

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)