# Cloudflare status

> Is Cloudflare down? Live status, uptime history, and per-region response times, measured by our own probes since August 2026.

Published: 2026-08-17 | Canonical: https://yoping.me/status/cloudflare

## How we check Cloudflare

We watch cdn-cgi/trace from all five of our probe regions, every 2 minutes. A region that sees a failure does not make this page say "down" on its own: a second region has to agree first, the same confirmation rule every YoPingMe monitor uses.

Every zone behind Cloudflare answers requests to /cdn-cgi/trace from Cloudflare's own edge, so it is a real, live signal that Cloudflare's network is routing traffic correctly, rather than a guess at which of Cloudflare's many products (DNS, CDN, WAF, Workers) happens to be reachable at any given moment.

The live board - the current verdict, 24-hour, 7-day, and 30-day uptime, and per-region response times - is on the HTML page at https://yoping.me/status/cloudflare. Those numbers change too fast to repeat honestly in a static mirror, so where an answer below says "the board above", it means that page.

## What is Cloudflare?

Cloudflare sits in front of a large share of the web as a combined content
delivery network, DNS provider, and security layer. A site behind
Cloudflare has its DNS records point at Cloudflare's edge, and every
visitor's request is answered from the nearest of Cloudflare's data
centers before, in many cases, ever reaching the site's actual server.
That is what makes Cloudflare fast for visitors and resilient against
traffic spikes and attacks, and it is also what makes a Cloudflare
incident unusually far-reaching: a problem at Cloudflare's edge does not
degrade one company's product, it can affect every site and API that
routes through the affected part of Cloudflare's network at the same
time.

For a site owner, an edge-level Cloudflare incident tends to look
different from an ordinary outage. DNS lookups can start failing before
anything else does, since that is often the very first hop. A site can go
fully unreachable even though its own origin server is running perfectly
fine, because nothing ever gets past Cloudflare's edge to reach it. Or,
in a narrower incident, one geography loses connectivity while everywhere
else stays completely normal, which is exactly the kind of failure a
single-region monitor cannot see and a multi-region one exists to catch.

Cloudflare's edge is also often the reason a site can look healthy from
one place and broken from another at the exact same moment. A regional
routing issue, a stale DNS answer cached somewhere between a visitor and
Cloudflare, or an isolated data center problem can each produce a split
where some visitors load the site instantly and others get nothing at
all. That split is worth telling apart from a real full outage before
you start debugging your own server, and checking from more than one
region, the way the board above does, is the fastest way to tell them
apart.

Because Cloudflare fronts so much of the internet, its own incidents tend
to draw immediate, wide attention, and its team is generally quick to
post updates once something is confirmed. Our board here is not a
replacement for that, it is a second, independently measured line of
sight into the same infrastructure, running on the same 2-minute schedule
regardless of when an official update lands.

## Frequently asked questions

### Is Cloudflare down right now?

Check the board above; it reflects our own probes against Cloudflare's edge network, refreshed every couple of minutes from all five of our regions.

### What happens to my site if Cloudflare goes down?

If your site sits fully behind Cloudflare, DNS resolution, the CDN cache, and any Cloudflare-side security rules stop working together, which usually means your entire site becomes unreachable rather than just slow, since Cloudflare is the first hop every visitor's request makes.

### My site is up on YoPingMe but visitors say it is down. Could this still be Cloudflare?

Yes. A regional edge issue can affect visitors in one part of the world while our probes in other regions see a healthy response, and a browser-side DNS cache can also keep serving a stale answer for minutes after an edge location recovers. Compare the per-region readings above rather than a single overall verdict.

### Does this page check every Cloudflare product?

No. It checks whether the core edge network is routing and answering requests, which is the layer nearly every Cloudflare-fronted site depends on. It does not separately verify Workers, R2, or any other individual product staying healthy on its own.