1

I'm in Taiwan. Why do I use the server in Tokyo? All this makes my speed experience very bad.

13 replies

null
    • Hey
    • 1 yr ago
    • Reported - view

    You should upload a diag to show how exactly it connects to Tokyo instead of Taipei.

    https://help.nextdns.io/t/y4hmvcx/report-network-latency-issue

      • Morris
      • 1 yr ago
      • Reported - view

      Hey I filled in the ipv4 location directly on the router. How can I find this report?

      • Hey
      • 1 yr ago
      • Reported - view

      Morris if you download the Windows app or run the command from that post it takes a diag and uploads it to NextDNS.

      Think of it like using maps, there are multiple ways of reaching a destination and you can take different turns. Currently your internet is taking a bad route resulting in unwanted latency.

      By going to that forum post and running that tool, it shows exactly how you get routed to NextDNS servers so they can see what route it takes and how you get connected to Tokyo.

      When the diag completes it gives you the link to the uploaded version so you can reply to NextDNS with the info for them to diagnose your issue.

    • Morris
    • 1 yr ago
    • Reported - view

    This is my ding

     

    Testing IPv6 connectivity
      available: true
    Fetching https://test.nextdns.io
      status: ok
      client: 123.0.221.253
      protocol: UDP
      dest IP: 45.90.30.91
      server: imcloud-tpe-1
    Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
      anexia-tpe: 10.533ms
    Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
      imcloud-tpe: 13.37ms
    Fetching PoP name for anycast primary IPv4 (45.90.28.0)
      zepto-hkg: 26.486ms
    Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
      imcloud-tpe: 10.964ms
    Fetching PoP name for ultra low latency primary IPv6 (ipv6.dns1.nextdns.io)
    Fetch error: Get "https://dns.nextdns.io/info": dial tcp: lookup ipv6.dns1.nextdns.io on 127.0.0.1:53: no such host
    Fetching PoP name for ultra low latency secondary IPv6 (ipv6.dns2.nextdns.io)
    Fetch error: Get "https://dns.nextdns.io/info": dial tcp: lookup ipv6.dns2.nextdns.io on 127.0.0.1:53: no such host
    Fetching PoP name for anycast primary IPv6 (2a07:a8c0::)
      zepto-hkg: 26.815ms
    Fetching PoP name for anycast secondary IPv6 (2a07:a8c1::)
      vultr-tyo: 44.001ms
    Pinging PoPs
      anexia-tpe (IPv6): 10.529ms
      anexia-tpe: 14.404ms
      imcloud-tpe: 14.368ms
      zepto-hkg (IPv6): 27.088ms
      anexia-hkg: 26.835ms
      zepto-hkg: 31.443ms
      zepto-tyo: 41.54ms
      anexia-hkg (IPv6): 62.308ms
      starry-osa: 65.084ms
      starry-osa (IPv6): 69.386ms
      vultr-sel (IPv6): 73.502ms
      vultr-sel: 73.43ms
      greencloud-han: 82.146ms
      zepto-sel: 98.909ms
      anexia-han: 123.001ms
      zepto-tyo (IPv6): 150.172ms
      greencloud-han (IPv6): 186.69ms
    Traceroute for ultra low latency primary IPv4 (37.252.243.39)
     

      • NextDNs
      • 1 yr ago
      • Reported - view

      Morris please submit the diag and provide the create URL

      • Morris
      • 1 yr ago
      • Reported - view

      NextDNS Excuse me, what should I do?

      • NextDNs
      • 1 yr ago
      • Reported - view

      Morris let the diag command complete, once done it will ask you if you want to submit it. Say yes and copy paste the returned URL here.

      • Morris
      • 1 yr ago
      • Reported - view

      NextDNS Understand

      • Morris
      • 1 yr ago
      • Reported - view

      Morris My state has been stopped here.

      • NextDNs
      • 1 yr ago
      • Reported - view

      Morris can you please manually traceroute this IP?

      • Morris
      • 1 yr ago
      • Reported - view

      NextDNS May I ask how to do it? I don't know how to operate this. Thank you.

      • Morris
      • 1 yr ago
      • Reported - view
    • Morris
    • 1 yr ago
    • Reported - view

Content aside

  • 1 Likes
  • 1 yr agoLast active
  • 13Replies
  • 340Views
  • 3 Following