[192749] in North American Network Operators' Group
Autunomous system filtering?
daemon@ATHENA.MIT.EDU (=?utf-8?Q?Giuseppe_Span=C3=B2_-_Da)
Fri Nov 18 13:05:31 2016
X-Original-To: nanog@nanog.org
From: =?utf-8?Q?Giuseppe_Span=C3=B2_-_Datacast_Srl?= <spano@datacast.it>
Date: Fri, 18 Nov 2016 19:04:33 +0100
To: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
Hi!
We are experiencing a strange issue with announcements from our =
AS207029.
On Sept. 16th we began to announce our prefixes 185.85.20.0/22 through =
our upstream provider AS28716 (E-Planet). Everything worked correctly.
Suddenly during the night between 17th and 18th Sept. the visibility of =
those prefixes dropped heavily (source: ripe stats) and we began =
experiencing big issues with our customers. We decided then to =
differentiate the announcements as it follows:
AS2876 announces 185.85.20.0/23
AS207029 announces 185.85.22.0/23 (those prefixes are idle at the =
moment)
essentially we split the /22 into two /23 so to keep monitored our AS =
propagation.
What=E2=80=99s happening is interesting:
prefixes announced by AS2876 are regularly spread everywhere, those =
announced by AS207029 not.
For example, we can see network 185.85.22.0/23 from HE looking glasses, =
but we cannot see it into Cogent, Level3 or Split looking glasses.
It seems an AS filtering is acting somewhere, and this looks a bit weird =
to me.
Did this ever happen to any of you? Do you have ideas?
Our upstream provider (that owns peering sessions with all the above =
providers) opened tickets to them, but if Network Engineers from Cogent, =
Level3 or Split should be reading this, could they kindly have a look =
into their filter configurations?
Thank you to all of you for your kind attention.
Regards,
Giuseppe Span=C3=B2 - Datacast Srl
spano@datacast.it
