Bell Canada outage?

Zachary McGibbon zachary.mcgibbon+nanog at gmail.com
Wed Aug 8 15:10:22 CDT 2012


Thanks for the info, looks like Bell needs to put some filtering on their
customer links!

Things seem to have calmed down now but I'm still watching my prefixes
received from my upstream provider:

while true; do snmpget -v2c -c <community>
<router> 1.3.6.1.4.1.9.9.187.1.2.4.1.1.<ip of bgp peer>.1.128; sleep 1; done

I also monitor all my prefixes and bgp messages in Cacti

On Wed, Aug 8, 2012 at 3:50 PM, Andree Toonk <andree+nanog at toonk.nl> wrote:

> Hi,
>
> .-- My secret spy satellite informs me that at 12-08-08 11:35 AM  Darius
> Jahandarie wrote:
> > On Wed, Aug 8, 2012 at 2:31 PM, Zachary McGibbon
> > <zachary.mcgibbon+nanog at gmail.com> wrote:
> >> Anyone at Bell Canada / Sympatico can tell us what's going on?  Our
> routing
> >> table is going nuts with Bell advertising a lot of routes they
> shouldn't be
> >
> > Bell leaked a full table. To add to the fun, it seems that TATA took
> > the full table and releaked it.
>
> A quick analysis leads met to believe AS46618 ( Dery Telecom Inc) is the
> cause of this. AS46618 is dual homed to VIDEOTRON and Bell. What seems
> to have happened is that they leaked routes learned from VIDEOTRON to Bell.
>
> Based on BGP data I see that at 17:27 UTC  AS46618 ( Dery Telecom Inc)
> started to leak a 'full table', or at least a significant chunk of it to
> its provider Bell AS577.
> Bell propagated that to it's peers. Tata was one of the ones that
> accepted all of that.
>
> I can see that Bell propagated at least 74,109 prefixes learned from
> AS46618 to Tata. Tata selected 70,160 of those routes.
>
>
> Cheers,
>  Andree
>
>
>
>
>
>
>
>


More information about the NANOG mailing list