0

45.90.30.0 issue from FR

Hi,

I am from France.

Since a few days, the latency to 45.90.30.0 have increased. This DNS server moved to Germany/Frankfurt (instead of Paris).

$ curl -k https://45.90.28.0/info
{"locationName": " Paris, France", "pop": "netbarista-par", "rtt": 13094}

$ curl -k https://45.90.30.0/info
{"locationName": " Frankfurt, Germany", "pop": "vultr-fra", "rtt": 18708}

 

Is there a current issue on 45.90.30.0 ?

Same issue with the ipv6 addresses...

thanks.

15 replies

null
    • NextDNs
    • 1 mth ago
    • Reported - view

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

      • Christophe_Yayon
      • 1 mth ago
      • Reported - view

      https://help.nextdns.io/profile/804lt4

       

      thanks

      • NextDNs
      • 1 mth ago
      • Reported - view

       wrong URL?

      • Christophe_Yayon
      • 1 mth ago
      • Reported - view

      sorry, https://nextdns.io/diag/1418e010-dc6b-11ee-8ab3-7d71086c4c18

      thanks

      • NextDNS_Network
      • 1 mth ago
      • Reported - view

       We've made some changes, and would you mind confirming if it's better now?

      • Christophe_Yayon
      • 1 mth ago
      • Reported - view

       Hi, it's ok since yesterday 23h00. Thanks !

    • Christophe_Yayon
    • 1 mth ago
    • Reported - view

    Hi,

     

    Since a few days, the latency to 45.90.30.0 (ipv6 too) has increased in work hours. During the night, the latency is normal. The issue seems to be related to your last change for this ticket. 

    Here are the grafana screenshots from primary 45.90.28.0 and secondary 45.90.30.0.

    Thanks.

      • NextDNS_Network
      • 1 mth ago
      • Reported - view

      It could be. Do you have a traceroute / MTR during the spike?

      • Christophe_Yayon
      • 1 mth ago
      • Reported - view

       

       

      This issue is very unstable, and sporadic.

      Here is a simple ping test :

       

      # ping 45.90.30.0
PING 45.90.30.0 (45.90.30.0) 56(84) bytes of data.
64 bytes from 45.90.30.0: icmp_seq=1 ttl=49 time=50.1 ms
64 bytes from 45.90.30.0: icmp_seq=2 ttl=49 time=13.3 ms
64 bytes from 45.90.30.0: icmp_seq=3 ttl=49 time=13.4 ms
64 bytes from 45.90.30.0: icmp_seq=4 ttl=49 time=13.3 ms
64 bytes from 45.90.30.0: icmp_seq=5 ttl=49 time=13.5 ms
64 bytes from 45.90.30.0: icmp_seq=6 ttl=49 time=13.7 ms
64 bytes from 45.90.30.0: icmp_seq=7 ttl=49 time=24.3 ms
64 bytes from 45.90.30.0: icmp_seq=8 ttl=49 time=222 ms
64 bytes from 45.90.30.0: icmp_seq=9 ttl=49 time=22.5 ms
64 bytes from 45.90.30.0: icmp_seq=10 ttl=49 time=13.5 ms
64 bytes from 45.90.30.0: icmp_seq=11 ttl=49 time=15.1 ms
64 bytes from 45.90.30.0: icmp_seq=12 ttl=49 time=20.5 ms
64 bytes from 45.90.30.0: icmp_seq=13 ttl=49 time=88.7 ms
64 bytes from 45.90.30.0: icmp_seq=14 ttl=49 time=13.4 ms
^C
--- 45.90.30.0 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 13019ms
rtt min/avg/max/mdev = 13.304/38.402/222.234/54.861 ms

