0

Routing to Mexico from UK on IPv6

I see from the forums that there have been some routing changes but IPv6 with my ISP (Andrews & Arnold) in the UK is still not very happy. 

My diagnostic report is here:

https://nextdns.io/diag/3ea4f110-a11b-11ee-af01-9991396cd19a

Key section is this:

 

Secondary IPv6: anexia-mex (146 ms)

1 my ipv6 1 ms 0 ms 0 ms AS20712 Andrews & Arnold Ltd
2 u.gormless.thn.aa.net.uk (2001:8b0:0:53::129) 9 ms 10 ms 10 ms AS20712 Andrews & Arnold Ltd
3 n-aimless.thn.aa.net.uk (2001:8b0:0:53::104) 9 ms 8 ms 16 ms AS20712 Andrews & Arnold Ltd
4 * * * *  
5 * * * *  
6 * * * *  
7 * * * *  
8 * * * *  
9 * * * *  
10 * * * *  
11 2001:504:0:2:0:3:2098:1 143 ms 144 ms 144 ms  
12 2604:d600:ff0c:3f::1 141 ms 140 ms 141 ms AS32098 TRANSTELCO-INC
13 2604:d600:ff00:bb::2 159 ms 158 ms 160 ms AS32098 TRANSTELCO-INC
14 2806:20d:16ff:fff8::1 165 ms 164 ms 165 ms AS32098 TRANSTELCO-INC
15 2806:320:0:5::2 177 ms 177 ms 180 ms AS28438 ATC HOLDING FIBRA MEXICO, S. DE R.L. DE C.V.
16 2001:1270:3000:2::a 140 ms 141 ms 140 ms AS22908 Sixsigma Networks Mexico, S.A. de C.V.
17 2803:ad80:0:2:: 138 ms 143 ms 141 ms AS42473 ANEXIA Internetdienstleistungs GmbH
18 dns2.nextdns.io (2a07:a8c1::) 140 ms 138 ms 141 ms AS34939 nextdns, Inc.

`ping.nextdns.io` shows IPv6 `anexia-lon` erroring out, and `anexia-mex` comes up for `anycast2` - which is a bit far I guess!

 

  zepto-lon (IPv6)         9 ms  (ultralow2)
  zepto-lon                9 ms  (ultralow2)
■ vultr-lon               12 ms  (anycast1, ultralow1)
  vultr-lon (IPv6)        12 ms  (anycast1, ultralow1)
  anexia-lon              13 ms  (anycast2)
  vultr-ams (IPv6)        14 ms
  zepto-ams (IPv6)        17 ms
  netbarista-par (IPv6)   17 ms
  anexia-par (IPv6)       18 ms
  anexia-par              18 ms
  netbarista-par          18 ms
  vultr-ams               19 ms
  zepto-bru (IPv6)        20 ms
  virtua-par              20 ms
  zepto-ams               20 ms
  virtua-par (IPv6)       21 ms
  zepto-bru               24 ms
  fusa-bru                25 ms
  fusa-bru (IPv6)         28 ms
  anexia-mex (IPv6)      141 ms  (anycast2)
  anexia-lon (IPv6)       error

8 replies

