Recursive DNS in AMS returning SERVFAIL for some zones
Network — transit & peering — AMS
Timeline
-
Resolved
Both resolvers in AMS have answered every query cleanly for 15 minutes. Duration: 22 minutes.
-
Identified
One of the two resolvers has a corrupted DNSSEC trust anchor after an automatic update. We have taken it out of rotation; the second resolver is handling all queries.
-
Investigating
The recursive resolvers we provide to machines in AMS are returning SERVFAIL for a subset of zones since 13:12 UTC. Machines configured with their own resolvers are not affected.
Times are shown in your time zone ().
Related pages
- Service statusLive status of every gpuserver.io component and data centre, probed every 60 seconds from five cities, with 90-day uptime and the incident log since 2022.
- Incident historyEvery incident and maintenance window on gpuserver.io since monitoring began in September 2022, month by month, with its timeline and post-incident review.
- Service level agreementThe 99.9% commitment: what counts as downtime, how it is measured from outside, five minutes of term back per minute lost, and the exclusions in full.
- NetworkUnmetered ports up to 25 Gbit/s, two carriers and an IX per site, always-on DDoS filtering, routed IPv6 — and the four things we do not offer, stated up front.