0

"anexia-fra-1" is having issues

Since a couple hours ago I'm noticing increased latency while browsing the web.

  vultr-fra                8 ms

  zepto-fra (IPv6)         8 ms  (anycast1, ultralow1)

  zepto-fra                8 ms  (anycast1, ultralow1)

  vultr-fra (IPv6)         8 ms

  exoscale-zrh            13 ms

  exoscale-zrh (IPv6)     13 ms

  anexia-zrh (IPv6)       14 ms

  anexia-zrh              15 ms

  anexia-par              17 ms

  virtua-par (IPv6)       17 ms  (anycast2, ultralow2)

  anexia-fra (IPv6)       17 ms

  netbarista-par          18 ms

  zepto-bru               21 ms

  virtua-par              23 ms

  anexia-par (IPv6)       24 ms

  netbarista-par (IPv6)   26 ms

  zepto-bru (IPv6)        27 ms

  anexia-fra              28 ms  (anycast2, ultralow2)   <====

  estnoc-bru              30 ms

 

According to ping.nextdns.io the problem seems to be "anexia-fra-1" which has unstable ping (between 8 and 30+ms).

Unfortunately I'm getting connected to "anexia-fra-1" most of the time. The other -fra servers seem unaffected with stable 8-10ms ping.

 

Another ping with even worse lag on anexia-fra:

 

zepto-fra                8 ms  (anycast1, ultralow1)

  zepto-fra (IPv6)         8 ms  (anycast1, ultralow1)

  vultr-fra                8 ms

  anexia-fra (IPv6)        8 ms

  vultr-fra (IPv6)         9 ms

  exoscale-zrh (IPv6)     13 ms

  exoscale-zrh            13 ms

  anexia-zrh (IPv6)       14 ms

  virtua-par (IPv6)       18 ms  (anycast2, ultralow2)

  netbarista-par          18 ms

  estnoc-bru              18 ms

  anexia-par              18 ms

  zepto-bru               20 ms

  virtua-par              22 ms

  anexia-par (IPv6)       23 ms

  zepto-bru (IPv6)        24 ms

  netbarista-par (IPv6)   26 ms

  anexia-zrh              33 ms

  anexia-fra              79 ms  (anycast2, ultralow2)  <====

 

Another ping, just the anexia part:

■ anexia-fra              79 ms  (anycast2, ultralow2)

  anexia-par (IPv6)       error

3 replies

null
    • Valynor
    • 3 yrs ago
    • Reported - view

    Traceroute:

    mtr -r -c 5 217.146.22.163
    Start: 2021-01-29T16:29:51+0100
    HOST: ConnorMint                  Loss%   Snt   Last   Avg  Best  Wrst StDev
    1.|-- _gateway                   0.0%     5    0.5   0.4   0.4   0.5   0.0
    2.|-- p3e9bf6b0.dip0.t-ipconnec  0.0%     5    4.4   5.1   4.4   6.4   0.8
    3.|-- 217.5.109.50               0.0%     5    8.5   8.2   8.1   8.5   0.2
    4.|-- 80.156.161.186             0.0%     5    7.5   8.0   7.5   8.8   0.5
    5.|-- ae0-0.bbr01.anx25.fra.de. 0.0% 5 8.1 9.8 8.0 15.7 3.3
    6.|-- dns.nextdns.io 0.0% 5 7.2 28.1 7.2 110.8 46.2

    ^really bad lag on hop 6

      • olivier
      • 3 yrs ago
      • Reported - view

      Valynor we're looking into it.

      • Valynor
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey Seems like that was a bigger issue with the servers being offline for several days.
      It's running fine again now:

      ■ anexia-fra (IPv6)        8 ms  (ultralow1)

        anexia-fra               8 ms  (anycast2, ultralow1)

        zepto-fra                8 ms  (anycast1)

        vultr-fra (IPv6)         8 ms  (ultralow2)

        vultr-fra                8 ms  (ultralow2)

        zepto-fra (IPv6)         9 ms  (anycast1)

        exoscale-zrh            13 ms

        exoscale-zrh (IPv6)     14 ms

        anexia-zrh (IPv6)       14 ms

        anexia-zrh              15 ms

Content aside

  • 3 yrs agoLast active
  • 3Replies
  • 170Views
  • 2 Following