Operational
No, Route 53 DNS is up.
All 4 nameservers we check answered in the latest sweep.
- 30-day uptime
- 100%
- Rank
- #17 of 61
- Median response
- 7 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 netflix.com, a zone Route 53 serves authoritatively, once a minute.
| Nameserver | Status | Address | Latest | 24 h uptime |
|---|---|---|---|---|
| ns-1372.awsdns-43.org | Operational | 205.251.197.92 | 13 ms | 100% |
| ns-1984.awsdns-56.co.uk | Operational | 205.251.199.192 | 1 ms | 100% |
| ns-659.awsdns-18.net | Operational | 205.251.194.147 | 14 ms | 100% |
| ns-81.awsdns-10.com | Operational | 205.251.192.81 | 1 ms | 100% |
Through public resolvers
Every minute each resolver is asked for a random name under netflix.com, so it can't answer from cache and has to reach Route 53 from its own network. If most of them still resolve the zone, Route 53 isn't marked down even when our own checks fail.
| Resolver | Status | Latest | 24 h success |
|---|---|---|---|
| Cloudflare | Resolves | 4 ms | 100% |
| Google Public DNS | Resolves | 6 ms | 100% |
| Quad9 | Resolves | 3 ms | 100% |
| OpenDNS | Resolves | 4 ms | 100% |
| AdGuard DNS | Resolves | 31 ms | 100% |
| Control D | Fails | — | 0.00% |
Incident history
Incidents we measured in the last 30 days. Route 53's own status page is the authority on what happened.
No incidents measured for Route 53 in the last 30 days.
Thinking of leaving Route 53?