[68754] in North American Network Operators' Group
RE: 2001:590::/32 announced by both AS4436 (nLayer) and AS4474 (Global Village, no contact in whois, but seems to be nLayer...)
daemon@ATHENA.MIT.EDU (Matthew Kaufman)
Tue Mar 16 11:53:01 2004
From: "Matthew Kaufman" <matthew@eeph.com>
To: "'william(at)elan.net'" <william@elan.net>,
"'Jeroen Massar'" <jeroen@unfix.org>
Cc: <nanog@merit.edu>
Date: Tue, 16 Mar 2004 08:52:07 -0800
In-Reply-To: <Pine.LNX.4.44.0403160725050.9972-100000@sokol.elan.net>
Errors-To: owner-nanog-outgoing@merit.edu
Brief history of AS 4436:=20
Scruz.net was founded in 1993, and incorporated about a year later.
AS 4436 was obtained in 1995 so that scruz.net could connect to MAE =
West.
Scruz.net was acquired in 1996 by Netsource Communications who =
continued
to operate scruz.net as a subsidiary.
Netsource Communications went bankrupt in 1997.
The scruz.net assets were purchased by Tycho Networks, Inc. =
(tycho.net)
in 1998.
Tycho.net added PAIX and PacBell NAP connections.
Tycho Networks was acquired in 1999 by DSL.net.
DSL.net added PAIX-VA, MAE ATM West, MAE ATM East, AADS NAP, and =
NYIIX
connections.
This month, DSL.net switched to an all-transit network model and the
peering assets (all NAP connections, associated routers, and the AS =
number)
were acquired by nLayer.
Authority/Disclaimer: I was a founder of scruz.net, a founder of =
tycho.net,
and am employed by DSL.net. You'll also note that I am the contact for =
the
'SCCI' OrgID. Some day all of the paperwork for the entire history will =
make
its way through ARIN, and AS 4436 will be under the nLayer OrgID and the
DSL.net IP addresses will be under the DSL.net OrgID. But I've learned =
to
not hold my breath while ARIN works.
Matthew Kaufman
matthew@eeph.com
> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On=20
> Behalf Of william(at)elan.net
>
> Why would nlayer be now using AS4436? It is listed as=20
> scruz.net, but as=20
> far as I remember scruz was taken overy by DSL.NET (I think that even=20
> included their peering agreements) and some of their ip block such as=20
> 204.139.8.0/21, 204.147.224.0/20 and others certainly seem to=20
> confirm that.
