Is Cloudflare DNS down right now?

No. Our checks are finding no problems with Cloudflare DNS right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Cloudflare DNS 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 DNS / site unreachable, can't connect, no response / timing out, website / app down, high latency and slow or laggy. Those are the options the report button offers for Cloudflare DNS, 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 DNS specifically, 1.1.1.1 is an anycast address answered from hundreds of locations, so you reach the nearest one and an unhealthy location affects only the people routed to it. Plenty of provider, hotel and captive portal networks also block or hijack 1.1.1.1 specifically. 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 DNS, query a different resolver and compare, for example dig @8.8.8.8 example.com. Another resolver answering while 1.1.1.1 does not is your route to 1.1.1.1 rather than DNS in general. https://1.1.1.1/help reports whether you reached Cloudflare's resolver at all. 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 DNS's side. Specifically: switch resolver rather than waiting it out. DNS has no graceful degradation, so every application breaks at once, and switching back later costs nothing. Names already cached keep resolving until they expire. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Cloudflare DNS publishes a machine-readable status feed, so our first check reads it directly and reports what Cloudflare DNS 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 DNS'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 DNS or 1.1.1.1. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Cloudflare DNS's own support, not us.