BLACKOUT.NETWORK › Network Status › Providers › Cloudflare

BLACKOUT.NETWORK · NETWORK STATUS

Cloudflare status right now

A network in front of a large share of websites: CDN, DDoS protection, DNS (including the 1.1.1.1 resolver), WARP and Zero Trust access.

Minor issueOfficial: Partially Degraded ServiceOur check: Partially Degraded Service
2active incidents now
50incidents in the last 90 days (official feed)
100.00%of our 5-minute checks with no degraded or major status, last 7 days

Live status

From Cloudflare Statuspage API. Times in Eastern (ET).

Degraded connectivity between Europe and Asia Pacific

Nov 18, 5:26 PM EST · ongoing · Minor issue · source: Cloudflare
Cache ReserveD1R2

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

Changes to Cloudflare Workers are not producing Event Subscription events

Nov 9, 8:53 PM EST · ongoing · Minor issue · source: Cloudflare
WorkersQueues

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

Edge data centers by region

North America56 of 63 sites normal · 1 in maintenance · 6 degraded or re-routedAlbuquerque, United States - (ABQ) (partial outage), Charlotte, United States - (CLT) (partial outage), Norfolk, United States - (ORF) (partial outage)
Europe54 of 61 sites normal · 4 in maintenance · 3 degraded or re-routedSaint Petersburg, Russia - (LED) (partial outage), Tallinn, Estonia - (TLL) (partial outage), Thessaloniki, Greece - (SKG) (partial outage)
Latin America & the Caribbean41 of 52 sites normal · 6 in maintenance · 5 degraded or re-routedArica, Chile - (ARI) (partial outage), Joinville, Brazil - (JOI) (partial outage), St. George's, Grenada - (GND) (partial outage)
Asia62 of 100 sites normal · 20 in maintenance · 18 degraded or re-routedAhmedabad, India - (AMD) (partial outage), Hagatna, Guam - (GUM) (partial outage), Islamabad, Pakistan - (ISB) (partial outage)
Africa23 of 34 sites normal · 5 in maintenance · 6 degraded or re-routedAnnaba, Algeria - (AAE) (partial outage), Harare, Zimbabwe - (HRE) (partial outage), Kinshasa, Congo - Kinshasa - (FIH) (partial outage)
Middle East15 of 22 sites normal · 7 in maintenance
Oceania10 of 13 sites normal · 1 in maintenance · 2 degraded or re-routedCanberra, Australia - (CBR) (partial outage), Tahiti, French Polynesia - (PPT) (partial outage)

Green = normal, blue = planned maintenance, orange = degraded or re-routed. A few sites re-routed at any time is normal; traffic moves to the next site.

Services and components · 39 of 40 normal

Cache Reservedegraded performance
CDN/Cacheoperational
Always Onlineoperational
CDN Cache Purgeoperational
Cloud Connectoroperational
Custom Pagesoperational
Load Balancing and Monitoringoperational
Speed Optimizationsoperational
Waiting Roomoperational
WebSocketsoperational
Authoritative DNSoperational
DNS Firewalloperational
DNS Root Serversoperational
DNS Updatesoperational
Recursive DNSoperational
Secondary DNSoperational
DNSSEC Updatesoperational
Networkoperational
Argo Smart Routingoperational
Bring Your Own IP (BYOIP)operational
Cloud Network Interconnect (CNI)operational
Health Checksoperational
Infrastructureoperational
IP Geolocationoperational

Our 5-minute checks · last 7 days

We read Cloudflare's official status every 5 minutes. Each sliver is one hour, colored by the worst status seen; the daily figure is the share of checks with no degraded or major status. Stored since Nov 11, 9:48 PM EST.

7 days agonow
100%Wed 11/11
100%Thu 11/12
100%Fri 11/13
100%Sat 11/14
100%Sun 11/15
100%Mon 11/16
100%Tue 11/17
100%Wed 11/18

Periods flagged by our checks

  • Nov 11, 9:48 PM EST → ongoing

    Partially Degraded Service

    Replicate Model Registry Unavailable; Changes to Cloudflare Workers are not producing Event Subscription events; Fedramp Customers have Delayed Purges; 70 component(s) not operational: Amman, Jordan - (AMM) (under maintenance), Albuquerque,

