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