Errors from multiple -FRA nodes in Germany
Starting yesterday I'm getting errors from all of the Frankfurt (-fra) servers. It's intermittent and clears up after a couple seconds/minutes but happens again later:
^note the 2 errors at the bottom, these are usually 11ms ping, too
When this happened I ran a sh -c 'sh -c "$(curl -s https://nextdns.io/diag)"' but it stopped half-way through, I guess the diagnostic is affected by this problem, too.
I was connected to one of the servers that errored out earlier and with no DNS everything stopped working until the NDNS app switched to a different server.
Please advise.
9 replies
-
Seems like an IPv6 related issue. If you ping other IPv6 resources (like 2001:4860:4860::8888), do you get errors as well when this happen?
-
NextDNS Thanks for your reply.
In true InterNet-bug-reporting-fashion the issue disappeared the minute I reported it here. :-]I'll follow up if it shows again. Cheers.
-
Valynor IPv6 weirdness :)
-
NextDNS It happened again while browsing the web, couldn't reach any sites for 20 seconds. This time it was IPv4 and v6.
Ping was working -
Anexia was just erroring out again and I started another diagnostic but it's freezing half-way through:
Do you want to continue? (press enter to accept) Password: Resolvers: 192.168.178.1 Testing IPv6 connectivity available: true Fetching https://test.nextdns.io status: unconfigured client: 2003:e6:9712:a500:c03c:4b6e:97f1:46f3 resolver: 74.63.24.240 Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io) vultr-fra: 21.314ms Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io) zepto-fra: 15.176ms Fetching PoP name for anycast primary IPv4 (45.90.28.0) zepto-fra: 14.306ms Fetching PoP name for anycast secondary IPv4 (45.90.30.0) vultr-fra: 19.406ms Fetching PoP name for ultra low latency primary IPv6 (ipv6.dns1.nextdns.io) vultr-fra: 15.004ms Fetching PoP name for ultra low latency secondary IPv6 (ipv6.dns2.nextdns.io) zepto-fra: 13.325ms Fetching PoP name for anycast primary IPv6 (2a07:a8c0::) zepto-fra: 14.563ms Fetching PoP name for anycast secondary IPv6 (2a07:a8c1::) vultr-fra: 14.56ms Pinging PoPs vultr-fra (IPv6): 16.261ms vultr-fra: 19.284ms zepto-fra: 18.969ms anexia-zrh: 25.538ms hetzner-nue: 24.769ms exoscale-muc: 26.546ms hetzner-nue (IPv6): 20.005ms zepto-fra (IPv6): 20.537ms exoscale-muc (IPv6): 35.783ms anexia-zrh (IPv6): 36.848ms anexia-muc: 36.815ms zepto-zrh: 48.459ms anexia-lux: 51.563ms fusa-bru (IPv6): 57.096ms anexia-muc (IPv6): 51.516ms zepto-zrh (IPv6): 50.793ms fusa-bru: 51.532ms anexia-lux (IPv6): 79.708ms anexia-fra (IPv6): 16.527ms anexia-fra: 15.501ms Traceroute for ultra low latency primary IPv4 (199.247.16.158) 1 192.168.178.1 3ms 1ms 2ms 2 62.155.246.176 10ms 9ms 9ms 3 217.5.109.74 16ms 13ms 21ms 4 217.5.109.74 14ms 13ms 13ms 5 80.157.204.62 19ms 20ms 18ms 6 89.149.137.14 19ms 18ms 17ms 7 46.33.81.30 17ms 17ms 18ms
-
-
Please traceroute 217.146.22.163
-
NextDNS
I CTRL-C'd out after 35 hops as there's clearly something wrong here:
traceroute to 217.146.22.163 (217.146.22.163), 64 hops max, 52 byte packets 1 192.168.178.1 (192.168.178.1) 1.551 ms 1.328 ms 0.770 ms 2 p3e9bf6b0.dip0.t-ipconnect.de (62.155.246.176) 7.931 ms 9.251 ms 8.943 ms 3 217.0.200.238 (217.0.200.238) 11.713 ms 11.434 ms 11.059 ms 4 80.156.161.186 (80.156.161.186) 10.870 ms 73.228 ms 28.987 ms 5 ae0-0.bbr01.anx25.fra.de.anexia-it.net (144.208.208.143) 19.476 ms 11.892 ms 11.971 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * 31 * * * 32 * * * 33 * * * 34 * * * 35 *^C
Content aside
- 1 yr agoLast active
- 9Replies
- 88Views
-
3
Following