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