No route to burstnet.eu

[johnpeach]

I have a server in Manchester, England on 2a02:21a8:1:252::c9d6:9fdc and cannot route either way between it and HE. My tunnel endpoint is on Optimum Online, Long Island.

From burstnet:

traceroute to homer.ipv6.peachfamily.net (2001:470:1f07:880:6ef0:49ff:fe2e:432a), 30 hops max, 80 byte packets
1  2a02:21a8:1:252::1 (2a02:21a8:1:252::1)  1.194 ms  1.494 ms  1.750 ms
2  * * *
3  * * *
4  * * *
5  * * *
6  * * *
7  * * *
8  * * *
9  * * *
10  * * *
11  * * *
12  * * 2a02:21a8::10c (2a02:21a8::10c)  0.811 ms !N

from New York:

traceroute to manchester.ipv6.peachfamily.net (2a02:21a8:1:252::c9d6:9fdc) from 2001:470:1f07:880:6ef0:49ff:fe2e:432a, 30 hops max, 24 byte packets
1  2001:470:1f07:880::1 (2001:470:1f07:880::1)  0.38 ms  0.316 ms  0.28 ms
2  johnpeach-1.tunnel.tserv4.nyc4.ipv6.he.net (2001:470:1f06:880::1)  18.65 ms  15.041 ms  14.794 ms
3  gige-g3-8.core1.nyc4.he.net (2001:470:0:5d::1)  20.049 ms  18.154 ms  16.911 ms
4  100gigabitethernet13-2.core1.chi1.he.net (2001:470:0:298::1)  28.072 ms  27.406 ms  26 ms
5  10gigabitethernet4-1.core1.den1.he.net (2001:470:0:293::2)  49.278 ms  49.974 ms  50.028 ms
6  10gigabitethernet13-5.core1.sjc2.he.net (2001:470:0:1b4::1)  80.509 ms  77.443 ms  77.777 ms
7  10gigabitethernet5-2.core1.pao1.he.net (2001:470:0:32::2)  79.52 ms  78.137 ms  78.489 ms
8  * * *
9  * * *
10  * * *
11  * * *
12  * * *



Routing to England via the West coast also seems suboptimal  ;D

[broquea]

http://bgp.he.net/AS51377

Single homed behind Cogent. The same Cogent who doesn't peer with HE or buy transit from anyone :) Enjoy the limited IPv6 connectivity!

Looks like they even took down all their peering/transits, going down from 16 to 1.

[johnpeach]

time to move that server I guess.....

[kasperd]

Single homed behind Cogent. The same Cogent who doesn't peer with HE or buy transit from anyone

I am curious about the reasons. I just tested from a few other networks, and all of them could reach 2a02:21a8:1:252::c9d6:9fdc.

Looks like they even took down all their peering/transits, going down from 16 to 1.

I have seen a different provider go from 1 to 0. They are still advertising IPv6 support on their website (dual stack with the IPv6 address in a range that is no longer advertised in BGP.)

[johnpeach]

I know Cogent's reputation perfectly well and would not have gone with an option that was single-homed through them had I bothered checking. I have a ticket open with Burstnet that has been raised to engineering to resolve; I'm interested to see what kind of an answer they come up with  ;D In the meantime, I have found a provider in London who are not single-homed and even have HE as one of their IPv6 peers....

[plugwash]

I am curious about the reasons. I just tested from a few other networks, and all of them could reach 2a02:21a8:1:252::c9d6:9fdc.

AIUI HE think of themselves as an "IPv6 tier 1" and as such refuse to buy IPv6 transit from anyone (they do buy IPv4 transit).

I don't believe cogent have released a public position on their relationship to HE but I strongly suspect they see HE as a relatively small provider who is trying to use their early adoption of IPv6 to bully their way up the ISP pecking order.

http://www.datacenterknowledge.com/archives/2009/10/22/peering-disputes-migrate-to-ipv6/