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