As they say, your mileage may vary We have a 2xT1 that we pay $560
per month for, and the routing/peering at TW Telecom is good, but then
again, we are in the San Francisco Bay Area. If the building owners
would have let TW Telecom into this buildings MPOE's we would have a 10
meg fiber
[~]# wget http://208.65.55.55/dummy.zip
--07:49:09-- http://208.65.55.55/dummy.zip
= `dummy.zip'
Connecting to 208.65.55.55:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 63,375,843 (60M) [application/zip]
100%
[=
=
Personally, I wouldn't go with TW Telecom for bandwidth. They tend to
be overly pricy and their peering is too selective. In a case where
the city you are located in doesn't have good peering such as Orlando
you need to carefully select your upstream. In the case of TW Telecom,
they have
You're using Nlayer these days?
-Charles
-Original Message-
From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf
Of Matt Liotta
Sent: Friday, May 15, 2009 6:53 AM
To: sc...@brevardwireless.com; WISPA General List
Subject: Re: [WISPA] I need a few people to run
Since you replied onlist... Yes, nLayer is in our mix, but they only
get about 10% of our transit traffic. It helps being peered to 100s of
ASNs. ;)
-Matt
On May 15, 2009, at 3:23 PM, Charles Wu wrote:
You're using Nlayer these days?
-Charles
-Original Message-
From:
Just download a file via http from our web server at
http://208.65.55.55/dummy.zip
and then
http://64.128.251.33/dummy.zip
Then email me with how fast each went and a traceroute from you to just one
of the servers please (they take same route).
If you are not capable of downloading at 20MB on
[r...@ds00209 ~]# wget http://208.65.55.55/dummy.zip
--23:53:06-- http://208.65.55.55/dummy.zip
= `dummy.zip'
Connecting to 208.65.55.55:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 63,375,843 (60M) [application/zip]
