[118023] in North American Network Operators' Group
RE: Invalid prefix announcement from AS9035 for 129.77.0.0/16
daemon@ATHENA.MIT.EDU (Dylan Ebner)
Fri Oct 9 10:34:36 2009
From: Dylan Ebner <dylan.ebner@crlmed.com>
To: Andrew Nusbaum <Andrew.Nusbaum@mindspark.com>, Jim Cowie
<cowie@renesys.com>, Adam Kennedy <akennedy@cyberlinktech.com>
Date: Fri, 9 Oct 2009 14:30:36 +0000
In-Reply-To: <7CC9F803BE7E0644A6219521B951AE38047A8DB549@s003mb01.staff.iaccap.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I thought that may be the case as well. Do people know of other services li=
ke BGPMon that may be able to keep up with the load better? Does anyone kno=
w how cyclops faired this morning with the additional load?
=20
Dylan Ebner
-----Original Message-----
From: Andrew Nusbaum [mailto:Andrew.Nusbaum@mindspark.com]=20
Sent: Friday, October 09, 2009 9:27 AM
To: Dylan Ebner; Jim Cowie; Adam Kennedy
Cc: NANOG
Subject: RE: Invalid prefix announcement from AS9035 for 129.77.0.0/16
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]
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
