0

French High Latency Issue Due To Wrong Route

Hi.

I am based in France/Paris but all my requests go through the US servers which gives a very high latency. Sometimes it goes up to 300ms.

Because it seems that the diagnostic cannot be done on iPhone or iPad, attached are the results from my macOS MacBook Pro:

- Ping

- Traceroute

- NextDNS Diagnostic.

Thanks for your help.

Pete

9 replies

null
    • NextDNs
    • 2 yrs ago
    • Reported - view

    Your screenshot and the file you attach show ~10ms latency and the right endpoint selected. How do you measure 300ms?

      • Pierre_Cartier
      • 2 yrs ago
      • Reported - view

      NextDNS 

      The screen shots and file above come from my MacBook Pro. 

      Because I can't use the Diag Tool on iOS I get the measurement from AdGuard Pro. 

      The 207ms below is today average with NextDNS. As mentioned above if I change the DNS to Cloudflare I get 10ms max. 

      Also, I didn't get any answer why my requests go through  the US?

      Thanks. 

      • Mogsy
      • 2 yrs ago
      • Reported - view

      Pierre Cartier I believe this is overall average. If you check your dns query log, click one query and that should be your normal latency. The 207 is average time overall 49k requests.

      • Pierre_Cartier
      • 2 yrs ago
      • Reported - view

      Mogsy 

      Thanks but I do know it's an average. It is in fact the day average of all requests being made.

      But like any average calculation, to get such results either each request latency is huge or the standard deviation is too important. Which means that in both cases the latency is still to big. 

      The tests I have been assked to perform reflect only one try like a speed test and don't give the reality of a full day. 

      Also, strangely I never got an answer why my requests go through the US and not UE when I sit in France, where NextDNS has servers. IMHO that will explain my latency problem. 

      Finally, like I already mentioned it, using Cloudflare gives me an average of 10ms which looks normal and more appropriate. There again, no feedback regarding this difference vs NextDNS. 

      • Pierre_Cartier
      • 2 yrs ago
      • Reported - view

      juliank 

      Mainly for two reasons. 

      1. AdGuard keeps the aesthetics of the page layout. 

      2. I am also using a VPN. 

      Being an Apple user iOS doesn't offer split tunnel option, something that AG does. Which allows me to use a provider for VPN and another for DNS.  

      • NextDNs
      • 2 yrs ago
      • Reported - view

      Pierre Cartier where do you see you are going through the US? None of you screenshots show that.

      On iOS you may have DNS requests timing out when device is in sleep mode. It really depend how adguard computes this metric. Average latency is generally not a very good metric.

      • Pierre_Cartier
      • 2 yrs ago
      • Reported - view

      NextDNS 

      Regarding your remark you might be right but it doesn't explain the difference between NextDNS and Cloudflare that I both tested 24H each to check the latency.

      So, if I follow your argument Cloudflare on AG should have shown 200ms and not 10ms, shouldn't it?

       

      About the traceroute, it shows I am routing to the US, am I not?


      traceroute to 45.90.28.114 (45.90.28.114), 10 hops max, 60 byte packets
      1 vl1.csw1-rin1.linode.com (45.79.12.201) 0.479 ms 0.638 ms 0.778 ms
      2 if-0-0-4-0.gw1.rin1.us.linode.com (45.79.12.0) 0.360 ms 0.364 ms 0.356 ms
      3 199.245.16.65 (199.245.16.65) 1.578 ms 1.704 ms 1.818 ms
      4 199.245.16.65 (199.245.16.65) 2.001 ms 2.019 ms ae-0.constant-company.dllstx11.us.bb.gin.ntt.net (128.241.219.54) 1.376 ms
      5 ae-0.constant-company.dllstx11.us.bb.gin.ntt.net (128.241.219.54) 1.904 ms 10.78.5.5 (10.78.5.5) 1.489 ms ae-0.constant-company.dllstx11.us.bb.gin.ntt.net (128.241.219.54) 1.892 ms
      6 10.78.5.5 (10.78.5.5) 1.476 ms 10.78.0.250 (10.78.0.250) 2.359 ms 10.78.0.130 (10.78.0.130) 1.447 ms

      ---------

      traceroute to 45.90.30.114 (45.90.30.114), 10 hops max, 60 byte packets
      1 vl1.csw1-rin1.linode.com (45.79.12.201) 0.506 ms 0.586 ms 0.663 ms
      2 if-0-1-4-0.gw2.rin1.us.linode.com (45.79.12.6) 0.378 ms if-0-0-4-0.gw1.rin1.us.linode.com (45.79.12.0) 0.355 ms 0.364 ms
      3 ae-0-100.gw2.rin1.us.linode.com (45.79.12.9) 0.362 ms 199.245.16.65 (199.245.16.65) 1.272 ms ae-0-100.gw2.rin1.us.linode.com (45.79.12.9) 0.348 ms
      4 ae-11.r21.dllstx14.us.bb.gin.ntt.net (129.250.7.114) 12.569 ms 199.245.16.65 (199.245.16.65) 1.345 ms 1.432 ms
      5 ae-11.r21.dllstx14.us.bb.gin.ntt.net (129.250.7.114) 12.570 ms 12.561 ms *
      6 xe-5-5-1-0.a00.dllstx14.us.ce.gin.ntt.net (168.143.191.171) 1.474 ms 1.146 ms 1.130 ms
      7 * * xe-5-5-1-0.a00.dllstx14.us.ce.gin.ntt.net (168.143.191.171) 1.417 ms

      • NextDNs
      • 2 yrs ago
      • Reported - view

      Pierre Cartier your traceroute starts from linode, I guess you have a VPN on. This VPN exit node is probably in the US, which could also explain your high DNS latency.

      • Pierre_Cartier
      • 2 yrs ago
      • Reported - view

      NextDNS 

      Indeed, I am using a VPN, Windscribe in fact. However your question is more related to how Tor works, not a VPN. 

      I am based in Paris and I am using Paris server from Windscribe. If I disabled NextDNS and use Windscribe DNS, my traceroute is correct. 

      However, when I activate NextDNS, the route goes to the US.  

      So, I am confused because it doesn't make sense. That's why I am looking for an explanation in order to get a solution. 

      Thanks. 

Content aside

  • 2 yrs agoLast active
  • 9Replies
  • 247Views
  • 3 Following