Level3 + HE = no-go?

[sporkv6]

So I saw that Level3 decided to join in the fun today and publish an AAAA record:

hotlap:~ spork$ host www.level3.com
www.level3.com has address 4.68.90.77
www.level3.com has IPv6 address 2001:1900:2018:3000::105

But on my HE tunnel, I die at the edge of HE's network:

Code Select Expand


3  gige-g3-8.core1.nyc4.he.net  12.844 ms  15.518 ms  10.421 ms
4  10gigabitethernet8-3.core1.chi1.he.net  29.561 ms  27.972 ms  28.109 ms
5  10gigabitethernet3-2.core1.den1.he.net  53.051 ms  54.448 ms  53.060 ms
6  10gigabitethernet4-4.core1.sjc2.he.net  82.874 ms  79.703 ms  79.987 ms
7  10gigabitethernet3-2.core1.pao1.he.net  84.509 ms  79.929 ms  83.902 ms
8  * * *
9  * * *
10  * * *


Am I seeing some weird misconfiguration that's been hiding for months, or do other people see this as well?  With a co-lo box with v6 transit (not HE) I can reach it, but it's a crappy path - US to Europe and back again.

Is Level3 being stingy with their IPv6 peering?

[hisken]

Jup, still some kind of peering dispute between HE and L3... Has been a problem for a long time. I don't think actually it will be resolved in short-term.

[sporkv6]

Here's another one not from HE, which I mentioned above:

Code Select Expand


5  xe-5-1-0.nyc20.ip6.tinet.net  1.663 ms  37.214 ms  54.513 ms
6  2001:504:1::a500:2497:1  2.385 ms  2.475 ms  2.074 ms
7  nyc002bb00.iij.net  2.232 ms  2.215 ms  2.074 ms
8  abn001bb00.iij.net  8.784 ms  8.264 ms  8.097 ms
9  2600:803:92f::1  81.105 ms  81.149 ms  80.963 ms
10  0.lo0.GW6.DCA6.ALTER.NET  78.619 ms  78.790 ms  78.793 ms
11  tu192.6b1.fft4.alter.net  100.922 ms  100.836 ms  101.505 ms
12  ffm-s1-rou-1006.DE.eurorings.net  100.497 ms  99.725 ms  176.879 ms
13  * * *
14  vl-4060.edge4.Paris1.Level3.net  97.995 ms  96.582 ms  115.666 ms
15  tu-607.sar1.Amsterdam1.Level3.net  101.396 ms  101.515 ms  101.682 ms
16  vl-4060.edge4.Paris1.Level3.net  96.625 ms  96.965 ms  96.396 ms
17  vl-4080.edge3.Paris1.Level3.net  97.229 ms  96.484 ms
    vl-4081.edge3.Paris1.Level3.net  119.584 ms
18  vl-4086.car1.Washington1.Level3.net  116.512 ms  117.631 ms  116.587 ms
19  vl-4080.car2.Washington1.Level3.net  128.264 ms  121.608 ms  112.243 ms
20  vl-4061.car1.NewYork2.Level3.net  130.649 ms  138.493 ms  105.245 ms
21  vl-4080.car2.NewYork2.Level3.net  102.640 ms  102.421 ms  101.674 ms
22  vl-4061.car1.Chicago1.Level3.net  125.581 ms  125.642 ms  146.282 ms
23  * * *
24  vl-4041.car2.Denver1.Level3.net  153.729 ms  196.940 ms  154.462 ms
25  vl-4080.car1.Denver1.Level3.net  337.844 ms  267.426 ms  462.496 ms
26  Level3-MOSS.vl-956.car1.Denver1.Level3.net  153.576 ms  154.571 ms  154.901 ms
27  *^C
[code]

I wonder how many of the "big guys" are using IPv6 as an opportunity to get themselves some more cash by forcing peers to become customers or to enforce more rigid ratios.

I'd say that path is "non-optimal".  If it were me, I'd take that path, some very nice destinations, but for my packets, I'd prefer to bypass Europe. :)[/code]

[cconn]

I have access to level3 via another peer, and although it does connect, I get a 404 Not Found error.

So you are not missing much  :P