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