Higher than normal ping to NextDNS instance
Hey guys,
Lately, I've noticed increased latency to my local NextDNS instance. Traceroute here:
https://pastebin.com/ztbXhg5T
It seems that no longer is NextDNS going to what was previously my local instance (Melbourne, Australia) but is now instead going to Sydney, Australia.
Did NextDNS remove its Melbourne instances? I've checked with a friend on a separate ISP in Australia and they also resolve to Sydney, whereas if we both ping Cloudflare's 1.1.1.1 we get 3ms (as we used to with NextDNS) to Melbourne.
Cheers.
-
Please provide a https://nextdns.io/diag
-
NextDNS https://nextdns.io/diag/0db473f0-3282-11ec-9959-4f6d345e53c6
I can see presence in Melbourne in the logs, but it looks like the IP of my particular instance is going to Sydney instead of Melbourne for some reason?
Happy to contact my ISP if needed; they're very helpful with regards to trace/routing issues.
-
bitpushr can you please check again?
-
NextDNS Looks like it's fixed now! Thanks :)
I'm still seeing higher latency for ultra-low latency IPv6 though. I've attacked another diag here:
https://nextdns.io/diag/029bc170-33d7-11ec-809f-05a30a1c564d
It's fixed for IPv4 though -- much thanks for that :)
-
-
Also in Melbourne, I see the same this with some of my IPv6 pings...
-
I think this issue could be caused by @AussieBroadBand. Their NOC is re-arranging IPv6 allocations to go live from Beta
-
@nextdns please have a look: https://nextdns.io/diag/3ef90920-347c-11ec-8313-1dc40e9c9949
-
Erwin Boermans we're on it
-
-
Attached results as well, in case this helps.
-
Another user in Western Australia is also seeing the same behaviour as above.
https://whrl.pl/RglC1V -
Just wanted to update this. After some routing changes from my ISP I'm no longer seeing increased ping/response times. Looks like all is good hopefully if we can get some validation from other users here in the thread.
