[122512] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: AS16387 leaking routes

daemon@ATHENA.MIT.EDU (Christopher Morrow)
Mon Feb 15 21:20:19 2010

In-Reply-To: <F0FF60999EF88B46A51094F8D4E537E330E88A04@itexbe12.uom.memphis.edu>
Date: Mon, 15 Feb 2010 21:19:44 -0500
From: Christopher Morrow <morrowc.lists@gmail.com>
To: "Ernest Andrew McCracken (emccrckn)" <emccrckn@memphis.edu>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Mon, Feb 15, 2010 at 6:13 PM, Ernest Andrew McCracken (emccrckn)
<emccrckn@memphis.edu> wrote:
> There are other ASN changes as well as from other peers. Here are some just a few minutes old.
>
> Date|Time|timestamp|Peer IP|Peer ASN|Event Description|Prefix|old AS|new AS
>
> 20100215|17:11:13|1266275473183|164.128.32.11|3303|ORIGIN_CHANGE|192.156.97/24|5651|16387

don't know what to tell ya... I only see 2 routes from 16387 in
routeviews or other places I can view routing info :( This isn't some
off-by-one error type thing in your collector code?

-Chris


home help back first fref pref prev next nref lref last post