Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 02 Oct 1998 15:27:19 -0700
From:      Graeme Tait <graeme@echidna.com>
To:        Graphic Rezidew <rezidew@kemicol.rezidew.net>
Cc:        freebsd-isp@FreeBSD.ORG
Subject:   Re: t-1 from whom?
Message-ID:  <36155347.63A2@echidna.com>
References:  <199810021449.JAA06468@kemicol.rezidew.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Graphic Rezidew wrote:
> 
> Hi, I run a network over my dual channel ISDN connection to do some shell,
> mail, and web-serving. As one would imagine, I am saturating my bandwidth.
> I have decided to get a T-1 and am considering service from AT-WORK (a
> company affiliated with AT-HOME, the cable modem people). The price is
> quite fair $1000/mo for a line that is basicly only restricting me from
> providing dial-up, based on the terms of usage doc.
>  The Thing that concerns me is that their network is so NEW...I am
> wondering if they have clean through put to the rest of the internet.
> 
> If anyone uses them Please let me know what your experience has been.
> 
> NOTE: I am not interested in hearing about how swell your cable modem is.
>       I am not signing up for cable modem service. This will be a real
>       T-1 on a network seperate from AT-HOME.


You don't say what region you are in. We seriously considered getting T-1 
into our NYC office before deciding to go with colocation instead. One of 
the T-1 candidates was @home - their price was good, but we got nervous 
about their quality.

Please don't read this as a condemnation of them, as the evidence is too 
slim, but you could consider it a red flag. We had a client with partial T-1 
from @home into their NYC office. I tried accessing their webserver from 
various points external to @home's network. I was not satisfied with the 
results, in particular it looked like there might be problems with their 
peering into particular networks. The same networks worked fine with Exodus, 
NJ (one of our colo candidates). But about this time the @home issue became 
moot at we switched our focus to colo.

Ask @home for a list of clients that are connected via whatever point you 
will be. Access (http, ping, traceroute) those clients webservers, etc. from 
a variety of ISP's, etc. You might also want to ask @home for specific 
details of their network and headroom policies.


-- 
Graeme Tait - Echidna

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36155347.63A2>