nanog mailing list archives
Re: Getting an RADB entry removed that was added by a previous peer
From: João Butzke <lista-gter () tbonet net br>
Date: Wed, 13 Sep 2017 08:25:13 -0300
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?
Current thread:
- Getting an RADB entry removed that was added by a previous peer Matthew Huff (Sep 13)
- Re: Getting an RADB entry removed that was added by a previous peer Job Snijders (Sep 13)
- Re: Getting an RADB entry removed that was added by a previous peer Sandra Murphy (Sep 13)
- Re: Getting an RADB entry removed that was added by a previous peer João Butzke (Sep 14)
- Re: Getting an RADB entry removed that was added by a previous peer Job Snijders (Sep 13)