[195808] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

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

daemon@ATHENA.MIT.EDU (Sandra Murphy)
Sat Sep 16 04:52:44 2017

X-Original-To: nanog@nanog.org
From: Sandra Murphy <sandy@tislabs.com>
In-Reply-To: <CACWOCC-VHoR_TPoKLWQT97kRKhEURCh+4-VAC7zNEajf-yPNtQ@mail.gmail.com>
Date: Wed, 13 Sep 2017 11:21:47 -0400
To: Job Snijders <job@ntt.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>, Sandra Murphy <sandy@tislabs.com>
Errors-To: nanog-bounces@nanog.org

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=E2=80=99s own resources.

=E2=80=94Sandy


> On Sep 13, 2017, at 7:10 AM, Job Snijders <job@ntt.net> wrote:
>=20
> On Wed, 13 Sep 2017 at 13:08, Matthew Huff <mhuff@ox.com> wrote:
>=20
>> 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.
>>=20
>> 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?
>>=20
> Easy! Email radb-support@merit.edu for assistance.
>=20
> Kind regards,
>=20
> Job


home help back first fref pref prev next nref lref last post