0

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

null
    • NextDNs
    • 3 yrs ago
    • Reported - view

    Please provide a https://nextdns.io/diag

      • bitpushr
      • 3 yrs ago
      • Reported - view

      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.

      • NextDNs
      • 3 yrs ago
      • Reported - view

      bitpushr can you please check again?

      • bitpushr
      • 3 yrs ago
      • Reported - view

      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 :)

    • entrepreneur, academic educator
    • Erwin
    • 3 yrs ago
    • Reported - view

    Also in Melbourne, I see the same this with some of my IPv6 pings...

    • entrepreneur, academic educator
    • Erwin
    • 3 yrs ago
    • Reported - view

    I think this issue could be caused by @AussieBroadBand. Their NOC is re-arranging IPv6 allocations to go live from Beta

    • entrepreneur, academic educator
    • Erwin
    • 3 yrs ago
    • Reported - view

    @nextdns please have a look: https://nextdns.io/diag/3ef90920-347c-11ec-8313-1dc40e9c9949

      • NextDNs
      • 3 yrs ago
      • Reported - view

      Erwin Boermans we're on it

    • Daniel_C.1
    • 3 yrs ago
    • Reported - view

    Attached results as well, in case this helps.

    NextDNS Results.txt
    • bitpushr
    • 3 yrs ago
    • Reported - view

    Another user in Western Australia is also seeing the same behaviour as above.
    https://whrl.pl/RglC1V

    • bitpushr
    • 3 yrs ago
    • Reported - view

    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.
     

    Screenshot 2021-10-26 220322
    • Zac_bitschkat
    • 3 yrs ago
    • Reported - view

    adding to this post, im in sydney and seeing similar to these guys. Anycast primary is going to melbourne.

    ndns results.txt
    • Zac_bitschkat
    • 3 yrs ago
    • Reported - view

    https://nextdns.io/diag/05aac1b0-7f2f-11ec-8a74-85fc32867507

    • bitpushr
    • 3 yrs ago
    • Reported - view

    @NextDNS

    I reached out to my ISP here:

    https://whrl.pl/Rgn6aJ

    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

Login to reply

Content aside

  • 3 yrs agoLast active
  • 14Replies
  • 233Views
  • 5 Following