Skip to content

Outage tracker / Cloudflare

Is Cloudflare down?

I'm having a problem

Operationalchecked moments ago

We reached Cloudflare from all 10 regions we check.

As of Sep 23, 2026, 9:09 AM UTC, Cloudflare answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Cloudflare (since Aug 8, 2026).

Cloudflare reports an active incident: "Increased Errors for Durable Objects" (minor incident, since Sep 23, 2026, 8:09 AM UTC). That is their claim, not our measurement: our probes are currently reaching Cloudflare, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Sep 23, 2026, 9:09 AM UTC
US-East349 msOperational
US-West50 msOperational
Europe75 msOperational
Asia-Pacific195 msOperational
US-Central252 msOperational
Canada45 msOperational
UK242 msOperational
Southeast Asia1228 msOperational
Australia232 msOperational
South America71 msOperational
their status pagetheir claim, not our reading

Cloudflare reports: Minor incident (“Minor Service Outage”)

from Cloudflare's own status page, checked Sep 23, 2026, 8:53 AM UTC

Cloudflare reports an active incident: Increased Errors for Durable Objects (minor incident, since Sep 23, 2026, 8:09 AM UTC)

Cloudflare's status page reports Minor Service Outage. Our probes are currently reaching Cloudflare successfully with normal latency. RealUptime's independent checks are currently succeeding from all 10 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

Cloudflare's own component breakdown, as they publish it

  • Abuse ReportsOperational
  • Accra, Ghana - (ACC)Operational
  • Adelaide, SA, Australia - (ADL)Operational
  • Ahmedabad, India - (AMD)Operational
  • Albuquerque, NM, United States - (ABQ)Operational
  • Americana, Brazil - (QWJ)Operational
  • Amman, Jordan - (AMM)Operational
  • Amsterdam, Netherlands - (AMS)Operational
  • AccessOperational
  • Algiers, Algeria - (ALG)Partial outage
  • Almaty, Kazakhstan - (ALA)Operational
  • Anchorage, AK, United States - (ANC)Operational
  • Arica, Chile - (ARI)Partial outage
  • Astara, Azerbaijan - (LLK)Operational
  • Athens, Greece - (ATH)Operational
  • Auckland, New Zealand - (AKL)Operational
  • Account ManagementOperational
  • Annaba, Algeria - (AAE)Partial outage
  • Ashburn, VA, United States - (IAD)Operational
  • Asunción, Paraguay - (ASU)Operational
  • Baghdad, Iraq - (BGW)Under maintenance
  • Barcelona, Spain - (BCN)Operational
  • Brisbane, QLD, Australia - (BNE)Operational
  • AI GatewayOperational
  • Antananarivo, Madagascar - (TNR)Operational
  • Atlanta, GA, United States - (ATL)Operational
  • Baku, Azerbaijan - (GYD)Under maintenance
  • Bangalore, India - (BLR)Under maintenance
  • Belém, Brazil - (BEL)Operational
  • Belgrade, Serbia - (BEG)Operational
  • Canberra, ACT, Australia - (CBR)Partial outage
  • AI SearchOperational
  • Austin, TX, United States - (AUS)Operational
  • Bangkok, Thailand - (BKK)Operational
  • Basra, Iraq - (BSR)Operational
  • Belo Horizonte, Brazil - (CNF)Under maintenance
  • Berlin, Germany - (TXL)Operational
  • Cape Town, South Africa - (CPT)Operational
  • Christchurch, New Zealand - (CHC)Operational
  • Always OnlineOperational
  • Bandar Seri Begawan, Brunei - (BWN)Operational
  • Bangor, ME, United States - (BGR)Operational
  • Beirut, Lebanon - (BEY)Operational
  • Bordeaux, France - (BOD)Operational
  • Hagatna, Guam - (GUM)Partial outage
  • AnalyticsOperational
  • Bogotá, Colombia - (BOG)Operational
  • Boston, MA, United States - (BOS)Operational
  • Bratislava, Slovakia - (BTS)Operational
  • Dakar, Senegal - (DKR)Operational
  • Dammam, Saudi Arabia - (DMM)Under maintenance
  • APIOperational
  • Brasilia, Brazil - (BSB)Operational
  • Brussels, Belgium - (BRU)Operational
  • Buffalo, NY, United States - (BUF)Partial outage
  • Dar Es Salaam, Tanzania - (DAR)Operational
  • Doha, Qatar - (DOH)Operational
  • Melbourne, VIC, Australia - (MEL)Operational
  • API ShieldOperational
  • Bucharest, Romania - (OTP)Operational
  • Buenos Aires, Argentina - (EZE)Operational
  • Calgary, AB, Canada - (YYC)Operational
  • Cebu, Philippines - (CEB)Operational
  • Djibouti City, Djibouti - (JIB)Operational
  • Dubai, United Arab Emirates - (DXB)Operational
  • Noumea, New Caledonia - (NOU)Operational
  • Apps MarketplaceOperational
  • Budapest, Hungary - (BUD)Operational
  • Caçador, Brazil - (CFC)Operational
  • Chandigarh, India - (IXC)Operational
  • Charlotte, NC, United States - (CLT)Operational
  • Durban, South Africa - (DUR)Operational
  • Erbil, Iraq - (EBL)Operational
  • Perth, WA, Australia - (PER)Operational
  • Area 1 - APIOperational
  • Campinas, Brazil - (VCP)Operational
  • Changde, China - (CGD)Operational
  • Chicago, IL, United States - (ORD)Operational
  • Chișinău, Moldova - (KIV)Operational
  • Gaborone, Botswana - (GBE)Partial outage
  • Haifa, Israel - (HFA)Operational
  • Sydney, NSW, Australia - (SYD)Operational
  • Area 1 - DashOperational
  • Chennai, India - (MAA)Operational
  • Cleveland, OH, United States - (CLE)Operational
  • Copenhagen, Denmark - (CPH)Operational
  • Harare, Zimbabwe - (HRE)Operational
  • Jeddah, Saudi Arabia - (JED)Under maintenance
  • Tahiti, French Polynesia - (PPT)Operational
  • ArtifactsOperational
  • Columbus, OH, United States - (CMH)Operational
  • Córdoba, Argentina - (COR)Operational
  • Dublin, Ireland - (DUB)Operational
  • Johannesburg, South Africa - (JNB)Operational
  • Kuwait City, Kuwait - (KWI)Operational
  • Suva, Fiji - (SUV)Operational
  • Dallas, TX, United States - (DFW)Operational
  • Düsseldorf, Germany - (DUS)Operational
  • Kigali, Rwanda - (KGL)Operational
  • Manama, Bahrain - (BAH)Under maintenance

