We saw disconnections to Comcast via HE, A subnet was announced with a
bogus path.
-- During the problem --
98.224.0.0/11 via 162.11.22.209 on vlan500 [ibgp_border 12:09:48
from 162.11.22.212] * (100/15) [AS65021i]
Type: BGP unicast univ
BGP.origin: IGP
BGP.as_path: 6939 200759 65021
BGP.next_hop: 184.5.5.69
BGP.local_pref: 100
-- Returned to normal --
98.192.0.0/10 via 162.11.22.209 on vlan500 [ibgp_border
2016-03-17 from 162.11.22.212] (100/15) [AS7922i]
Type: BGP unicast univ
BGP.origin: IGP
BGP.as_path: 6939 7922
BGP.next_hop: 184.5.5.69
BGP.local_pref: 100
On Fri, Apr 22, 2016 at 12:22 PM, Ken Chase <m...@sizone.org> wrote:
> and of course the second I post it all fixes itself. NANOG works! Thanks!
>
> (was going on for about 10-15 min)
>
> On Fri, Apr 22, 2016 at 01:21:47PM -0400, Ken Chase said:
> >
> >From toronto - something odd - mtr to google.com (google.com
> (172.217.3.142))
> >
> > 5. v638.core1.tor1.he.net
> > 6. 100ge7-2.core1.nyc4.he.net
> > 7. 100ge11-1.core1.par2.he.net
> > 8. 10ge3-2.core1.zrh1.he.net
> > 9. ???
> >
> >par is paris, zrh is zurich?
> >
> >same base path for hitting my EC2 nodes... Cant imagine this is just
> affecting Toronto
> >HE customers.
> >
> >EC2 node is in 107.20/14
> >
> >/kc
>
> /kc
