[152019] in North American Network Operators' Group

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

RE: The day SORBS goes away ...

daemon@ATHENA.MIT.EDU (Nathan Eisenberg)
Mon Apr 9 13:49:09 2012

From: Nathan Eisenberg <nathan@atlasnetworks.us>
To: NANOG list <nanog@nanog.org>
Date: Mon, 9 Apr 2012 17:48:03 +0000
In-Reply-To: <20120409170514.GC6643@dan.olp.net>
X-Envelope-From: nathan@atlasnetworks.us
X-MDaemon-Deliver-To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

> Our ARIN allocation is:
>=20
> 67.217.144.0/20
>=20
> and SORBS had us listed within a larger black listed range, like the
> containing /12. It took us weeks to be removed from that range (or to
> have
> an exception added). This was probably a couple of years ago, or early
> last
> year.

Our experience with their DUHL was very similar, and around the same time. =
 My post to NANOG about it is here:
http://mailman.nanog.org/pipermail/nanog/2011-June/037568.html

Despite the only public reply being utterly unhelpful, the post resulted in=
 human contact from SORBs and an eventual resolution of the issue.  I have =
observed this pattern repeated several times on-list since then (and severa=
l times prior to my post), so it would seem that posting to NANOG is (or, a=
t that time, was) part of their delisting process.

Nathan Eisenberg



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