Skip to content

Outage tracker / Cloudflare

Is Cloudflare down?

I'm having a problem

Vendor reports an incidentWhat Cloudflare reports

Cloudflare reports an incident on its status page: Elevated number of 5XX errors in PDX.

Impact: minor. Since 2026-10-14 04:40 UTC.

Latest update, 2026-10-14 04:40 UTC: Cloudflare is investigating increased numbers of 5XX errors in PDX. We are working to analyse and mitigate this problem. More updates to follow shortly.

One more incident is open on its status page.

Cloudflare's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Cloudflare pass from all 10 regions we check.

As of Oct 14, 2026, 4:49 AM UTC, RealUptime's checks of Cloudflare passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 14, 2026, 4:49 AM UTC
US-East256 msChecks passing
US-West99 msChecks passing
Europe59 msChecks passing
Asia-Pacific43 msChecks passing
US-Central63 msChecks passing
Canada236 msChecks passing
UK168 msChecks passing
Southeast Asia54 msChecks passing
Australia332 msChecks passing
South America42 msChecks passing
their status pagetheir claim, not our reading

Cloudflare reports: Partial outage (“Partial System Outage”)

from Cloudflare's own status page, checked Oct 14, 2026, 4:42 AM UTC

Cloudflare reports an active incident: Elevated number of 5XX errors in PDX (minor incident, since Oct 14, 2026, 4:40 AM UTC)

