All 61 providers answering
Which DNS provider stays up.
We query the authoritative nameservers of 61 DNS providers every minute and publish what comes back: live status, 30-day uptime, latency and every outage.
Uptime leaderboard
Ranked by the share of nameserver checks that got a correct answer over the last 30 days. Ties go to fewer incidents, then lower latency.
| # | Provider | 30-day uptime | Downtime | Median | p95 | Incidents |
|---|---|---|---|---|---|---|
| 1 | GoDaddy | 100% | 1 ms | 0 | ||
| 2 | Gcore | 100% | 2 ms | 0 | ||
| 3 | Hurricane Electric | 100% | 2 ms | 0 | ||
| 4 | Linode | 100% | 2 ms | 0 | ||
| 5 | NS1 | 100% | 2 ms | 0 | ||
| 6 | Oracle Cloud | 100% | 2 ms | 0 | ||
| 7 | Vercel | 100% | 2 ms | 0 | ||
| 8 | Cloudflare | 100% | 3 ms | 0 | ||
| 9 | Bunny | 100% | 3 ms | 0 | ||
| 10 | Porkbun | 100% | 3 ms | 0 |
Every provider, right now
Current status from the latest sweep, with one bar per day. Hover a bar for that day's numbers, or open a provider for its nameservers.
Showing 15 of 61 providers
- ≥ 99.9%
- ≥ 99%
- < 99%
- No data
Thirty days in numbers
Downtime is counted in nameserver-minutes: one nameserver failing for ten minutes adds ten.
Aug 31Today
- Most reliable
- GoDaddy
- 100% uptime
- Fastest median
- GoDaddy
- 1 ms
- Longest incident
- None
- Nothing in 30 days
- Incidents recorded
- 0
- Across 30 days
| Provider | Range | Median |
|---|---|---|
| GoDaddy | 1 ms | |
| Gcore | 2 ms | |
| Hurricane Electric | 2 ms | |
| Linode | 2 ms | |
| NS1 | 2 ms | |
| Oracle Cloud | 2 ms | |
| Vercel | 2 ms | |
| Cloudflare | 3 ms | |
| Bunny | 3 ms | |
| Porkbun | 3 ms | |
| Akamai | 4 ms | |
| Openprovider | 4 ms |
Joker
SoftLayer
- None
- 1–5 min
- 6–30 min
- 31–120 min
- > 2 h
Recent incidents
An incident opens after two failing sweeps in a row and closes after three clean ones.
No incidents in the last 30 days.
How we measure
- What we query
- An SOA query for a zone each provider serves authoritatively, sent straight to up to four of its nameservers. No recursion, no caching resolver in between. Every target is verified before we monitor it: the zone is delegated to the provider, or its nameservers answer for it with authority and refuse a zone they don't host.
- What counts as up
- An authoritative NOERROR answer within 2 seconds. Timeouts, SERVFAIL, REFUSED and non-authoritative answers count as failures. Answers slower than 1 second count as up but slow. A failed query is retried once before it counts.
- Where we measure from
- Right now one location probes every nameserver each minute. When more locations report, a check only fails when most of them saw it fail.
- Through public resolvers
- Each minute we also ask Cloudflare, Google, Quad9, OpenDNS, AdGuard and Control D for a random name under every provider's zone. The random label defeats caching, so each resolver has to reach the provider from its own network. A provider is only marked down when most resolvers fail too.
- Protecting against our own outages
- Each sweep also queries root and .com servers. If those fail, or more than 40% of providers fail at once, the problem is on our side and the sweep is discarded. If every nameserver of a provider refuses its zone, the zone moved rather than the provider failing, so that provider is skipped until its target is refreshed.
- Status
- Operational means every nameserver answered. Degraded means at least one failed or was slow. Down means none answered.
Is this an official status page for these providers?
No. DNSMigrator is not affiliated with any provider listed here. These are independent measurements from our network; each provider's own status page is the authority on their incidents.
Why does a provider show downtime its status page doesn't mention?
We measure individual nameservers. A single anycast node or network path can fail for our locations while resolvers elsewhere never notice, because they retry another nameserver.
Does degraded mean my domains stopped resolving?
Usually not. Resolvers try the next nameserver when one fails, so a partial outage mostly adds latency. Down means every nameserver we check stopped answering.
How long is data kept?
Raw checks for 48 hours, hourly rollups for 35 days, and incidents for 90 days.
Why isn't my provider listed?
We monitor providers with fixed public nameservers. Self-hosted servers such as PowerDNS or BIND, and file-based sources, have no shared nameservers to check.
Moving to a more reliable provider?