Level3 IPv6 peering with HE only in London?

Anurag Bhatia me at anuragbhatia.com
Thu Apr 12 10:54:35 CDT 2012


Yes it is.

You can cross check via looking glass of both networks.

(Sent from my mobile device)

Anurag Bhatia
http://anuragbhatia.com
On Apr 12, 2012 9:23 PM, "Christian de Larrinaga" <cdel at firsthand.net>
wrote:

> v6 traffic picking up through L3/HE?
> /C
> On 12 Apr 2012, at 16:35, Dave Sotnick wrote:
>
> > Yep, looks much better now.
> >
> > This is what Level3 had to say:
> >
> > "David,
> >
> > You should see this repaired at this time, looks like the peering
> > between L3 and HE crashed in
> > stateside when the ipv6 max prefix limits exceeded the router
> configurations.
> >
> > Please let us know if any further questions.
> >
> > Regards,
> >
> > Level 3 Communications"
> >
> > Thanks all,
> > -Dave
> >
> > On Wed, Apr 11, 2012 at 11:37 PM, Mike Leber <mleber at he.net> wrote:
> >> Was fixed a short while ago, please retest.
> >>
> >> Mike.
> >>
> >>
> >> On 4/11/12 9:08 PM, 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 (2001:1900:4:1::3C6) 0 msec 0 msec
> 0
> >>> msec
> >>>  3 vl-4045.car1.Denver1.Level3.net (2001:1900:4:1::276) 84 msec 228
> >>> msec 224 msec
> >>>  4 vl-4081.car2.Denver1.Level3.net (2001:1900:4:1::32) 20 msec 20
> msec 20
> >>> msec
> >>>  5 vl-4042.edge1.Chicago2.Level3.net (2001:1900:4:1::36) 44 msec 44
> msec
> >>> 44 msec
> >>>  6 vl-4067.car1.Chicago1.Level3.net (2001:1900:4:1::1D) 48 msec 212
> >>> msec 224 msec
> >>>  7 vl-4061.car2.NewYork2.Level3.net (2001:1900:4:1::22) 184 msec 216
> >>> msec 232 msec
> >>>  8 vl-4080.car1.NewYork2.Level3.net (2001:1900:4:1::F1) 80 msec 80
> msec 80
> >>> msec
> >>>  9 vl-4041.car1.NewYork1.Level3.net (2001:1900:4:1::101) 80 msec 80
> msec
> >>> 80 msec
> >>>  10 vl-4086.edge3.London1.Level3.net (2001:1900:6:1::11) 176 msec 144
> >>> msec 164 msec
> >>>  11 vl-4081.edge3.London1.Level3.net (2001:1900:5:1::102) 136 msec 132
> >>> msec
> >>>    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 (2001:470:0:128::1) 344
> >>> msec 208 msec 200 msec
> >>>  14 10gigabitethernet5-3.core1.lax1.he.net (2001:470:0:10E::1) 276
> >>> msec 260 msec 268 msec
> >>>  15 10gigabitethernet7-4.core1.fmt2.he.net (2001:470:0:18D::1) 272
> >>> msec 272 msec 324 msec
> >>>  16 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
> >>> ) and my own corporate IPv6 connection from Level 3.
> >>>
> >>> I opened a ticket with Level 3. Anyone else seen this?
> >>>
> >>> -Dave
> >>>
> >>
> >
>
>
>


More information about the NANOG mailing list