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.
14 replies
-
Please provide a https://nextdns.io/diag
-
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
-
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.
-
adding to this post, im in sydney and seeing similar to these guys. Anycast primary is going to melbourne.
-
@NextDNS
I reached out to my ISP here:
And they're requesting a BGP or Traceroute from your side to theirs (Aussie Broadband) r.e very high secondary IPv6 latency.
I've done an updated Network Diagnostic here:https://nextdns.io/diag/c6d00890-7f26-11ec-8a74-85fc32867507
Content aside
- 2 yrs agoLast active
- 14Replies
- 233Views
-
5
Following