I emailed about this to friends at HE yesterday. Heard they are working on it.
I can see forwward as well as reverse paths via Europe - so very likely they lost connectivity/BGP session with Level3 in US or something like that. Let's see how it goes. On Thu, Apr 12, 2012 at 9:46 AM, Derek Ivey <de...@derekivey.com> wrote: > I'm seeing the same thing from my area (Harrisburg, PA). Strange. > > *Show Level 3 (Harrisburg, PA) Traceroute to www.he.net* > 1 > vl-17.car1.Pittsburgh3.Level3.**net<http://vl-17.car1.Pittsburgh3.Level3.net>(2001:1900:35::21) > 208 msec 200 msec 276 msec > 2 > vl-4044.car1.Washington1.**Level3.net<http://vl-4044.car1.Washington1.Level3.net>(2001:1900:4:1::2B9) > 48 msec 208 msec 200 msec > 3 > vl-4083.car2.Washington1.**Level3.net<http://vl-4083.car2.Washington1.Level3.net>(2001:1900:4:1::DE) > 200 msec 312 msec 104 msec > 4 > vl-4061.car1.NewYork2.Level3.**net<http://vl-4061.car1.NewYork2.Level3.net>(2001:1900:4:1::106) > 160 msec 100 msec 124 msec > 5 > vl-4041.car1.NewYork1.Level3.**net<http://vl-4041.car1.NewYork1.Level3.net>(2001:1900:4:1::101) > 80 msec 156 msec 56 msec > 6 > vl-4086.edge3.London1.Level3.**net<http://vl-4086.edge3.London1.Level3.net>(2001:1900:6:1::11) > 212 msec 116 msec 248 msec > 7 > vl-4081.edge4.London1.Level3.**net<http://vl-4081.edge4.London1.Level3.net>(2001:1900:5:1::106) > 200 msec > > vl-4081.edge3.London1.Level3.**net<http://vl-4081.edge3.London1.Level3.net>(2001:1900:5:1::102) > 200 msec 204 msec > 8 2001:1900:5:3::11E 208 msec 204 msec 208 msec > 9 > 10gigabitethernet7-4.core1.**nyc4.he.net<http://10gigabitethernet7-4.core1.nyc4.he.net>(2001:470:0:128::1) > 204 msec 40 msec 200 msec > 10 > 10gigabitethernet5-3.core1.**lax1.he.net<http://10gigabitethernet5-3.core1.lax1.he.net>(2001:470:0:10E::1) > 408 msec 404 msec 260 msec > 11 > 10gigabitethernet7-4.core1.**fmt2.he.net<http://10gigabitethernet7-4.core1.fmt2.he.net>(2001:470:0:18D::1) > 368 msec 380 msec 416 msec > 12 > 10gigabitethernet2-1.core1.**fmt1.he.net<http://10gigabitethernet2-1.core1.fmt1.he.net>(2001:470:0:2D::1) > 256 msec 400 msec 224 msec > > C:\Users\Derek>tracert 2001:1900:35::21 (from my HE tunnel) > > Tracing route to > vl-17.car1.Pittsburgh3.Level3.**net<http://vl-17.car1.Pittsburgh3.Level3.net>[2001:1900:35::21] > over a maximum of 30 hops: > ... > 3 16 ms 14 ms 21 ms gige-g4-12.core1.ash1.he.net[2001:470:0:90::1] > 4 25 ms 25 ms 24 ms > 10gigabitethernet1-2.core1.**nyc4.he.net<http://10gigabitethernet1-2.core1.nyc4.he.net>[2001:470:0:36::2] > 5 88 ms 90 ms 98 ms > 10gigabitethernet1-2.core1.**lon1.he.net<http://10gigabitethernet1-2.core1.lon1.he.net>[2001:470:0:128::2] > 6 88 ms 89 ms 89 ms > ge-5-3-2.edge4.London.Level3.**net<http://ge-5-3-2.edge4.London.Level3.net>[2001:1900:5:3::11d] > 7 88 ms 89 ms 89 ms > vl-4080.edge4.London1.Level3.**net<http://vl-4080.edge4.London1.Level3.net>[2001:1900:5:1::105] > 8 158 ms 158 ms 158 ms > vl-4086.car1.NewYork1.Level3.**net<http://vl-4086.car1.NewYork1.Level3.net>[2001:1900:6:1::12] > 9 163 ms 163 ms 163 ms > ae-2-4047.edge2.Washington12.**Level3.net<http://ae-2-4047.edge2.Washington12.Level3.net>[2001:1900:4:1::3b9] > 10 163 ms 163 ms 163 ms > ae-1-4080.edge1.Washington12.**Level3.net<http://ae-1-4080.edge1.Washington12.Level3.net>[2001:1900:4:1::3d9] > 11 164 ms 164 ms 164 ms > vl-4046.car1.Washington1.**Level3.net<http://vl-4046.car1.Washington1.Level3.net>[2001:1900:4:1::3b2] > 12 177 ms 177 ms 187 ms > vl-17.car1.Pittsburgh3.Level3.**net<http://vl-17.car1.Pittsburgh3.Level3.net>[2001:1900:35::21] > > Trace complete. > > > > On 4/12/2012 12:08 AM, Dave Sotnick wrote: > >> Hello Nanog, >> >> Looks like Level3's only IPv6 route to HE is via London right now: >> >> Show Level 3 (Las Vegas, NV) Traceroute to www.he.net >> 1 vl-5.bar1.LasVegas1.Level3.net (2001:1900:2F::1) 0 msec 0 msec 0 msec >> 2 >> vl-11.bar2.LasVegas1.Level3.**net<http://vl-11.bar2.LasVegas1.Level3.net>(2001:1900:4:1::3C6) >> 0 msec 0 msec 0 msec >> 3 >> vl-4045.car1.Denver1.Level3.**net<http://vl-4045.car1.Denver1.Level3.net>(2001:1900:4:1::276) >> 84 msec 228 >> msec 224 msec >> 4 >> vl-4081.car2.Denver1.Level3.**net<http://vl-4081.car2.Denver1.Level3.net>(2001:1900:4:1::32) >> 20 msec 20 msec 20 msec >> 5 >> vl-4042.edge1.Chicago2.Level3.**net<http://vl-4042.edge1.Chicago2.Level3.net>(2001:1900:4:1::36) >> 44 msec 44 msec 44 msec >> 6 >> vl-4067.car1.Chicago1.Level3.**net<http://vl-4067.car1.Chicago1.Level3.net>(2001:1900:4:1::1D) >> 48 msec 212 >> msec 224 msec >> 7 >> vl-4061.car2.NewYork2.Level3.**net<http://vl-4061.car2.NewYork2.Level3.net>(2001:1900:4:1::22) >> 184 msec 216 >> msec 232 msec >> 8 >> vl-4080.car1.NewYork2.Level3.**net<http://vl-4080.car1.NewYork2.Level3.net>(2001:1900:4:1::F1) >> 80 msec 80 msec 80 msec >> 9 >> vl-4041.car1.NewYork1.Level3.**net<http://vl-4041.car1.NewYork1.Level3.net>(2001:1900:4:1::101) >> 80 msec 80 msec 80 msec >> 10 >> vl-4086.edge3.London1.Level3.**net<http://vl-4086.edge3.London1.Level3.net>(2001:1900:6:1::11) >> 176 msec 144 >> msec 164 msec >> 11 >> vl-4081.edge3.London1.Level3.**net<http://vl-4081.edge3.London1.Level3.net>(2001:1900:5:1::102) >> 136 msec 132 msec >> >> vl-4081.edge4.London1.Level3.**net<http://vl-4081.edge4.London1.Level3.net>(2001:1900:5:1::106) >> 148 msec >> 12 2001:1900:5:3::11E 160 msec 156 msec 160 msec >> 13 >> 10gigabitethernet7-4.core1.**nyc4.he.net<http://10gigabitethernet7-4.core1.nyc4.he.net>(2001:470:0:128::1) >> 344 >> msec 208 msec 200 msec >> 14 >> 10gigabitethernet5-3.core1.**lax1.he.net<http://10gigabitethernet5-3.core1.lax1.he.net>(2001:470:0:10E::1) >> 276 >> msec 260 msec 268 msec >> 15 >> 10gigabitethernet7-4.core1.**fmt2.he.net<http://10gigabitethernet7-4.core1.fmt2.he.net>(2001:470:0:18D::1) >> 272 >> msec 272 msec 324 msec >> 16 >> 10gigabitethernet2-1.core1.**fmt1.he.net<http://10gigabitethernet2-1.core1.fmt1.he.net>(2001:470:0:2D::1) >> 288 msec >> 272 msec 276 msec >> 17 * * * >> 18 * * * >> >> Confirmed by L3's looking glasses ( >> http://lg.level3.net/**traceroute/traceroute.cgi?** >> site=lvg1&target=www.he.net&**ipv6=true<http://lg.level3.net/traceroute/traceroute.cgi?site=lvg1&target=www.he.net&ipv6=true> >> ) and my own corporate IPv6 connection from Level 3. >> >> I opened a ticket with Level 3. Anyone else seen this? >> >> -Dave >> >> > -- Anurag Bhatia anuragbhatia.com or simply - http://[2001:470:26:78f::5] if you are on IPv6 connected network! Twitter: @anurag_bhatia <https://twitter.com/#!/anurag_bhatia> Linkedin: http://linkedin.anuragbhatia.com