Re: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-10 Thread Christopher Morrow
... -Chris -Andy -Original Message- From: Dylan Ebner [mailto:dylan.eb...@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

Re: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-10 Thread ML
Matthew Huff wrote: About 4 hours ago BGPmon picked up a rogue announcement of 129.77.0.0 from AS9035 (ASN-WIND Wind Telecomunicazioni spa) with an upstream of AS1267 (ASN-INFOSTRADA Infostrada S.p.A.). I don't see it now on any looking glass sites. Hopefully this was just a typo that was

Re: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-10 Thread christian
On Sat, Oct 10, 2009 at 4:24 PM, ML m...@kenweb.org wrote: Matthew Huff wrote: About 4 hours ago BGPmon picked up a rogue announcement of 129.77.0.0 from AS9035 (ASN-WIND Wind Telecomunicazioni spa) with an upstream of AS1267 (ASN-INFOSTRADA Infostrada S.p.A.). I don't see it now on any

Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-09 Thread Matthew Huff
About 4 hours ago BGPmon picked up a rogue announcement of 129.77.0.0 from AS9035 (ASN-WIND Wind Telecomunicazioni spa) with an upstream of AS1267 (ASN-INFOSTRADA Infostrada S.p.A.). I don't see it now on any looking glass sites. Hopefully this was just a typo that was quickly corrected. I

Re: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-09 Thread Wouter Prins
Hi Matthew, You are not the only one having this issue. They are announcing some other prefixes as well! 2009/10/9 Matthew Huff mh...@ox.com About 4 hours ago BGPmon picked up a rogue announcement of 129.77.0.0 from AS9035 (ASN-WIND Wind Telecomunicazioni spa) with an upstream of AS1267

Re: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-09 Thread Adam Kennedy
Agreed. Our prefixes at AS40060 were announced as well. I received a notification around 7:00am EDT that our prefixes were detected announced from AS9035 with the same upstream AS1267. On 10/9/09 8:34 AM, Wouter Prins w...@null0.nl wrote: Hi Matthew, You are not the only one having this

RE: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-09 Thread Dylan Ebner
dylan.eb...@crlmed.com www.consultingradiologists.com -Original Message- From: Matthew Huff [mailto:mh...@ox.com] Sent: Friday, October 09, 2009 7:28 AM To: nanog@nanog.org Subject: Invalid prefix announcement from AS9035 for 129.77.0.0/16 About 4 hours ago BGPmon picked up a rogue

Re: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-09 Thread Jim Cowie
Lots of people were affected, but none significantly. They originated 86,747 networks very briefly (less than a minute at 7:23 UTC), and I don't think anyone outside Telecom Italia's customer cone even saw them. So the impact was really, really limited. The correct origins were being

Re: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-09 Thread sjk
, October 09, 2009 7:28 AM To: nanog@nanog.org Subject: Invalid prefix announcement from AS9035 for 129.77.0.0/16 About 4 hours ago BGPmon picked up a rogue announcement of 129.77.0.0 from AS9035 (ASN-WIND Wind Telecomunicazioni spa) with an upstream of AS1267 (ASN-INFOSTRADA Infostrada S.p.A

RE: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-09 Thread Dylan Ebner
the long delay is frustrating. Thanks Dylan Ebner -Original Message- From: Jim Cowie [mailto:co...@renesys.com] Sent: Friday, October 09, 2009 9:11 AM To: Adam Kennedy Cc: NANOG Subject: Re: Invalid prefix announcement from AS9035 for 129.77.0.0/16 Lots of people were affected, but none

RE: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-09 Thread Dylan Ebner
: Friday, October 09, 2009 7:28 AM To: nanog@nanog.org Subject: Invalid prefix announcement from AS9035 for 129.77.0.0/16 About 4 hours ago BGPmon picked up a rogue announcement of 129.77.0.0 from AS9035 (ASN-WIND Wind Telecomunicazioni spa) with an upstream of AS1267 (ASN-INFOSTRADA

RE: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-09 Thread Andrew Nusbaum
[mailto:dylan.eb...@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

RE: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-09 Thread Dylan Ebner
...@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

Re: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-09 Thread christian
this type of detection, so the long delay is frustrating. Thanks Dylan Ebner -Original Message- From: Jim Cowie [mailto:co...@renesys.com] Sent: Friday, October 09, 2009 9:11 AM To: Adam Kennedy Cc: NANOG Subject: Re: Invalid prefix announcement from AS9035 for 129.77.0.0/16 Lots

RE: Invalid prefix announcement from AS9035 for 129.77.0.0/16

2009-10-09 Thread Andrew Nusbaum
: 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