Re: Getting an RADB entry removed that was added by a previous peer

2017-09-14 Thread João Butzke 

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: *n...@relianceglobalcom.com*
mnt-by: MAINT-AS6517
changed: *j...@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?

Re: Getting an RADB entry removed that was added by a previous peer

2017-09-13 Thread Sandra Murphy 
Job should also have pointed to http://irrexplorer.nlnog.net (notes "Created by 
Job Snijders").  It notes multiple route objects (e.g., 
http://irrexplorer.nlnog.net/search/129.77.0.0/16).  IMHO, worth a look or two 
from time to time for one’s own resources.

—Sandy


> On Sep 13, 2017, at 7:10 AM, Job Snijders  wrote:
> 
> On Wed, 13 Sep 2017 at 13:08, Matthew Huff  wrote:
> 
>> 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?
>> 
> Easy! Email radb-supp...@merit.edu for assistance.
> 
> Kind regards,
> 
> Job

Re: Getting an RADB entry removed that was added by a previous peer

2017-09-13 Thread Job Snijders 
On Wed, 13 Sep 2017 at 13:08, Matthew Huff  wrote:

> 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?
>
Easy! Email radb-supp...@merit.edu for assistance.

Kind regards,

Job

Getting an RADB entry removed that was added by a previous peer

2017-09-13 Thread Matthew Huff 
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?