[174237] in North American Network Operators' Group
Re: Prefix hijacking, how to prevent and fix currently
daemon@ATHENA.MIT.EDU (Tarun Dua)
Mon Sep 1 05:29:08 2014
X-Original-To: nanog@nanog.org
In-Reply-To: <CAEmG1=rGU=zzTXo8CWFua_AAp7vQ9UbkfH4nZTOqSgBuy5s0zA@mail.gmail.com>
Date: Mon, 1 Sep 2014 14:58:58 +0530
From: Tarun Dua <lists@tarundua.net>
To: Matthew Petach <mpetach@netflight.com>
Cc: Doug Madory <dmadory@renesys.com>, nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
Would it not help if RIPE un-publishes these ASN's from their whois database ?
I filed the abuse report at RIPE but haven't heard back from them. We
are NOT a RIPE member but an APNIC member.
Regards
-Tarun
On Mon, Sep 1, 2014 at 3:49 AM, Matthew Petach <mpetach@netflight.com> wrote:
> On Sun, Aug 31, 2014 at 12:47 PM, Doug Madory <dmadory@renesys.com> wrote:
>
>> Ah yes BusinessTorg (AS60937). I have also seen this one doing what you
>> are describing. Not to MSFT or GOOG, but another major technology company
>> that we peer with. In fact, it is going on right now but only visible if
>> you receive routes directly from them. A while ago, I sent them a note
>> describing what was happening and suggested they might want to stop
>> accepting routes from that AS, but they still do.
>>
>
>
> Be aware that even if you don't think you're
> peering with them directly, you may be picking
> up routes via the public route servers at exchange
> points, so check to see if you need to apply
> filters on your route server peerings as well.
>
> Matt
