0

Slow ping on 45.90.30.0 but fast on 45.90.28.0 ?

I notice some problems with pinging the 2 main ip-addresses of NextDNS. I used a wired machine to do these ping tests... It seems that the .30 ip is not routing correct?

IPV4

ping 45.90.28.0
PING 45.90.28.0 (45.90.28.0): 56 data bytes
64 bytes from 45.90.28.0: icmp_seq=0 ttl=51 time=5.626 ms
64 bytes from 45.90.28.0: icmp_seq=1 ttl=51 time=5.515 ms
64 bytes from 45.90.28.0: icmp_seq=2 ttl=51 time=5.571 ms
64 bytes from 45.90.28.0: icmp_seq=3 ttl=51 time=5.477 ms
64 bytes from 45.90.28.0: icmp_seq=4 ttl=51 time=5.619 ms

 

ping 45.90.30.0
PING 45.90.30.0 (45.90.30.0): 56 data bytes
64 bytes from 45.90.30.0: icmp_seq=0 ttl=56 time=11.466 ms
64 bytes from 45.90.30.0: icmp_seq=1 ttl=56 time=11.401 ms
64 bytes from 45.90.30.0: icmp_seq=2 ttl=56 time=11.403 ms
64 bytes from 45.90.30.0: icmp_seq=3 ttl=56 time=11.591 ms
64 bytes from 45.90.30.0: icmp_seq=4 ttl=56 time=11.368 ms
64 bytes from 45.90.30.0: icmp_seq=5 ttl=56 time=11.590 ms

IPV6

ping6 2a07:a8c0::0
PING6(56=40+8+8 bytes)  --> 2a07:a8c0::
16 bytes from 2a07:a8c0::, icmp_seq=0 hlim=54 time=6.932 ms
16 bytes from 2a07:a8c0::, icmp_seq=1 hlim=54 time=6.924 ms
16 bytes from 2a07:a8c0::, icmp_seq=2 hlim=54 time=7.025 ms
16 bytes from 2a07:a8c0::, icmp_seq=3 hlim=54 time=7.199 ms
16 bytes from 2a07:a8c0::, icmp_seq=4 hlim=54 time=6.929 ms
16 bytes from 2a07:a8c0::, icmp_seq=5 hlim=54 time=7.030 ms
ping6 2a07:a8c1::0
PING6(56=40+8+8 bytes) --> 2a07:a8c1::
16 bytes from 2a07:a8c1::, icmp_seq=0 hlim=52 time=281.576 ms
16 bytes from 2a07:a8c1::, icmp_seq=1 hlim=52 time=281.665 ms
16 bytes from 2a07:a8c1::, icmp_seq=2 hlim=52 time=281.361 ms
16 bytes from 2a07:a8c1::, icmp_seq=3 hlim=52 time=281.260 ms
16 bytes from 2a07:a8c1::, icmp_seq=4 hlim=52 time=281.644 ms
16 bytes from 2a07:a8c1::, icmp_seq=5 hlim=52 time=281.535 ms
16 bytes from 2a07:a8c1::, icmp_seq=6 hlim=52 time=281.560 ms
16 bytes from 2a07:a8c1::, icmp_seq=7 hlim=52 time=281.531 ms

 

ping.nextdns.io

  vultr-ams            4 ms  (anycast1, ultralow2)
  vultr-ams (IPv6)     5 ms  (anycast1, ultralow2)
  zepto-ams            5 ms
  zepto-fra           10 ms
  anexia-fra (IPv6)   10 ms
  zepto-lon (IPv6)    10 ms
  zepto-fra (IPv6)    11 ms
  zepto-lon           11 ms
  estnoc-bru          11 ms
  vultr-fra (IPv6)    11 ms
  anexia-fra          13 ms  (anycast2)
  vultr-lon           13 ms
  vultr-fra           13 ms
  vultr-lon (IPv6)    13 ms
  zepto-bru           16 ms
  anexia-ams          18 ms  (ultralow1)
  anexia-ams (IPv6)   20 ms  (ultralow1)
  zepto-bru (IPv6)    35 ms
  zetta-syd (IPv6)   286 ms  (anycast2)

 

Diag

https://nextdns.io/diag/89c60dd0-66c9-11eb-a15a-97cb7443d919

 

Contact me for more info..

7replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • This is the traceroute btw
     

    traceroute 45.90.28.0
    traceroute to 45.90.28.0 (45.90.28.0), 64 hops max, 52 byte packets
     1  192.168.2.254 (192.168.2.254)  0.626 ms  0.404 ms  0.361 ms
     2  195-190-228-47.fixed.kpn.net (195.190.228.47)  9.220 ms  1.761 ms  1.504 ms
     3  * * *
     4  * * *
     5  nl-ams02a-rc2-lag-2-0.aorta.net (84.116.135.146)  5.980 ms
        nl-ams17b-rc1-lag-3-0.aorta.net (84.116.135.150)  5.959 ms  5.903 ms
     6  nl-srk03a-ri1-ae-2-0.aorta.net (84.116.135.145)  5.913 ms
        nl-srk03a-ri1-ae-3-0.aorta.net (84.116.135.149)  5.879 ms
        nl-srk03a-ri1-ae-2-0.aorta.net (84.116.135.145)  6.321 ms
     7  213.46.182.142 (213.46.182.142)  6.324 ms  6.707 ms  6.372 ms
     8  * * *
     9  choopa-llc.ear3.amsterdam1.level3.net (213.19.196.242)  7.657 ms  7.432 ms  7.204 ms

     

    traceroute 45.90.30.0
    traceroute to 45.90.30.0 (45.90.30.0), 64 hops max, 52 byte packets
     1  192.168.2.254 (192.168.2.254)  0.626 ms  0.390 ms  0.354 ms
     2  195-190-228-47.fixed.kpn.net (195.190.228.47)  1.792 ms  1.551 ms  1.492 ms
     3  * * *
     4  * * *
     5  nl-ams09b-ri1-ae31-0.aorta.net (84.116.130.150)  11.506 ms  11.491 ms  11.376 ms
     6  de-fra02a-rc1-ae-14-0.aorta.net (84.116.130.149)  13.199 ms  13.220 ms  13.226 ms
     7  de-fra02a-ri1-ae-30-0.aorta.net (84.116.137.17)  15.931 ms  29.406 ms  11.402 ms
     8  213.46.179.114.aorta.net (213.46.179.114)  13.183 ms  17.174 ms  13.249 ms

     

    IPV6

    traceroute6 2a07:a8c0::0
    traceroute6 to 2a07:a8c0::0 (2a07:a8c0::) from 2a02:a441:2991:1:197:7980:3762:502, 64 hops max, 12 byte packets
     1  2a02-a441-2991-1--1.fixed6.kpn.net  0.515 ms  0.497 ms  0.443 ms
     2  2001:67c:2502:f100::2:2f  1.703 ms  7.759 ms  1.811 ms
     3  * * *
     4  * * *
     5  2001:730:2200::5474:8025  6.171 ms
        2001:730:2200::5474:8004  7.030 ms  7.056 ms
     6  2001:730:2200::5474:8009  6.437 ms  6.352 ms  6.289 ms
     7  * * *
     8  * * *
     9  choopa-llc.ear3.amsterdam1.level3.net  8.231 ms  28.393 ms  9.123 ms
    10  2001:19f0:5000::a48:9e  8.110 ms  9.525 ms  9.583 ms
    11  2001:19f0:5000::a48:1002  7.169 ms  7.066 ms  7.098 ms
    
    traceroute6 2a07:a8c1::0
    traceroute6 to 2a07:a8c1::0 (2a07:a8c1::) from 2a02:a441:2991:1:197:7980:3762:502, 64 hops max, 12 byte packets
     1  2a02-a441-2991-1--1.fixed6.kpn.net  0.486 ms  0.392 ms  0.374 ms
     2  2001:67c:2502:f100::2:2f  1.811 ms  1.453 ms  1.422 ms
     3  * * *
     4  * * *
     5  2001:730:2200::5474:8025  11.429 ms  11.250 ms  11.253 ms
     6  * * *
     7  * * *
     8  2001:730:2d01:20::2  11.569 ms  11.563 ms  11.464 ms
    
    Like
  • Thank you for sharing this detail, I have the same high ping times and slow dns resolution on 45.90.30.94 of roughly 108ms, and fast normal times of 6ms on 45.90.28.94.

    I look forward to seeing what's going on, for now, i quit using 45.90.30.94, and am just using 45.90.28.94.  That makes surfing more normal speed.  Thank you for sharing this Michiel

    Like
      • Michiel
      • Michiel
      • 8 mths ago
      • Reported - view

      RDLMP for me it seems that the .28.x addrrsses are fast and .30.x are ‘slow’

      Like
      • RDLMP
      • Mitchell_Parks
      • 8 mths ago
      • Reported - view

      Michiel I agree, I'm still figuring out how all of these IPs etc. are set up, how you determine which ip is closest etc.  I wasthinking the portal and paid subscription enables the fastest two IPs. Does that sound correct to you Michiel my portal shows the two ips under Setup/Linked IP 45.90.28.94 and 45.90.30.94 and 28.94 is 5ms, 30.94 is 110ms.  The 28.94 is fast on quickie lookups, about 10ms slower than cached lookups over 'cough cough' the competitors.  I hope that nextdns will be best, it's a great overall infrastructure.  We will see over the next months.  I see the founder/creator chimes in and helps a lot.

      Like
      • Michiel
      • Michiel
      • 8 mths ago
      • 1
      • Reported - view

      RDLMP for me it seems 45.90.28.0 is the fastest, when pinging... I use dnscrypt-proxy btw

      Like 1
  • Do you or does anyone know.....

    Can we use 45.90.28.0 even though the setup screen tells us to use 45.90.28.94?

    The nextdns.io tells me to use 45.90.28.94 and 45.90.30.94.

    45.90.28.94 is 5ms, 45.90.30.94 is 108 ms running Steve Gibson's GRC DNS Benchmark.

    I'd love to know what others know about nextdns.io. I don't want to run with just one dns server. I'd prefer 2 to use. but 45.90.30.94 is way way too slow with dns queries.

    Thank you all, the community is great.

    Like
  • FYI to everyone intestested.

    Since we all don't have routers or PCs in every city around the world and in particular on internet backbone connections, you can use portals called 'looking glass' from each carrier to ping from a city on their network to you, or you to nextdns.io servers.

    You can make sure the problem isn't your equipment first.

    Here's a 'Looking Glass' portal link on Cogentco network.

    https://www.cogentco.com/en/looking-glass

    Play with it, if you ping yourself, make sure responding to pings is enabled, then when you're through turn it back OFF.

    Thanks everyone.

    Like
Like Follow
  • 8 mths agoLast active
  • 7Replies
  • 165Views
  • 2 Following