Operational
No, Cloudflare DNS is up.
All 4 nameservers we check answered in the latest sweep.
- 30-day uptime
- 100%
- Rank
- #8 of 61
- Median response
- 3 ms
- Incidents, 30 days
- 0
Uptime, last 30 days
- ≥ 99.9%
- ≥ 99%
- < 99%
- No data
30 days ago100% uptime · no downtimeToday
Nameservers we check
Each one gets a direct SOA query for cloudflare.com, a zone Cloudflare serves authoritatively, once a minute.
| Nameserver | Status | Address | Latest | 24 h uptime |
|---|---|---|---|---|
| ns3.cloudflare.com | Operational | 162.159.0.33 | 2 ms | 100% |
| ns4.cloudflare.com | Operational | 162.159.1.33 | 2 ms | 100% |
| ns5.cloudflare.com | Operational | 162.159.2.9 | 2 ms | 100% |
| ns6.cloudflare.com | Operational | 162.159.3.11 | 2 ms | 100% |
Through public resolvers
Every minute each resolver is asked for a random name under cloudflare.com, so it can't answer from cache and has to reach Cloudflare from its own network. If most of them still resolve the zone, Cloudflare isn't marked down even when our own checks fail.
| Resolver | Status | Latest | 24 h success |
|---|---|---|---|
| Cloudflare | Resolves | 5 ms | 100% |
| Google Public DNS | Resolves | 13 ms | 100% |
| Quad9 | Resolves | 7 ms | 100% |
| OpenDNS | Resolves | 6 ms | 100% |
| AdGuard DNS | Resolves | 27 ms | 100% |
| Control D | Fails | — | 0.00% |
Incident history
Incidents we measured in the last 30 days. Cloudflare's own status page is the authority on what happened.
No incidents measured for Cloudflare in the last 30 days.
Thinking of leaving Cloudflare?