[118021] in North American Network Operators' Group
RE: Invalid prefix announcement from AS9035 for 129.77.0.0/16
daemon@ATHENA.MIT.EDU (Andrew Nusbaum)
Fri Oct 9 10:29:31 2009
From: Andrew Nusbaum <Andrew.Nusbaum@mindspark.com>
To: Dylan Ebner <dylan.ebner@crlmed.com>, Jim Cowie <cowie@renesys.com>, Adam
Kennedy <akennedy@cyberlinktech.com>
Date: Fri, 9 Oct 2009 10:27:08 -0400
In-Reply-To: <017265BF3B9640499754DD48777C3D20664ECB076B@MBX9.EXCHPROD.USA.NET>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Usually I get alerts from BGPMon within about 20 minutes of an event being =
detected. Not so much with the event this morning. I'm guessing that the =
orgination of 86,747 prefixes from the wrong AS probably got their MTA pret=
ty busy...
-----Original Message-----
From: Dylan Ebner [mailto:dylan.ebner@crlmed.com]=20
Sent: Friday, October 09, 2009 10:23 AM
To: Jim Cowie; Adam Kennedy
Cc: NANOG
Subject: RE: Invalid prefix announcement from AS9035 for 129.77.0.0/16
Does anyone know why it takes BGPMon so long to send out an email. It looks=
like it BGPMon detected the AS9035 announcements at the right time (around=
7:00 UTC) but I didn't get a notification until around 13:00 UTC. It seems=
like many people rely on BGPMon to do this type of detection, so the long =
delay is frustrating.
Thanks=20
Dylan Ebner
