StatOSS

Cloudflare uptime

Cloudflare, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.

api.cloudflare.com/client/v4/ipsEvery 5 minutes

Cloudflare is up.

Up for 51 d 10 h. Last checked 2026-11-20 18:52 UTC from Helsinki, Finland: 200 in 45 ms.

Last 24 hours

Up for 51 d 10 h100% passed

287 checks, median 32 ms from Helsinki, all passed

95% under 44 ms

Response time by region
EuropeEurope32 ms
N. AmericaNorth America41 ms
AsiaAsia55 ms
OceaniaOceania36 ms

Medians over this range, on one scale up to 100 ms.

Last 90 days

Up for 51 d 10 h100% passed

14,805 checks, median 35 ms from Helsinki, all passed

95% under 74 ms

Response time by region
EuropeEurope35 ms
N. AmericaNorth America50 ms
AsiaAsia56 ms
OceaniaOceania38 ms

Medians over this range, on one scale up to 100 ms. Europe's places are scaled to Helsinki, its fastest shared place.

Each bar of the first strip is one check, five minutes apart; each bar of the second is a day. Height is response time, red is a failed check, amber a timeout. Times are UTC, as of 2026-11-20 18:56 UTC.

In the last 30 days Cloudflare passed 8,862 of 8,862 checks, 100%.

No outage since checks began on 30 Sep 2026.

Availability

The share of checks that passed, and the outages that began, in each window up to now.

LastPassedChecksOutages
24 hours100%288 of 2880
7 days100%2,014 of 2,0140
30 days100%8,862 of 8,8620
90 daysNot enough history yet: checks began on 30 Sep 2026

A year of checks is kept; the year's figure appears here once there is a year of them.

Response time by location

Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.

FromMedian95th percentileMeanChecks
Falkenstein, Germany70 ms104 ms72 ms43
Helsinki, Finland32 ms47 ms34 ms420
Ashburn, USA43 ms72 ms47 ms503
Copenhagen, Denmark45 ms61 ms46 ms42
Singapore52 ms89 ms58 ms503
Sydney, Australia39 ms67 ms42 ms504

Outages

None detected since checks began on 30 Sep 2026.

What is checked

CDN, DNS, DDoS protection, Workers and a large part of the web's front doors. StatOSS itself sits behind it.

StatOSS sends GET https://api.cloudflare.com/client/v4/ips and counts the check as passed on status 200 within 10 seconds. The API endpoint that lists Cloudflare's IP ranges. It is public and needs no token, and it answers through the same API that dashboards, Terraform and wrangler use.

It checks Cloudflare's API. Sites behind Cloudflare go through its edge, which is a different path and can fail in one place while the API answers.

Cloudflare reports its own incidents at www.cloudflarestatus.com. The figures here are measured from outside and can differ from it in both directions.

How it is measured

  • One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
  • A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 200.
  • A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
  • Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
  • Availability is the share of checks that passed. There are no maintenance windows: every check counts.

It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.