These are Cloudflare's components, named and scored by Cloudflare. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Cloudflare's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Cloudflare response time, by region

US-East
416msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 781ms2026-08-26 UTC: p95 804ms2026-08-27 UTC: p95 718ms2026-08-28 UTC: p95 449ms2026-08-29 UTC: p95 429ms2026-08-30 UTC: p95 458ms2026-08-31 UTC: p95 427ms2026-09-01 UTC: p95 554ms2026-09-02 UTC: p95 491ms2026-09-03 UTC: p95 528ms2026-09-04 UTC: p95 502ms2026-09-05 UTC: p95 376ms2026-09-06 UTC: p95 370ms2026-09-07 UTC: p95 371ms2026-09-08 UTC: p95 378ms2026-09-09 UTC: p95 390ms2026-09-10 UTC: p95 427ms2026-09-11 UTC: p95 410ms2026-09-12 UTC: p95 363ms2026-09-13 UTC: p95 382ms2026-09-14 UTC: p95 409ms2026-09-15 UTC: p95 423ms2026-09-16 UTC: p95 451ms2026-09-17 UTC: p95 449ms2026-09-18 UTC: p95 405ms2026-09-19 UTC: p95 407ms2026-09-20 UTC: p95 413ms2026-09-21 UTC: p95 394ms2026-09-22 UTC: p95 400ms2026-09-23 UTC: p95 416ms
Aug 25Sep 8Sep 23
US-West
422msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 442ms2026-08-26 UTC: p95 480ms2026-08-27 UTC: p95 540ms2026-08-28 UTC: p95 367ms2026-08-29 UTC: p95 423ms2026-08-30 UTC: p95 437ms2026-08-31 UTC: p95 363ms2026-09-01 UTC: p95 325ms2026-09-02 UTC: p95 385ms2026-09-03 UTC: p95 544ms2026-09-04 UTC: p95 410ms2026-09-05 UTC: p95 484ms2026-09-06 UTC: p95 433ms2026-09-07 UTC: p95 334ms2026-09-08 UTC: p95 376ms2026-09-09 UTC: p95 306ms2026-09-10 UTC: p95 273ms2026-09-11 UTC: p95 288ms2026-09-12 UTC: p95 226ms2026-09-13 UTC: p95 329ms2026-09-14 UTC: p95 286ms2026-09-15 UTC: p95 357ms2026-09-16 UTC: p95 392ms2026-09-17 UTC: p95 378ms2026-09-18 UTC: p95 382ms2026-09-19 UTC: p95 367ms2026-09-20 UTC: p95 372ms2026-09-21 UTC: p95 466ms2026-09-22 UTC: p95 430ms2026-09-23 UTC: p95 422ms
Aug 25Sep 8Sep 23
Europe
239msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 281ms2026-08-26 UTC: p95 233ms2026-08-27 UTC: p95 248ms2026-08-28 UTC: p95 240ms2026-08-29 UTC: p95 229ms2026-08-30 UTC: p95 217ms2026-08-31 UTC: p95 263ms2026-09-01 UTC: p95 273ms2026-09-02 UTC: p95 284ms2026-09-03 UTC: p95 233ms2026-09-04 UTC: p95 269ms2026-09-05 UTC: p95 239ms2026-09-06 UTC: p95 250ms2026-09-07 UTC: p95 196ms2026-09-08 UTC: p95 274ms2026-09-09 UTC: p95 256ms2026-09-10 UTC: p95 296ms2026-09-11 UTC: p95 259ms2026-09-12 UTC: p95 243ms2026-09-13 UTC: p95 247ms2026-09-14 UTC: p95 244ms2026-09-15 UTC: p95 252ms2026-09-16 UTC: p95 249ms2026-09-17 UTC: p95 253ms2026-09-18 UTC: p95 247ms2026-09-19 UTC: p95 243ms2026-09-20 UTC: p95 252ms2026-09-21 UTC: p95 287ms2026-09-22 UTC: p95 327ms2026-09-23 UTC: p95 239ms
Aug 25Sep 8Sep 23
Asia-Pacific
448msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 578ms2026-08-26 UTC: p95 472ms2026-08-27 UTC: p95 472ms2026-08-28 UTC: p95 623ms2026-08-29 UTC: p95 484ms2026-08-30 UTC: p95 609ms2026-08-31 UTC: p95 444ms2026-09-01 UTC: p95 565ms2026-09-02 UTC: p95 541ms2026-09-03 UTC: p95 508ms2026-09-04 UTC: p95 429ms2026-09-05 UTC: p95 479ms2026-09-06 UTC: p95 514ms2026-09-07 UTC: p95 476ms2026-09-08 UTC: p95 531ms2026-09-09 UTC: p95 566ms2026-09-10 UTC: p95 460ms2026-09-11 UTC: p95 422ms2026-09-12 UTC: p95 485ms2026-09-13 UTC: p95 465ms2026-09-14 UTC: p95 467ms2026-09-15 UTC: p95 407ms2026-09-16 UTC: p95 453ms2026-09-17 UTC: p95 506ms2026-09-18 UTC: p95 501ms2026-09-19 UTC: p95 494ms2026-09-20 UTC: p95 535ms2026-09-21 UTC: p95 505ms2026-09-22 UTC: p95 505ms2026-09-23 UTC: p95 448ms
Aug 25Sep 8Sep 23
US-Central
687msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 412ms2026-09-04 UTC: p95 555ms2026-09-05 UTC: p95 632ms2026-09-06 UTC: p95 628ms2026-09-07 UTC: p95 497ms2026-09-08 UTC: p95 340ms2026-09-09 UTC: p95 377ms2026-09-10 UTC: p95 491ms2026-09-11 UTC: p95 419ms2026-09-12 UTC: p95 343ms2026-09-13 UTC: p95 307ms2026-09-14 UTC: p95 287ms2026-09-15 UTC: p95 547ms2026-09-16 UTC: p95 535ms2026-09-17 UTC: p95 513ms2026-09-18 UTC: p95 503ms2026-09-19 UTC: p95 505ms2026-09-20 UTC: p95 505ms2026-09-21 UTC: p95 521ms2026-09-22 UTC: p95 875ms2026-09-23 UTC: p95 687ms
Aug 25Sep 8Sep 23
Canada
471msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 512ms2026-09-04 UTC: p95 435ms2026-09-05 UTC: p95 472ms2026-09-06 UTC: p95 428ms2026-09-07 UTC: p95 324ms2026-09-08 UTC: p95 470ms2026-09-09 UTC: p95 399ms2026-09-10 UTC: p95 287ms2026-09-11 UTC: p95 394ms2026-09-12 UTC: p95 392ms2026-09-13 UTC: p95 420ms2026-09-14 UTC: p95 464ms2026-09-15 UTC: p95 364ms2026-09-16 UTC: p95 536ms2026-09-17 UTC: p95 762ms2026-09-18 UTC: p95 427ms2026-09-19 UTC: p95 453ms2026-09-20 UTC: p95 415ms2026-09-21 UTC: p95 432ms2026-09-22 UTC: p95 493ms2026-09-23 UTC: p95 471ms
Aug 25Sep 8Sep 23
UK
302msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 251ms2026-09-04 UTC: p95 310ms2026-09-05 UTC: p95 280ms2026-09-06 UTC: p95 277ms2026-09-07 UTC: p95 250ms2026-09-08 UTC: p95 233ms2026-09-09 UTC: p95 155ms2026-09-10 UTC: p95 209ms2026-09-11 UTC: p95 173ms2026-09-12 UTC: p95 225ms2026-09-13 UTC: p95 234ms2026-09-14 UTC: p95 166ms2026-09-15 UTC: p95 224ms2026-09-16 UTC: p95 520ms2026-09-17 UTC: p95 622ms2026-09-18 UTC: p95 580ms2026-09-19 UTC: p95 579ms2026-09-20 UTC: p95 234ms2026-09-21 UTC: p95 560ms2026-09-22 UTC: p95 566ms2026-09-23 UTC: p95 302ms
Aug 25Sep 8Sep 23
Southeast Asia
1.1sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 703ms2026-09-04 UTC: p95 809ms2026-09-05 UTC: p95 752ms2026-09-06 UTC: p95 755ms2026-09-07 UTC: p95 780ms2026-09-08 UTC: p95 756ms2026-09-09 UTC: p95 621ms2026-09-10 UTC: p95 429ms2026-09-11 UTC: p95 630ms2026-09-12 UTC: p95 697ms2026-09-13 UTC: p95 738ms2026-09-14 UTC: p95 680ms2026-09-15 UTC: p95 766ms2026-09-16 UTC: p95 789ms2026-09-17 UTC: p95 709ms2026-09-18 UTC: p95 910ms2026-09-19 UTC: p95 906ms2026-09-20 UTC: p95 879ms2026-09-21 UTC: p95 982ms2026-09-22 UTC: p95 972ms2026-09-23 UTC: p95 1.1s
Aug 25Sep 8Sep 23
Australia
680msp95 · latest
1s500ms0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 784ms2026-09-04 UTC: p95 933ms2026-09-05 UTC: p95 681ms2026-09-06 UTC: p95 608ms2026-09-07 UTC: p95 682ms2026-09-08 UTC: p95 603ms2026-09-09 UTC: p95 490ms2026-09-10 UTC: p95 242ms2026-09-11 UTC: p95 665ms2026-09-12 UTC: p95 582ms2026-09-13 UTC: p95 620ms2026-09-14 UTC: p95 855ms2026-09-15 UTC: p95 719ms2026-09-16 UTC: p95 557ms2026-09-17 UTC: p95 649ms2026-09-18 UTC: p95 645ms2026-09-19 UTC: p95 702ms2026-09-20 UTC: p95 672ms2026-09-21 UTC: p95 672ms2026-09-22 UTC: p95 840ms2026-09-23 UTC: p95 680ms
Aug 25Sep 8Sep 23
South America
574msp95 · latest
1s500ms0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 727ms2026-09-04 UTC: p95 520ms2026-09-05 UTC: p95 631ms2026-09-06 UTC: p95 639ms2026-09-07 UTC: p95 579ms2026-09-08 UTC: p95 700ms2026-09-09 UTC: p95 594ms2026-09-10 UTC: p95 585ms2026-09-11 UTC: p95 518ms2026-09-12 UTC: p95 621ms2026-09-13 UTC: p95 536ms2026-09-14 UTC: p95 553ms2026-09-15 UTC: p95 598ms2026-09-16 UTC: p95 450ms2026-09-17 UTC: p95 611ms2026-09-18 UTC: p95 559ms2026-09-19 UTC: p95 583ms2026-09-20 UTC: p95 522ms2026-09-21 UTC: p95 650ms2026-09-22 UTC: p95 594ms2026-09-23 UTC: p95 574ms
Aug 25Sep 8Sep 23

