...
-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
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
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
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
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
We also received a notification that our IP block 67.135.55.0/24 (AS19629) is
being annouced by AS9035. Hopefully someone is receiving my emails.
Thanks
Dylan Ebner, Network Engineer
Consulting Radiologists, Ltd.
1221 Nicollet Mall, Minneapolis, MN 55403
ph. 612.573.2236 fax. 612.573.2250
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
We are seeing the same ting with 66.146.192.0/19 66.251.224.0/19.
According to cyclopes this is still continuing. . .
Dylan Ebner wrote:
We also received a notification that our IP block 67.135.55.0/24 (AS19629) is
being annouced by AS9035. Hopefully someone is receiving my emails.
Thanks
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
I just received confirmation from AS9035 that they are not annoucing my IP
block.
Dylan Ebner, Network Engineer
-Original Message-
From: sjk [mailto:s...@sleepycatz.com]
Sent: Friday, October 09, 2009 9:20 AM
Cc: nanog@nanog.org
Subject: Re: Invalid prefix announcement from AS9035
[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
...@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 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
Message-
From: Andrew Nusbaum [mailto:andrew.nusb...@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
14 matches
Mail list logo
