Is Cloudflare down right now?

No. Our checks are finding no problems with Cloudflare right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Cloudflare continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are website / app down, DNS / site unreachable, 5xx error pages, SSL / certificate errors, high latency and slow or laggy. Those are the options the report button offers for Cloudflare, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Cloudflare specifically, Cloudflare serves from hundreds of cities and you get whichever is nearest, so an unhealthy colocation affects you and nobody two cities away. Their error codes also separate the two sides: 520 through 524 usually mean the origin server behind Cloudflare, not Cloudflare. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Cloudflare, load a well-known site behind Cloudflare from another network or over mobile data. Failing from every network is the site or Cloudflare; failing only from yours points at the colocation you are routed to, which any site's /cdn-cgi/trace will name. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Cloudflare's side. Specifically: resist pausing Cloudflare on your domain. Pausing exposes your origin directly, changes DNS globally and takes time to propagate back, so you are frequently still broken after the incident has cleared. Development mode is the safer lever. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Cloudflare publishes a machine-readable status feed, so our first check reads it directly and reports what Cloudflare itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at www.cloudflarestatus.com, and it is linked further up this page. That is Cloudflare's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Cloudflare or cloudflare.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Cloudflare's own support, not us.