[195375] in North American Network Operators' Group
Re: Multicom Hijacks: Do you peer with these turkeys (AS35916)?
daemon@ATHENA.MIT.EDU (Jima)
Fri Aug 4 09:15:55 2017
X-Original-To: nanog@nanog.org
To: nanog@nanog.org
From: Jima <nanog@jima.us>
Date: Fri, 4 Aug 2017 07:15:44 -0600
In-Reply-To: <3a6c4f25-7208-ef62-961a-b0153a833d42@jima.us>
Errors-To: nanog-bounces@nanog.org
Oops, following up a bit late.
I was told yesterday that AS209 blocked their acceptance of
163.198.0.0/16 from AS35916 based on a number of complaints, which
unfortunately left a path via their peering with NTT (which I presume
they can't filter for $reasons). But then a short time later AS35916
withdrew the announcement entirely, possibly because of the traffic
engineering implications of that filtering (not sure).
Short-term, it's a win, but long-term we may not have seen the last of
this prefix.
Jima
On 2017-08-03 06:24, Jima wrote:
> A few years back, Ronald named-and-shamed my work's new carrier for
> facilitating a prefix hijacker on this very list. As luck would have it,
> I had a fresh, crisp business card from our sales rep, so I passed the
> (quite legitimate) grievance along, and a short time later, the hijacked
> prefixes had one less upstream.
>
> Years later now, I have a different job, and a circuit with AS209. I'll
> see if I can't scare someone up (if it's still active by the time I get
> into the office).
>
> Thanks Ronald. Rest assured that many of us remember. :-)
