1

Not using the closest server

I've run already the diag quite a few times from my router but it is no resolved

anexia-sof-1.edge.nextdns.io

is used which is quite slow from a network distance perspective regardless if it is close from a geographical perspective

results from ping

  serverwala-buh (IPv4)   32 ms

■ anexia-ams (IPv6)       47 ms  (secondary)

  exoscale-vie (IPv6)     48 ms

■ anexia-lon (IPv4)       53 ms  (secondary)

■ zepto-lon (IPv4)        54 ms  (primary)

■ zepto-fra (IPv6)        55 ms  (primary)

  anexia-vie (IPv4)       62 ms

  estnoc-buh (IPv4)       62 ms

  exoscale-vie (IPv4)     64 ms

  serverwala-buh (IPv6)   67 ms

  serverwala-mil (IPv4)   68 ms

  anexia-vie (IPv6)       70 ms

  edgeuno-ist (IPv6)      83 ms

  edgeuno-ist (IPv4)      85 ms

  zepto-sof (IPv4)        89 ms

  premiumrdp-ist (IPv4)   95 ms

  anexia-sof (IPv6)       98 ms

  anexia-sof (IPv4)       98 ms

  citynet-cai (IPv4)     102 ms

 

diag report here: https://nextdns.io/diag/3dfa7a90-50cf-11eb-9bcc-51da18bb30ac

27 replies

null
    • G_B
    • 3 yrs ago
    • Reported - view

    Any updates ?

    • G_B
    • 3 yrs ago
    • Reported - view

    ultralow definition is really funny here

    serverwala-buh           42 ms

      exoscale-vie (IPv6)      57 ms

      zepto-fra (IPv6)         58 ms  (anycast1)

      anexia-lon               62 ms  (anycast2)

      serverwala-buh (IPv6)    65 ms

      anexia-ams (IPv6)        68 ms  (anycast2)

      zepto-lon                71 ms  (anycast1)

      estnoc-buh               71 ms

      edgeuno-ist (IPv6)       82 ms

      zepto-mil (IPv6)         84 ms

      anexia-vie (IPv6)        98 ms

      zepto-mil               104 ms

      anexia-vie              107 ms

      edgeuno-ist             110 ms

      anexia-sof (IPv6)       122 ms  (ultralow1)

    ■ anexia-sof              125 ms  (ultralow1)

      citynet-cai             128 ms

      zepto-sof               142 ms  (ultralow2)

      premiumrdp-ist          246 ms

      exoscale-vie            255 ms

    dns2.nextdns.io (IPv6) error (ultralow2)

     

    Olivier Poitrey any actions coming?

      • olivier
      • 3 yrs ago
      • Reported - view

      G B please run a https://nextdns.io/diag

      • G_B
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey the link for the diag is there in my first post already

      • olivier
      • 3 yrs ago
      • Reported - view

      G B things changed in 9 days. Can you please performed a new one?

      • G_B
      • 3 yrs ago
      • Reported - view
      • G_B
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey any updates ?

      • olivier
      • 3 yrs ago
      • Reported - view

      G B we're still working on it

      • G_B
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey 

      • G_B
      • 3 yrs ago
      • Reported - view

      Olivier  an update is urgently needed here

      • G_B
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey shall I expect an update or consider this and your support dead in the water ?

      • G_B
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey your support here is unacceptable, the only worst is your communication. I don't know what the issue is and why you can't solve it but you could at least post something like "it is taking longer than expected" or "we haven't figured it out yet"

      • Anownymous
      • 3 yrs ago
      • Reported - view

      G B free user?

      • G_B
      • 3 yrs ago
      • Reported - view

      Anownymous no, paid on day 1

      • Anownymous
      • 3 yrs ago
      • Reported - view

      G B same. I am a pro subscriber too. This kind of community support is really not that great if issues requires checking in the server, i wish they add proper  support in the Pro tier, not just business tier.

      • olivier
      • 3 yrs ago
      • Reported - view

      G B the problem has been solved weeks ago by steering your ISP to another PoP. We do not have a Greek PoP yet so we can’t provide the best latency in your location for the moment.

      • G_B
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey Why you say it is solved? It is pretty clear from my posts that it was never solved. I still connect to the same server with the same bad performance

      • olivier
      • 3 yrs ago
      • Reported - view

      G B please provide another diag.

      • G_B
      • 3 yrs ago
      • Reported - view
      • olivier
      • 3 yrs ago
      • Reported - view

      G B please disable nextdns and show the output of https://test.nextdns.io

      • G_B
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey needed to find a timeslot to do this, here you go:

      {
      "status": "unconfigured",
      "client": "2a02:587:2c18:5510:f9c4:3300:ede7:b386",
      "resolver": "83.235.71.59",
      "server": "zepto-lon-1"
      }
      
      • olivier
      • 3 yrs ago
      • Reported - view

      G B which version of the CLI do you run?

      • G_B
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey I was in 1.9.4 actually. I upgraded now to the latest and I see a server change but still far from optimal, actually worst than before

        serverwala-buh           29 ms

        anexia-ams (IPv6)        47 ms  (anycast2)

        anexia-lon               52 ms  (anycast2)

        zepto-lon                52 ms  (anycast1)

        zepto-fra (IPv6)         54 ms  (anycast1)

        exoscale-vie (IPv6)      55 ms

        exoscale-vie             63 ms

        anexia-vie               63 ms

        anexia-vie (IPv6)        77 ms

        serverwala-mil           78 ms

        edgeuno-ist (IPv6)       86 ms

        edgeuno-ist             100 ms  (ultralow1)

        citynet-cai             101 ms

      ■ premiumrdp-ist          106 ms  (ultralow2)

        anexia-sof              170 ms

        zepto-sof               190 ms

        anexia-sof (IPv6)       196 ms

        serverwala-buh (IPv6)    error

        estnoc-buh               error

      dns1.nextdns.io (IPv6) error (ultralow1)

      dns2.nextdns.io (IPv6) error (ultralow2)

      • G_B
      • 3 yrs ago
      • Reported - view
      • olivier
      • 3 yrs ago
      • Reported - view

      G B it will be optimal when we will have a Greek PoP.

Content aside

  • 1 Likes
  • 3 yrs agoLast active
  • 27Replies
  • 631Views
  • 5 Following