CheckUpstream measured Cloudflare at 100.000% availability across 2824 independent checks (global · api). 372 incidents were recorded in the past 12 months; the most recent resolved earlier today after 2 hours. Status signals are polled from Cloudflare's official status feed, alongside independent probes and community reports. Cloudflare publishes 1 product-level SLA uptime commitment (up to 100%), and service credits must be claimed within 0 days of a breach.
180 days measured availability how this is computed
100.000%
global · api · n=2824 · p95 698ms (30d)
Share of our own checks against Cloudflare endpoints that returned Cloudflare's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 363 incidents · 25 of 180 days with none posted · 43d 22h of declared impact
Fewer incidents in the last 30 days than 1% of 232 tracked services.
Share of each window with no impact declared by Cloudflare
7d
77.703%
30d
76.008%
90d
75.393%
180d
75.591%
1y
87.963%
Downtime like this can be refundable
If you're a paying Cloudflare customer, outages in these windows may count against Cloudflare's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Cloudflare entitlement →Does Cloudflare actually matter to you?
A Cloudflare outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Predicted resolution
n=344~194m (p25 86m – p75 548m)
Based on 344 historical Minor incidents · currently 6469m elapsed.
From 361 incidents Cloudflare published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long Cloudflare takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Excluded: 2 still open.
Aug 31, 20:16 UTC · resolved in 1h 53m · Resolved
Aug 31, 18:47 UTC · in progress · Investigating
Aug 31, 11:40 UTC · resolved in 3h 20m · Resolved
1signal across 1 source
HN 1
Live Cloudflare status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/cloudflare)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Cloudflare is currently Degraded. CheckUpstream tracks Cloudflare in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Cloudflare down" view? See the Cloudflare Live status page.
Aug 31, 11:40 UTC · resolved in 9m · Resolved
Aug 27, 14:40 UTC · resolved in 9m · Resolved
Aug 26, 20:08 UTC · resolved in 12h 33m · Resolved
Aug 26, 14:59 UTC · resolved in 5h 11m · Resolved
Aug 24, 20:38 UTC · resolved in 1d · Resolved
Aug 24, 05:47 UTC · resolved in 1h 12m · Resolved
Aug 24, 03:53 UTC · resolved in 16h 46m · Resolved
Aug 22, 02:31 UTC · resolved in 2d 1h · Resolved
Aug 21, 20:43 UTC · resolved in 5h 56m · Resolved
Aug 21, 14:59 UTC · resolved in 2h 45m · Resolved
Aug 21, 07:31 UTC · resolved in 18m · Resolved
Aug 21, 06:40 UTC · resolved in 8h 19m · Resolved
Cloudflare's last resolved incident started earlier today and lasted 1h 53m (degraded performance).
Cloudflare's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Cloudflare endpoints. It is the share of checks that returned the expected response, not a figure taken from Cloudflare's status page.
Sign up to CheckUpstream and add Cloudflare to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Cloudflare's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.