Incident history

Incidents per month from the official feed, by severity. The public Statuspage API returns only the latest 50 incidents (back to Nov 4, 2026). History is short: dashed boxes and empty months before the feed's first entry mean no published data, not a clean record.

No data: before the feed historyDecNo data: before the feed historyJanNo data: before the feed historyFebNo data: before the feed historyMarNo data: before the feed historyAprNo data: before the feed historyMayNo data: before the feed historyJunNo data: before the feed historyJulNo data: before the feed historyAugNo data: before the feed historySepNo data: before the feed historyOctNov 2026: 48 minor issueNov 2026: 2 operational50Nov
No data: before the feed historyJunNo data: before the feed historyJulNo data: before the feed historyAugNo data: before the feed historySepNo data: before the feed historyOctNov 2026: 48 minor issueNov 2026: 2 operational50Nov

Last 13 weeks

Before the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no data1 incident(s)120 incident(s)2029 incident(s)2913 weeks agothis week
Before the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no dataBefore the feed history: no data1 incident(s)120 incident(s)2029 incident(s)2913 weeks agothis week
OperationalMinorDegradedMajorNo data

Root causes: hack, AI, config error or something else?

For each incident in the past year we show a cause only when Cloudflare's own report states one, quoting the sentence. The category is our label for that sentence; anything else is marked Unconfirmed / not yet disclosed.

Unconfirmed / not yet disclosed: 49Other (see official report): 150incidents
Unconfirmed / not yet disclosed: 49
Other (see official report): 1
  • Nov 18, 5:26 PM EST · ongoing

    Degraded connectivity between Europe and Asia Pacific

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 18, 3:35 PM EST · resolved Nov 18, 6:22 PM EST

    Increased latency on Analytics API (GraphQL) queries

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 18, 8:45 AM EST · resolved Nov 18, 10:03 AM EST

    R2 Downloads Stalling in Japan

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 18, 3:04 AM EST · resolved Nov 18, 3:46 AM EST

    Network disruption across multiple colocations in India

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 18, 2:00 AM EST · resolved Nov 18, 5:00 AM EST

    Network Performance Issues in North America

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 17, 10:39 PM EST · resolved Nov 17, 11:51 PM EST

    Network Performance Issues in Paris

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 17, 9:31 PM EST · resolved Nov 17, 10:04 PM EST

    Elevated 5xx error rates and latency in Mumbai

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 17, 8:10 PM EST · resolved Nov 17, 9:39 PM EST

    Cloudflare Access Issue

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 17, 4:56 PM EST · resolved Nov 17, 7:17 PM EST

    Issues with Durable Objects and Dependent Services

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 17, 3:05 PM EST · resolved Nov 17, 5:08 PM EST

    R2 elevated errors and timeouts for requests from South America

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 17, 12:12 PM EST · resolved Nov 17, 1:00 PM EST

    Network performance issues in Los Angeles (LAX) and Frankfurt (FRA) datacenters

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 17, 10:02 AM EST · resolved Nov 17, 10:23 PM EST

    Errors and stalled predictions on some models

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 17, 8:55 AM EST · resolved Nov 17, 9:35 AM EST

    Elevated number of 5xx and 499 errors

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 17, 8:54 AM EST · resolved Nov 17, 9:56 AM EST

    Cloudflare One Gateway traffic unable to connect to Cloudflare domains that are regionalized

    Other (see official report)

    “Engineering has identified the root cause and is preparing a fix for release A fix has been implemented and we are monitoring the results.” — Cloudflare

    Official incident report

  • Nov 17, 5:24 AM EST · resolved Nov 17, 11:37 AM EST

    Turnstile verification failures

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 16, 11:50 PM EST · resolved Nov 17, 12:50 AM EST

    Elevated number of 52x origin connectivity errors in Seoul

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 16, 7:41 PM EST · resolved Nov 16, 8:48 PM EST

    Network Performance Issues in Ashburn, US

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 16, 3:10 PM EST · resolved Nov 16, 3:40 PM EST

    Network Performance Issues in Montreal, Canada

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 16, 9:30 AM EST · resolved Nov 16, 11:19 AM EST

    Errors creating predictions for some models

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 14, 8:30 PM EST · resolved Nov 14, 10:00 PM EST

    Elevated number of errors in Bogotá

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 14, 2:41 PM EST · resolved Nov 14, 3:20 PM EST

    Elevated error rates on R2 buckets in West North America

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 14, 12:30 AM EST · resolved Nov 14, 1:45 AM EST

    Increased errors for R2 and Tiered Cache

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 13, 6:53 PM EST · resolved Nov 13, 8:01 PM EST

    Issues with 1.1.1.1 public resolver in Canada

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 13, 10:31 AM EST · resolved Nov 14, 8:37 AM EST

    Cloudflare is seeing an issue with Workers API availability

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Nov 13, 9:55 AM EST · resolved Nov 13, 7:51 PM EST

    Cloudflare is currently having an issue with the r8.im registry used for Replicate model publishing and builds is currently restricted

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

