RE: Invalid prefix announcement from AS9035 for 129.77.0.0/16

[Andrew Nusbaum]

I actually got origin change alerts from Cyclops about 2 minutes after the announcements started. 
-Andy

-----Original Message-----
From: Dylan Ebner [mailto:dylan.ebner@crlmed.com] 
Sent: Friday, October 09, 2009 10:31 AM
To: Andrew Nusbaum; Jim Cowie; Adam Kennedy
Cc: NANOG
Subject: RE: Invalid prefix announcement from AS9035 for 129.77.0.0/16

I thought that may be the case as well. Do people know of other services like BGPMon that may be able to keep up with the load better? Does anyone know how cyclops faired this morning with the additional load?
 


Dylan Ebner


-----Original Message-----
From: Andrew Nusbaum [mailto:Andrew.Nusbaum@mindspark.com] 
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 pretty 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 


Dylan Ebner