[195807] in North American Network Operators' Group
Re: Getting an RADB entry removed that was added by a previous peer
daemon@ATHENA.MIT.EDU (=?UTF-8?Q?Jo=c3=a3o_Butzke?=)
Sat Sep 16 04:43:27 2017
X-Original-To: nanog@nanog.org
To: nanog@nanog.org
From: =?UTF-8?Q?Jo=c3=a3o_Butzke?= <lista-gter@tbonet.net.br>
Date: Wed, 13 Sep 2017 08:25:13 -0300
In-Reply-To: <17b2db517ab5409699ddb5b8cfed72a0@ox.com>
Errors-To: nanog-bounces@nanog.org
You tried the contact on the whois database?
route: 129.77.0.0/16
descr: NYC-OTA LIMITED PARTNERSHIP-AS14607 (added by MAINT-AS6517)
origin: AS6517
remarks: -------------------------------------------------
remarks: - This route object was registered by -
remarks: - Reliance Globalcom Services, Inc MAINT-AS6517 -
remarks: - on behalf of their customer: -
remarks: - NYC-OTA LIMITED PARTNERSHIP-AS14607 NYC -
remarks: -------------------------------------------------
notify: *noc@relianceglobalcom.com*
mnt-by: MAINT-AS6517
changed: *jkim@relianceglobalcom.com* 20091117
source: RADB
Best Regards, João Butzke.
Em 13/09/2017 08:05, Matthew Huff escreveu:
> It appears that Reliance Globalcom (AS6157) added an RADB entry for our prefix (129.77.0.0/16) when we were a peer of theirs years ago, and it was never removed when we ended the relationship. We are ASN 14607.
>
> I've reached out to their support, but does anyone have a suggestion on how I could get this cleaned up if they don't respond?