Notable past outages

The big ones, with the cause in the official write-up's own words.

Dec 5, 2025

Body-parsing change breaks ~28% of HTTP traffic

Config / deploy error

“The issue was not caused, directly or indirectly, by a cyber attack… Instead, it was triggered by changes being made to our body parsing logic while attempting to detect and mitigate an industry-wide vulnerability.”

Impact: About 25 minutes of failures for a subset of customers (about 28% of HTTP traffic Cloudflare serves).

Cloudflare post-mortem
Nov 18, 2025

Global outage from a Bot Management feature file

Config / deploy error

“The issue was not caused, directly or indirectly, by a cyber attack… it was triggered by a change to one of our database systems' permissions which caused the database to output multiple entries into a 'feature file' used by our Bot Management system.”

Impact: Error pages on a large share of websites behind Cloudflare worldwide for several hours.

Cloudflare post-mortem
Jul 14, 2025

1.1.1.1 DNS resolver offline worldwide

Config / deploy error

“The root cause was an internal configuration error and not the result of an attack or a BGP hijack.”

Impact: 62 minutes of downtime for the 1.1.1.1 resolver; for many users almost nothing on the Internet would load.

Cloudflare post-mortem
Jun 12, 2025

Workers KV outage from a third-party storage provider

Third-party dependency

“Part of this infrastructure is backed by a third-party cloud provider, which experienced an outage today and directly impacted availability of our KV service.”

Impact: 2 hours 28 minutes of impact on Workers KV, WARP, Access, Gateway, Turnstile and more.

Cloudflare post-mortem
Jul 2, 2019

WAF rule exhausts CPU worldwide

Config / deploy error

“The CPU exhaustion was caused by a single WAF rule that contained a poorly written regular expression that ended up creating excessive backtracking.”

Impact: Cloudflare's HTTP/HTTPS service went offline for 27 minutes.

Cloudflare post-mortem
Know about the next big outage first
The free BLACKOUT.NETWORK newsletter: major outages, threats and what to do. Follow us on YouTube and X too.
Get the free newsletter

If your business runs on Cloudflare

A short playbook. Tick items as you go (saved on this device only).

1 · Confirm the impact

2 · Fail over and limit the damage

3 · Monitor and get alerts

4 · Communication templates

Customer heads-up (incident open)

Status update ({time} ET): Some of our services are slow or unavailable because of an outage at Cloudflare, a provider we use. Your data is safe. We're working around it and will update you by {next} ET. Live status: {your_status_page}

Internal alert

Cloudflare incident affecting {services} in {region} since {time} ET. Impact on us: {impact}. Owner: {name}. Failover: {yes_no}. Next check-in {next} ET.

All clear

Resolved ({time} ET): Cloudflare has recovered and our services are back to normal. If anything still looks wrong, reply here or contact {support}. Thank you for your patience.

Fill in the {curly} parts. Post updates somewhere not hosted on the affected provider.

Official links, contacts and alerts

Every link checked before publishing. Phone numbers only where Cloudflare publishes them.

Other providers: AWS · Microsoft Azure · Microsoft 365 · Google Cloud · Google Workspace · Akamai · Starlink · Networks near me · All network checks. Research only; not affiliated with Cloudflare (CDN, DNS 1.1.1.1, Zero Trust). Names identify services only.