Cloudflare's status page reports Partial System Outage. Our checks of Cloudflare currently pass with normal latency. Our checks currently pass 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 the vendor's report and our check reading side by side. A check can miss problems that users see. 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)Operational
  • Almaty, Kazakhstan - (ALA)Operational
  • Anchorage, AK, United States - (ANC)Operational
  • Arica, Chile - (ARI)Major outage
  • Astara, Azerbaijan - (LLK)Operational
  • Athens, Greece - (ATH)Operational
  • Auckland, New Zealand - (AKL)Operational
  • Account ManagementOperational
  • Annaba, Algeria - (AAE)Major outage
  • Ashburn, VA, United States - (IAD)Operational
  • Asunción, Paraguay - (ASU)Operational
  • Baghdad, Iraq - (BGW)Operational
  • Barcelona, Spain - (BCN)Operational
  • Brisbane, QLD, Australia - (BNE)Operational
  • AI GatewayOperational
  • Antananarivo, Madagascar - (TNR)Operational
  • Atlanta, GA, United States - (ATL)Operational
  • Baku, Azerbaijan - (GYD)Degraded performance
  • Bangalore, India - (BLR)Degraded performance
  • Belgrade, Serbia - (BEG)Operational
  • Belém, Brazil - (BEL)Operational
  • Canberra, ACT, Australia - (CBR)Major outage
  • AI SearchOperational
  • Austin, TX, United States - (AUS)Operational
  • Bangkok, Thailand - (BKK)Operational
  • Basra, Iraq - (BSR)Operational
  • Belo Horizonte, Brazil - (CNF)Degraded performance
  • Berlin, Germany - (TXL)Operational
  • Cape Town, South Africa - (CPT)Operational
  • Christchurch, New Zealand - (CHC)Major outage
  • 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)Major outage
  • AnalyticsOperational
  • Bogotá, Colombia - (BOG)Operational
  • Boston, MA, United States - (BOS)Operational
  • Bratislava, Slovakia - (BTS)Operational
  • Dakar, Senegal - (DKR)Operational
  • Dammam, Saudi Arabia - (DMM)Operational
  • APIOperational
  • Brasilia, Brazil - (BSB)Operational
  • Brussels, Belgium - (BRU)Operational
  • 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)Degraded performance
  • 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)Degraded performance
  • Haifa, Israel - (HFA)Operational
  • Sydney, NSW, Australia - (SYD)Degraded performance
  • 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)Operational
  • 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
  • Chittagong, Bangladesh - (CGP)Operational
  • Dallas, TX, United States - (DFW)Operational
  • Düsseldorf, Germany - (DUS)Operational
  • Kigali, Rwanda - (KGL)Operational
  • Manama, Bahrain - (BAH)Operational

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
462msp95 · latest
500ms250ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-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 420ms2026-09-24 UTC: p95 458ms2026-09-25 UTC: p95 412ms2026-09-26 UTC: p95 418ms2026-09-27 UTC: p95 422ms2026-09-28 UTC: p95 414ms2026-09-29 UTC: p95 440ms2026-09-30 UTC: p95 435ms2026-10-01 UTC: p95 357ms2026-10-02 UTC: p95 341ms2026-10-03 UTC: p95 309ms2026-10-04 UTC: p95 375ms2026-10-05 UTC: p95 459ms2026-10-06 UTC: p95 405ms2026-10-07 UTC: p95 440ms2026-10-08 UTC: p95 403ms2026-10-09 UTC: p95 385ms2026-10-10 UTC: p95 392ms2026-10-11 UTC: p95 385ms2026-10-12 UTC: p95 397ms2026-10-13 UTC: p95 453ms2026-10-14 UTC: p95 462ms
Sep 15Sep 29Oct 14
US-West
445msp95 · latest
500ms250ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-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 452ms2026-09-24 UTC: p95 463ms2026-09-25 UTC: p95 446ms2026-09-26 UTC: p95 401ms2026-09-27 UTC: p95 402ms2026-09-28 UTC: p95 431ms2026-09-29 UTC: p95 431ms2026-09-30 UTC: p95 311ms2026-10-01 UTC: p95 304ms2026-10-02 UTC: p95 235ms2026-10-03 UTC: p95 245ms2026-10-04 UTC: p95 354ms2026-10-05 UTC: p95 371ms2026-10-06 UTC: p95 377ms2026-10-07 UTC: p95 361ms2026-10-08 UTC: p95 470ms2026-10-09 UTC: p95 349ms2026-10-10 UTC: p95 388ms2026-10-11 UTC: p95 370ms2026-10-12 UTC: p95 394ms2026-10-13 UTC: p95 467ms2026-10-14 UTC: p95 445ms
Sep 15Sep 29Oct 14
Europe
211msp95 · 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-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 346ms2026-09-24 UTC: p95 365ms2026-09-25 UTC: p95 239ms2026-09-26 UTC: p95 269ms2026-09-27 UTC: p95 285ms2026-09-28 UTC: p95 273ms2026-09-29 UTC: p95 248ms2026-09-30 UTC: p95 276ms2026-10-01 UTC: p95 178ms2026-10-02 UTC: p95 154ms2026-10-03 UTC: p95 146ms2026-10-04 UTC: p95 227ms2026-10-05 UTC: p95 249ms2026-10-06 UTC: p95 213ms2026-10-07 UTC: p95 250ms2026-10-08 UTC: p95 252ms2026-10-09 UTC: p95 218ms2026-10-10 UTC: p95 234ms2026-10-11 UTC: p95 269ms2026-10-12 UTC: p95 283ms2026-10-13 UTC: p95 245ms2026-10-14 UTC: p95 211ms
Sep 15Sep 29Oct 14
Asia-Pacific
684msp95 · 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-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 483ms2026-09-24 UTC: p95 582ms2026-09-25 UTC: p95 422ms2026-09-26 UTC: p95 540ms2026-09-27 UTC: p95 527ms2026-09-28 UTC: p95 516ms2026-09-29 UTC: p95 509ms2026-09-30 UTC: p95 508ms2026-10-01 UTC: p95 343ms2026-10-02 UTC: p95 329ms2026-10-03 UTC: p95 374ms2026-10-04 UTC: p95 485ms2026-10-05 UTC: p95 448ms2026-10-06 UTC: p95 477ms2026-10-07 UTC: p95 605ms2026-10-08 UTC: p95 450ms2026-10-09 UTC: p95 500ms2026-10-10 UTC: p95 442ms2026-10-11 UTC: p95 336ms2026-10-12 UTC: p95 514ms2026-10-13 UTC: p95 527ms2026-10-14 UTC: p95 684ms
Sep 15Sep 29Oct 14
US-Central
566msp95 · 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-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 683ms2026-09-24 UTC: p95 871ms2026-09-25 UTC: p95 529ms2026-09-26 UTC: p95 534ms2026-09-27 UTC: p95 534ms2026-09-28 UTC: p95 590ms2026-09-29 UTC: p95 599ms2026-09-30 UTC: p95 401ms2026-10-01 UTC: p95 417ms2026-10-02 UTC: p95 463ms2026-10-03 UTC: p95 382ms2026-10-04 UTC: p95 484ms2026-10-05 UTC: p95 477ms2026-10-06 UTC: p95 508ms2026-10-07 UTC: p95 556ms2026-10-08 UTC: p95 535ms2026-10-09 UTC: p95 479ms2026-10-10 UTC: p95 469ms2026-10-11 UTC: p95 507ms2026-10-12 UTC: p95 457ms2026-10-13 UTC: p95 415ms2026-10-14 UTC: p95 566ms
Sep 15Sep 29Oct 14
Canada
500msp95 · 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-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 492ms2026-09-24 UTC: p95 611ms2026-09-25 UTC: p95 443ms2026-09-26 UTC: p95 501ms2026-09-27 UTC: p95 464ms2026-09-28 UTC: p95 494ms2026-09-29 UTC: p95 527ms2026-09-30 UTC: p95 574ms2026-10-01 UTC: p95 442ms2026-10-02 UTC: p95 351ms2026-10-03 UTC: p95 360ms2026-10-04 UTC: p95 435ms2026-10-05 UTC: p95 350ms2026-10-06 UTC: p95 594ms2026-10-07 UTC: p95 482ms2026-10-08 UTC: p95 509ms2026-10-09 UTC: p95 583ms2026-10-10 UTC: p95 452ms2026-10-11 UTC: p95 511ms2026-10-12 UTC: p95 459ms2026-10-13 UTC: p95 446ms2026-10-14 UTC: p95 500ms
Sep 15Sep 29Oct 14
UK
238msp95 · 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-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 323ms2026-09-24 UTC: p95 349ms2026-09-25 UTC: p95 464ms2026-09-26 UTC: p95 387ms2026-09-27 UTC: p95 329ms2026-09-28 UTC: p95 354ms2026-09-29 UTC: p95 278ms2026-09-30 UTC: p95 276ms2026-10-01 UTC: p95 337ms2026-10-02 UTC: p95 165ms2026-10-03 UTC: p95 193ms2026-10-04 UTC: p95 265ms2026-10-05 UTC: p95 263ms2026-10-06 UTC: p95 280ms2026-10-07 UTC: p95 280ms2026-10-08 UTC: p95 255ms2026-10-09 UTC: p95 266ms2026-10-10 UTC: p95 281ms2026-10-11 UTC: p95 287ms2026-10-12 UTC: p95 256ms2026-10-13 UTC: p95 253ms2026-10-14 UTC: p95 238ms
Sep 15Sep 29Oct 14
Southeast Asia
842msp95 · latest
1s500ms0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-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 966ms2026-09-24 UTC: p95 841ms2026-09-25 UTC: p95 788ms2026-09-26 UTC: p95 966ms2026-09-27 UTC: p95 887ms2026-09-28 UTC: p95 906ms2026-09-29 UTC: p95 774ms2026-09-30 UTC: p95 775ms2026-10-01 UTC: p95 468ms2026-10-02 UTC: p95 729ms2026-10-03 UTC: p95 572ms2026-10-04 UTC: p95 625ms2026-10-05 UTC: p95 546ms2026-10-06 UTC: p95 693ms2026-10-07 UTC: p95 676ms2026-10-08 UTC: p95 704ms2026-10-09 UTC: p95 717ms2026-10-10 UTC: p95 762ms2026-10-11 UTC: p95 578ms2026-10-12 UTC: p95 705ms2026-10-13 UTC: p95 788ms2026-10-14 UTC: p95 842ms
Sep 15Sep 29Oct 14
Australia
602msp95 · 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-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 598ms2026-09-24 UTC: p95 531ms2026-09-25 UTC: p95 689ms2026-09-26 UTC: p95 600ms2026-09-27 UTC: p95 763ms2026-09-28 UTC: p95 593ms2026-09-29 UTC: p95 390ms2026-09-30 UTC: p95 472ms2026-10-01 UTC: p95 526ms2026-10-02 UTC: p95 340ms2026-10-03 UTC: p95 505ms2026-10-04 UTC: p95 562ms2026-10-05 UTC: p95 661ms2026-10-06 UTC: p95 715ms2026-10-07 UTC: p95 538ms2026-10-08 UTC: p95 556ms2026-10-09 UTC: p95 656ms2026-10-10 UTC: p95 636ms2026-10-11 UTC: p95 529ms2026-10-12 UTC: p95 612ms2026-10-13 UTC: p95 773ms2026-10-14 UTC: p95 602ms
Sep 15Sep 29Oct 14
South America
577msp95 · 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-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 582ms2026-09-24 UTC: p95 752ms2026-09-25 UTC: p95 437ms2026-09-26 UTC: p95 560ms2026-09-27 UTC: p95 532ms2026-09-28 UTC: p95 607ms2026-09-29 UTC: p95 538ms2026-09-30 UTC: p95 564ms2026-10-01 UTC: p95 420ms2026-10-02 UTC: p95 377ms2026-10-03 UTC: p95 577ms2026-10-04 UTC: p95 688ms2026-10-05 UTC: p95 560ms2026-10-06 UTC: p95 757ms2026-10-07 UTC: p95 862ms2026-10-08 UTC: p95 567ms2026-10-09 UTC: p95 511ms2026-10-10 UTC: p95 706ms2026-10-11 UTC: p95 605ms2026-10-12 UTC: p95 598ms2026-10-13 UTC: p95 579ms2026-10-14 UTC: p95 577ms
Sep 15Sep 29Oct 14

