Operational
No, CentralNic DNS is up.
All 4 nameservers we check answered in the latest sweep.
- 30-day uptime
- 100%
- Rank
- #23 of 61
- Median response
- 8 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 centralnic.com, a zone CentralNic serves authoritatively, once a minute.
| Nameserver | Status | Address | Latest | 24 h uptime |
|---|---|---|---|---|
| ns1.rrpproxy.net | Operational | 193.227.117.226 | 8 ms | 100% |
| ns2.rrpproxy.net | Operational | 194.50.187.226 | 7 ms | 100% |
| ns3.rrpproxy.net | Operational | 194.0.182.226 | 7 ms | 100% |
| ns4.rrpproxy.net | Operational | 194.0.182.226 | 8 ms | 100% |
Through public resolvers
Every minute each resolver is asked for a random name under centralnic.com, so it can't answer from cache and has to reach CentralNic from its own network. If most of them still resolve the zone, CentralNic isn't marked down even when our own checks fail.
| Resolver | Status | Latest | 24 h success |
|---|---|---|---|
| Cloudflare | Resolves | 6 ms | 100% |
| Google Public DNS | Resolves | 18 ms | 100% |
| Quad9 | Resolves | 53 ms | 100% |
| OpenDNS | Resolves | 28 ms | 100% |
| AdGuard DNS | Resolves | 61 ms | 100% |
| Control D | Fails | — | 0.00% |
Incident history
Incidents we measured in the last 30 days. CentralNic's own status page is the authority on what happened.
No incidents measured for CentralNic in the last 30 days.
Thinking of leaving CentralNic?