# ping 45.90.28.0
PING 45.90.28.0 (45.90.28.0) 56(84) bytes of data.
64 bytes from 45.90.28.0: icmp_seq=1 ttl=48 time=13.5 ms
64 bytes from 45.90.28.0: icmp_seq=2 ttl=48 time=13.6 ms
64 bytes from 45.90.28.0: icmp_seq=3 ttl=48 time=13.4 ms
64 bytes from 45.90.28.0: icmp_seq=4 ttl=48 time=13.5 ms
64 bytes from 45.90.28.0: icmp_seq=5 ttl=48 time=13.5 ms
64 bytes from 45.90.28.0: icmp_seq=6 ttl=48 time=13.4 ms
64 bytes from 45.90.28.0: icmp_seq=7 ttl=48 time=13.3 ms
64 bytes from 45.90.28.0: icmp_seq=8 ttl=48 time=13.4 ms
64 bytes from 45.90.28.0: icmp_seq=9 ttl=48 time=13.5 ms
64 bytes from 45.90.28.0: icmp_seq=10 ttl=48 time=13.3 ms
64 bytes from 45.90.28.0: icmp_seq=11 ttl=48 time=13.5 ms
64 bytes from 45.90.28.0: icmp_seq=12 ttl=48 time=13.5 ms
64 bytes from 45.90.28.0: icmp_seq=13 ttl=48 time=13.7 ms
64 bytes from 45.90.28.0: icmp_seq=14 ttl=48 time=13.5 ms

       

      I also made some mtr tests on 45.90.30.0, here are the screenshots.

      I snapped the screenshot as soon I see a bad response time. As I understand the results, latency seems coming from the last hop (dns2.nextdns.io) itself... Isn't it ?

      Screenshot 2024-03-16 at 18.28.22 Screenshot 2024-03-16 at 18.28.36 Screenshot 2024-03-16 at 18.28.44 Screenshot 2024-03-16 at 18.29.07
      • Will_Tisdale
      • 1 mth ago
      • Reported - view

       

      I'm also seeing very similar latency spikes on anexia-lon up to ~250ms, and on vultr-lon up to about ~80ms.

      Anexia drops down to ~13ms overnight between 0100 and 0600, so it's likely that particular server is overloaded.

      The vultr latency is constant, with packet loss too, but the problem appears to be in the NTT network and not the server.

                                                             My traceroute  [v0.95]
nas.z3n.uk (2001:8b0:6401:82a0:0:ffff:a0a:a05) -> 2a07:a8c0:: (2a07:a8c0::)                                2024-03-18T12:53:27+0000
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                                           Packets               Pings
 Host                                                                                    Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. router.z3n.uk                                                                         0.0%   935    2.5   2.2   1.7  12.2   0.8
 2. g.gormless.thn.aa.net.uk                                                              0.0%   935   14.2  12.8  11.9  22.2   0.9
 3. ntt.a.needless.tch.aa.net.uk                                                          0.0%   935   13.6  12.9  11.7  29.4   0.9
 4. xe-0-5-3-3.a01.londen17.uk.bb.gin.ntt.net                                             0.0%   935   12.5  15.0  12.1  55.9   5.0
 5. ae-7.r20.londen12.uk.bb.gin.ntt.net                                                  22.4%   935   20.7  16.3  12.2  50.7   5.6
 6. ae-0.a02.londen12.uk.bb.gin.ntt.net                                                   0.0%   935   13.8  14.6  12.1  52.7   4.3
 7. xe-0-3-0-0.a02.londen12.uk.ce.gin.ntt.net                                             1.5%   935   70.8  25.8  12.4 116.6  21.2
 8. ethernetae7-sr1.lon3.constant.com                                                     1.3%   935   73.1  23.6  13.0  88.1  19.1
 9. ethernetswp25-ds1-u3-r51b4-b.lon3.constant.com                                        1.3%   935   70.7  21.5  12.5  70.7  18.6
10. (waiting for reply)
11. 2a07:a8c0::                                                                           0.6%   934   69.7  21.7  12.2  71.4  18.7

      All in all, it's making anycast kinda naff at the moment. 

      • Christophe_Yayon
      • 1 mth ago
      • Reported - view

       Ok, I understand, perhaps NextDNS staff could contact NTT ?

    • Christophe_Yayon
    • 1 mth ago
    • Reported - view

    It seems to be better since yesterday 17h35 (GMT+1). Did you change something ?

    • Christophe_Yayon
    • 1 mth ago
    • Reported - view

    Hi,

    same issue back again this night from France.

    what does it happen ?

      • NextDNs
      • 1 mth ago
      • Reported - view

      please send a diag

      • Christophe_Yayon
      • 1 mth ago
      • Reported - view

       

      hi, it seems to be solved since about 13h00 (France).

      thanks !

Login to reply

Content aside

  • 1 mth agoLast active
  • 15Replies
  • 207Views
  • 5 Following