null
    • S_M
    • 1 yr ago
    • Reported - view

    @nextdns_network  if you are looking at routing atm, I’m still seeing this in the UK. May be related to the other post that’s also routing via Mexico from US?

    • S_M
    • 1 yr ago
    • Reported - view

    https://nextdns.io/diag/b43fafd0-ae0b-11ee-94cc-87221b70b108

    Still getting sent to Mexico from theUK for ipv6 

    @nextdns_network - any thoughts?

    ```

    Traceroute for anycast secondary IPv6 (2a07:a8c1::)
    1 2001:8b0:dc1b:1da0::1    0ms   0ms   0ms
    2 2001:8b0:0:53::129    7ms   7ms   8ms
    3 2001:8b0:0:53::104    7ms   7ms   7ms
    4                   *     *     *
    5                   *     *     *
    6                   *     *     *
    7                   *     *     *
    8                   *     *     *
    9                   *     *     *
   10                   *     *     *
   11 2001:504:0:2:0:3:2098:1  141ms 143ms 141ms
   12 2604:d600:ff0c:3f::1  138ms 139ms 139ms
   13 2604:d600:ff00:bb::2  159ms 160ms 160ms
   14 2806:20d:16ff:fff8::1  160ms 161ms 162ms
   15 2806:320:0:5::2  174ms 174ms 174ms
   16 2001:1270:3000:2::a  139ms 138ms 139ms
   17 2803:ad80:0:2::  135ms 136ms 136ms
   18    2a07:a8c1::  138ms 139ms 139ms
```
      • NextDNS_Network
      • 1 yr ago
      • Reported - view

       We've applied some changes to Mexico node, please try again now.

      • Adrian
      • 1 yr ago
      • Reported - view

       

      I have just checked and am also seeing routing to Mexico from the UK:

      1  me  242.196 ms  2.568 ms  2.234 ms

      2  * * *

      3  * * *

      4  *

          2a00:1940:0:c::82  27.450 ms  8.972 ms

      5  2a00:1940:0:c::8d  7.112 ms  7.345 ms  7.899 ms

      6  2a00:1940:0:96::2  8.179 ms  7.487 ms  6.819 ms

      7  * * *

      8  * * *

      9  * * *

      10  * * *

      11  * * *

      12  * * *

      13  * * *

      14  2001:504:0:2:0:3:2098:1  234.777 ms  411.602 ms  144.211 ms

      15  2604:d600:ff0c:3f::1  354.063 ms  351.992 ms  156.213 ms

      16  2604:d600:ff0c:23::  367.670 ms  156.595 ms  354.499 ms

      17  2806:20d:16ff:fff8::1  158.851 ms  354.194 ms  157.731 ms

      18  2806:320:0:5::2  366.071 ms  167.154 ms  330.463 ms

      19  2001:1270:3000:2::a  154.009 ms  324.748 ms  154.456 ms

      20  2803:ad80:0:2::  137.497 ms  136.335 ms  137.405 ms

      21 dns2.nextdns.io 138.308 ms 137.013 ms 278.032 ms

      • S_M
      • 1 yr ago
      • Reported - view

       Sorry - still the same I'm afraid.

      I feel really bad just sending you errors like this - is there anything else I can do to help you? Do you need my ISP to try anything?

      Diag is here. 

      https://nextdns.io/diag/58b9e620-afba-11ee-b30f-ef9cf60d19e2

      ping.nextdns.io gives this

      
■ vultr-lon                9 ms  (anycast1, ultralow1)
  vultr-lon (IPv6)         9 ms  (anycast1, ultralow1)
  anexia-lon              10 ms  (anycast2)
  zepto-ams (IPv6)        14 ms
  vultr-ams (IPv6)        14 ms
  zepto-ams               15 ms
  anexia-par              16 ms
  netbarista-par          17 ms
  virtua-par              19 ms
  zepto-bru               22 ms
  zepto-bru (IPv6)        28 ms
  fusa-bru (IPv6)         32 ms
  netbarista-par (IPv6)   41 ms
  zepto-lon (IPv6)        43 ms  (ultralow2)
  virtua-par (IPv6)       45 ms
  fusa-bru                59 ms
  zepto-lon               66 ms  (ultralow2)
  vultr-ams               73 ms
  anexia-par (IPv6)       78 ms
  *anexia-mex (IPv6)      185 ms  (anycast2)*
  anexia-lon (IPv6)       error
      • NextDNS_Network
      • 1 yr ago
      • Reported - view

       We'll check it with our upstream provider today and get back to you.

      • S_M
      • 1 yr ago
      • Reported - view

       Great - thank you. I've just done a check again this morning. `anexia-mex (IPv6) 137 ms (anycast2)` still really wants to help serve my dns lookups. 

       

      Diagnostic is here. 

      • Adrian
      • 1 yr ago
      • Reported - view

      I'm still seeing this issue. Is there any update?

Login to reply

Content aside

  • 1 yr agoLast active
  • 8Replies
  • 140Views
  • 2 Following