Check your own site while you wait on Cloudflare

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • CDNUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Cloudflare reports an incident on its status page, and again when it reports it resolved.

Get an email when Cloudflare reports an incident

Email me when Cloudflare reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Cloudflare's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 256msstatus code: 200checked: Oct 14, 2026, 4:48 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
      Checks passinglatency: 99msstatus code: 200checked: Oct 14, 2026, 4:48 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
      Checks passinglatency: 63msstatus code: 200checked: Oct 14, 2026, 4:49 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
      Checks passinglatency: 236msstatus code: 200checked: Oct 14, 2026, 4:47 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
    Checks passinglatency: 42msstatus code: 200checked: Oct 14, 2026, 4:47 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 59msstatus code: 200checked: Oct 14, 2026, 4:48 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
      Checks passinglatency: 168msstatus code: 200checked: Oct 14, 2026, 4:46 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 43msstatus code: 200checked: Oct 14, 2026, 4:49 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
      Checks passinglatency: 54msstatus code: 200checked: Oct 14, 2026, 4:49 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
      Checks passinglatency: 332msstatus code: 200checked: Oct 14, 2026, 4:48 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 probe events

Elevated number of 5XX errors in PDXdeclared on their status page2026-10-14
Network Performance Issues in LAX, 2h 7mdeclared on their status page2026-10-13
Cloudflare Service Issues, 28mdeclared on their status page2026-10-13
Cloudflare Workers - Cron Trigger Activation Issues, 8h 51mdeclared on their status page2026-10-13
Audit Logs v2 ingestion is missing multiple Cloudflare products declared on their status page2026-10-13
Network performance issues in Ashburn, US (IAD), 10h 56mdeclared on their status page2026-10-13
Cloudflare Workers - Cron Trigger Activation Issues, 3h 11mdeclared on their status page2026-10-12
Cloudflare Network Performance Issues, 7h 28mdeclared on their status page2026-10-12

check 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 check readings and Cloudflare's own claim at the time, side by side.

Full check history for Cloudflare: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Put this badge in your README

Cloudflare uptime by RealUptime's checksLive, from this page's own readings.
[![Cloudflare uptime by RealUptime's checks](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 by RealUptime's checks"></a>

The badge shows the share of our checks that passed 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Cloudflare down?", https://realuptime.io/outages/cloudflare. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://api.cloudflare.com/client/v4/ips
secondary
https://www.cloudflare.com/
secondaryfunctional: live API
https://api.cloudflare.com/client/v4/user/tokens/verify
secondary
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.7.1/jquery.min.js

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: api.cloudflare.com

RealUptime is not affiliated with Cloudflare; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.