Is it Cloudflare, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Cloudflare -- it cannot diagnose Cloudflare's own systems.

What we measured, function by function

Cloudflare answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 349msstatus code: 200checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Cloudflare normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 50msstatus code: 200checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Cloudflare normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 252msstatus code: 200checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Cloudflare normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 45msstatus code: 200checked: Sep 23, 2026, 9:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Cloudflare normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 71msstatus code: 200checked: Sep 23, 2026, 9:07 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Cloudflare normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 75msstatus code: 200checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Cloudflare normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 242msstatus code: 200checked: Sep 23, 2026, 9:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Cloudflare normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 195msstatus code: 200checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Cloudflare normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1228msstatus code: 200checked: Sep 23, 2026, 9:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Cloudflare normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 232msstatus code: 200checked: Sep 23, 2026, 9:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Cloudflare normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Cloudflare, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Cloudflare yet, which is not evidence that nothing is wrong.

Recent outages

Increased Errors for Durable Objectsdeclared on their status page2026-09-23
Elevated number of R2 503 errors in Australian Eastern Coast region, 17mdeclared on their status page2026-09-23
Issues with 1.1.1.1 for Families, 44mdeclared on their status page2026-09-23
Network Performance Issues in Taipei, 1mdeclared on their status page2026-09-22
Cloudflare One Clients are incorrectly challenged on some sitesdeclared on their status page2026-09-22
Bot Management Configuration Propagation Issues, 1h 4mdeclared on their status page2026-09-22
Connectivity issues in Los Angeles (LAX), 1mdeclared on their status page2026-09-22
Elevated error rates for Stream Live LL-HLS, 1h 1mdeclared on their status page2026-09-22

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Cloudflare since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Cloudflare covering any window you pick, with our measurements and Cloudflare's own claim at the time, side by side.

Full availability history for Cloudflare: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Cloudflare, and again when they can reach it again. That is our own measurement from ten regions, not Cloudflare's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Cloudflare uptime measured by RealUptimeLive, from this page's own readings.
[![Cloudflare uptime measured by RealUptime](https://realuptime.io/outages/cloudflare/badge.svg?days=30)](https://realuptime.io/outages/cloudflare)
<a href="https://realuptime.io/outages/cloudflare"><img src="https://realuptime.io/outages/cloudflare/badge.svg?days=30" alt="Cloudflare uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Cloudflare's SLA implies, from our measurement

At or above your target

We measured none of downtime for Cloudflare over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Cloudflare's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.cloudflare.com/client/v4/ips
secondary
https://www.cloudflare.com/
RealUptime is not affiliated with Cloudflare; the name identifies what we measured, and nothing here speaks for Cloudflare's own team. We send a single web request to Cloudflare from 10 regions on our own schedule and time the response. We do not see inside Cloudflare's systems, do not use an account or real transaction, and are not the same signal Cloudflare's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Cloudflare is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.