Cloudflare status · Cloud & Infrastructure · checked (24s ago)
Degraded
Partly — Cloudflare is up but running slower than usual (Minor Service Outage).
According to Cloudflare's official status page, Cloudflare was reporting “Minor Service Outage” when isuptime last checked at . Over the last 30 days, Cloudflare's feed reported no outage in 100.00% of our checks.
No outage reported (30d)
100.00%
Share of our checks where Cloudflare's feed reported no outage. Degraded counts as no-outage. Not an SLA.
Response time
4.64 s
How long the last status check took
Reported by
Degraded
Minor Service Outage
What to do while Cloudflare is down
isuptime cannot fix Cloudflare, and neither can you. These are the things that are actually worth doing until it comes back.
Stop retrying in a loop. If your code calls Cloudflare, back off exponentially and cap the retries. A retry storm from every client at once is a large part of why outages take as long to clear as they do, and it will exhaust your own quota before the service returns.
Get told when it clears, instead of refreshing. The bell in the header sets up a browser notification, or a Discord, Slack or Telegram webhook, for the moment Cloudflare's status changes.
Move the urgent work elsewhere. Only worth it for something that cannot wait — check the substitute is up first.
Everything above is read from Cloudflare's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Cloudflare in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
What Cloudflare is
Cloudflare sits in front of a large share of the web as a CDN, DNS provider, DDoS filter and WAF, and also runs Workers, R2, Pages, Zero Trust and the 1.1.1.1 resolver. Because it is in the request path for so many other sites, a real Cloudflare incident is felt across services that have nothing to do with each other.
What Cloudflare's status feed covers
Cloudflare's status page is unusual: alongside its product components it lists hundreds of individual edge locations, each reporting its own status. There is almost always some point of presence in maintenance or re-routing, so the aggregate indicator sits amber far more often than Cloudflare is actually impaired — an anycast network routing around a dead location in Guam or Arica is the design working, not an outage. isuptime weighs the aggregate indicator against how many components are actually affected and whether Cloudflare has an incident open, so a handful of edge locations does not get reported as “Cloudflare is down”.
One bar per day. Each shows the share of that day's checks where Cloudflare's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Cloudflare was down.
2026-08-2530 of 30 days recordedToday
No outage reported (99%+)
95–99%
80–95%
Under 80%
No data
Other services reporting problems right now
8 other services isuptime tracks were also reporting a problem as of the same check, 24s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Cloudflare's status endpoint.
Which Cloudflare features are affected?
Africa — partial_outage
Annaba, Algeria - (AAE) — partial_outage
Arica, Chile - (ARI) — partial_outage
Asia — partial_outage
Brisbane, QLD, Australia - (BNE) — partial_outage
Buffalo, NY, United States - (BUF) — partial_outage
Canberra, ACT, Australia - (CBR) — partial_outage
Christchurch, New Zealand - (CHC) — partial_outage
Cloudflare outage history
Cloudflare has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Cloudflare posted itself — not every problem users hit.
Partly — Cloudflare is up but running slower than usual (Minor Service Outage). Checked (24s ago).
What is Cloudflare's status right now?
Cloudflare is reporting “Minor Service Outage” on its official status page — Degraded — as of . That status feed answered our last check in 4.64 s. isuptime reads this from Cloudflare's own published feed and does not test Cloudflare independently.
When did Cloudflare last go down?
The most recent incident Cloudflare published was “Elevated Errors with any / all in http_response_cache_settings”, opened Sep 23, 03:54 PM UTC (1h ago), and still open. That is the latest entry in Cloudflare's own incident feed, not every problem users experienced.
What is Cloudflare's uptime?
isuptime does not measure Cloudflare's uptime directly — it reads Cloudflare's own published status feed. Over the last 30 days, Cloudflare's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
Is it just me, or is Cloudflare down for everyone?
Cloudflare is reporting a problem on its own status page, so this is affecting other users too, not just you.
Cloudflare says operational but it is not working for me
Errors on a Cloudflare-fronted site are usually about the origin, not Cloudflare: a 521, 522 or 523 means Cloudflare could not reach the server behind it, which is the site owner's problem. A 1020 is a firewall rule blocking you. If DNS resolution is failing generally, test against a different resolver before blaming 1.1.1.1 — the resolver and the CDN are separate systems with separate failure modes.
