BigBiz's Network Connection
BigBiz's servers are among the best connected machines
in the world.
Our servers are housed in specially built server rooms, with
redundant power, backups, 24x7 monitoring, and fully redundant
network connections. We feature direct connections to all the
major Internet backbone carriers and exchange points.
We use state of the art Cisco, 3COM, and HP networking equipment.
Our uplink provider AboveNet has a network map which shows
the capacity and connectivity.
Having direct connections to the main exchange points means less "hops"
between you and your clients, super-fast turnarounds and transfer speeds,
and eliminating those "connection refused" messages which plague ISPs with poor
connectivity.
By hosting your web pages at BigBiz instead of a 2nd or 3rd tier ISPs,
you are eliminating unnecessary extra "hops" through intermediate
routers.
How fast is BigBiz?
We can reach the MAE in about 1 millisecond, and CIX in under 3 milliseconds.
Most users can't even ping a directly connected ethernet machine in that
time! Having good connectivity means users can get to your web site
without delay.
Approx. ping times to some major sites are listed below, we dare you
to compare with your ISP:
- Nasa (nsipo.arc.nasa.gov) 3ms
PING nsipo.arc.nasa.gov (128.102.32.20): 56 data bytes
64 bytes from 128.102.32.20: icmp_seq=0 ttl=251 time=3.1 ms
64 bytes from 128.102.32.20: icmp_seq=1 ttl=251 time=2.6 ms
64 bytes from 128.102.32.20: icmp_seq=2 ttl=251 time=2.6 ms
64 bytes from 128.102.32.20: icmp_seq=3 ttl=251 time=2.9 ms
64 bytes from 128.102.32.20: icmp_seq=4 ttl=251 time=2.6 ms
--- nsipo.arc.nasa.gov ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 2.6/2.7/3.1 ms
- Digital Equipment Corporation (decwrl.dec.com) 3ms
PING ftp.digital.com (204.123.2.4): 56 data bytes
64 bytes from 204.123.2.4: icmp_seq=0 ttl=251 time=3.2 ms
64 bytes from 204.123.2.4: icmp_seq=1 ttl=251 time=2.5 ms
64 bytes from 204.123.2.4: icmp_seq=2 ttl=251 time=2.7 ms
64 bytes from 204.123.2.4: icmp_seq=3 ttl=251 time=2.6 ms
64 bytes from 204.123.2.4: icmp_seq=4 ttl=251 time=3.2 ms
--- ftp.digital.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 2.5/2.8/3.2 ms
- Stanford University (Stanford.EDU) 10ms
PING stanford.edu (171.64.7.69): 56 data bytes
64 bytes from 171.64.7.69: icmp_seq=0 ttl=246 time=8.8 ms
64 bytes from 171.64.7.69: icmp_seq=1 ttl=246 time=21.7 ms
64 bytes from 171.64.7.69: icmp_seq=2 ttl=246 time=7.7 ms
64 bytes from 171.64.7.69: icmp_seq=3 ttl=246 time=6.1 ms
64 bytes from 171.64.7.69: icmp_seq=4 ttl=246 time=9.0 ms
--- stanford.edu ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 6.1/10.6/21.7 ms
- @HOME (www.home.net) 7 ms
PING www.home.net (24.0.30.17): 56 data bytes
64 bytes from 24.0.30.17: icmp_seq=0 ttl=248 time=6.3 ms
64 bytes from 24.0.30.17: icmp_seq=1 ttl=248 time=5.7 ms
64 bytes from 24.0.30.17: icmp_seq=2 ttl=248 time=5.5 ms
64 bytes from 24.0.30.17: icmp_seq=3 ttl=248 time=6.1 ms
64 bytes from 24.0.30.17: icmp_seq=4 ttl=248 time=9.2 ms
--- www.home.net ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 5.5/6.5/9.2 ms
- Digex (www.digex.net) 5 ms
PING www.digex.net (207.87.16.114): 56 data bytes
64 bytes from 207.87.16.114: icmp_seq=0 ttl=121 time=5.9 ms
64 bytes from 207.87.16.114: icmp_seq=1 ttl=121 time=4.0 ms
64 bytes from 207.87.16.114: icmp_seq=2 ttl=121 time=4.8 ms
64 bytes from 207.87.16.114: icmp_seq=3 ttl=121 time=5.3 ms
64 bytes from 207.87.16.114: icmp_seq=4 ttl=121 time=4.2 ms
--- www.digex.net ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 4.0/4.8/5.9 ms
- Exodus Communications (www.exodus.net) 8 ms
PING www.external.exodus.net (209.185.20.216): 56 data bytes
64 bytes from 209.185.20.216: icmp_seq=0 ttl=248 time=21.0 ms
64 bytes from 209.185.20.216: icmp_seq=1 ttl=248 time=4.5 ms
64 bytes from 209.185.20.216: icmp_seq=2 ttl=248 time=4.5 ms
64 bytes from 209.185.20.216: icmp_seq=3 ttl=248 time=5.6 ms
64 bytes from 209.185.20.216: icmp_seq=4 ttl=248 time=4.6 ms
--- www.external.exodus.net ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 4.5/8.0/21.0 ms
- Pacific Bell (www.pacbell.com) 9 ms
PING gw2.PacBell.COM (204.107.17.21): 56 data bytes
64 bytes from 204.107.17.21: icmp_seq=0 ttl=249 time=9.2 ms
64 bytes from 204.107.17.21: icmp_seq=1 ttl=249 time=9.7 ms
64 bytes from 204.107.17.21: icmp_seq=2 ttl=249 time=8.6 ms
64 bytes from 204.107.17.21: icmp_seq=3 ttl=249 time=8.6 ms
64 bytes from 204.107.17.21: icmp_seq=4 ttl=249 time=9.1 ms
--- gw2.PacBell.COM ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 8.6/9.0/9.7 ms
- Yahoo (www.yahoo.com) 4 ms
PING www6.yahoo.com (204.71.177.71): 56 data bytes
64 bytes from 204.71.177.71: icmp_seq=0 ttl=249 time=4.6 ms
64 bytes from 204.71.177.71: icmp_seq=1 ttl=249 time=4.5 ms
64 bytes from 204.71.177.71: icmp_seq=2 ttl=249 time=4.4 ms
64 bytes from 204.71.177.71: icmp_seq=3 ttl=249 time=4.2 ms
64 bytes from 204.71.177.71: icmp_seq=4 ttl=249 time=4.4 ms
--- www6.yahoo.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 4.2/4.4/4.6 ms
- Netscape (www.netscape.com) 2 ms
PING www24.netscape.com (207.200.73.73): 56 data bytes
64 bytes from 207.200.73.73: icmp_seq=0 ttl=250 time=2.4 ms
64 bytes from 207.200.73.73: icmp_seq=1 ttl=250 time=2.2 ms
64 bytes from 207.200.73.73: icmp_seq=2 ttl=250 time=2.5 ms
64 bytes from 207.200.73.73: icmp_seq=3 ttl=250 time=2.4 ms
64 bytes from 207.200.73.73: icmp_seq=4 ttl=250 time=2.3 ms
--- www24.netscape.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 2.2/2.3/2.5 ms
- Oracle (www.oracle.com) 6 ms
PING v-www.us.oracle.com (205.227.44.16): 56 data bytes
64 bytes from 205.227.44.16: icmp_seq=0 ttl=48 time=6.0 ms
64 bytes from 205.227.44.16: icmp_seq=1 ttl=48 time=5.6 ms
64 bytes from 205.227.44.16: icmp_seq=2 ttl=48 time=5.0 ms
64 bytes from 205.227.44.16: icmp_seq=3 ttl=48 time=6.1 ms
64 bytes from 205.227.44.16: icmp_seq=4 ttl=48 time=5.5 ms
--- v-www.us.oracle.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 5.0/5.6/6.1 ms
- Apple (www.apple.com) 6 ms
PING www.apple.com (17.254.0.91): 56 data bytes
64 bytes from 17.254.0.91: icmp_seq=0 ttl=47 time=7.5 ms
64 bytes from 17.254.0.91: icmp_seq=1 ttl=47 time=7.6 ms
64 bytes from 17.254.0.91: icmp_seq=2 ttl=47 time=5.4 ms
64 bytes from 17.254.0.91: icmp_seq=3 ttl=47 time=5.4 ms
64 bytes from 17.254.0.91: icmp_seq=4 ttl=47 time=5.7 ms
--- www.apple.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 5.4/6.3/7.6 ms
International
- Japan (sony.co.jp) 120 ms
PING sony.co.jp (202.238.80.21): 56 data bytes
64 bytes from 202.238.80.21: icmp_seq=0 ttl=243 time=117.6 ms
64 bytes from 202.238.80.21: icmp_seq=1 ttl=244 time=128.7 ms
64 bytes from 202.238.80.21: icmp_seq=2 ttl=244 time=109.6 ms
64 bytes from 202.238.80.21: icmp_seq=3 ttl=244 time=117.6 ms
64 bytes from 202.238.80.21: icmp_seq=4 ttl=244 time=112.4 ms
--- sony.co.jp ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 109.6/117.1/128.7 ms
- United Kingdom (www.demon.co.uk) 160 ms
PING www.demon.co.uk (193.195.1.1): 56 data bytes
64 bytes from 193.195.1.1: icmp_seq=0 ttl=243 time=166.1 ms
64 bytes from 193.195.1.1: icmp_seq=1 ttl=243 time=157.2 ms
64 bytes from 193.195.1.1: icmp_seq=2 ttl=243 time=153.4 ms
64 bytes from 193.195.1.1: icmp_seq=3 ttl=243 time=160.6 ms
64 bytes from 193.195.1.1: icmp_seq=4 ttl=243 time=158.4 ms
--- www.demon.co.uk ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 153.4/159.1/166.1 ms
- Germany (netsurf.de) 180 ms
PING netsurf.de (195.180.6.4): 56 data bytes
64 bytes from 195.180.6.4: icmp_seq=0 ttl=240 time=178.0 ms
64 bytes from 195.180.6.4: icmp_seq=1 ttl=240 time=178.1 ms
64 bytes from 195.180.6.4: icmp_seq=2 ttl=240 time=178.5 ms
64 bytes from 195.180.6.4: icmp_seq=3 ttl=240 time=176.9 ms
64 bytes from 195.180.6.4: icmp_seq=4 ttl=240 time=181.0 ms
--- netsurf.de ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 176.9/178.5/181.0 ms
- Canada (www.uunet.ca) 77 ms
PING www.uunet.ca (205.150.149.122): 56 data bytes
64 bytes from 205.150.149.122: icmp_seq=0 ttl=244 time=77.2 ms
64 bytes from 205.150.149.122: icmp_seq=1 ttl=244 time=77.3 ms
64 bytes from 205.150.149.122: icmp_seq=2 ttl=244 time=77.3 ms
64 bytes from 205.150.149.122: icmp_seq=3 ttl=244 time=77.7 ms
64 bytes from 205.150.149.122: icmp_seq=4 ttl=244 time=77.8 ms
--- www.uunet.ca ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 77.2/77.4/77.8 ms
- Australia (www.yahoo.com.au) 300 ms
PING www.yahoo.com.au (203.103.130.22): 56 data bytes
64 bytes from 203.103.130.22: icmp_seq=0 ttl=242 time=313.1 ms
64 bytes from 203.103.130.22: icmp_seq=1 ttl=242 time=234.0 ms
64 bytes from 203.103.130.22: icmp_seq=2 ttl=242 time=309.5 ms
64 bytes from 203.103.130.22: icmp_seq=3 ttl=242 time=227.0 ms
64 bytes from 203.103.130.22: icmp_seq=4 ttl=242 time=305.7 ms
--- www.yahoo.com.au ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 227.0/277.8/313.1 ms
File transfers speed
Here is the log from a ftp session to gatekeeper.dec.com (large repository
of public domain and shareware files):
ftp> get Index-byname.Z
local: Index-byname.Z remote: Index-byname.Z
200 PORT command successful.
150 Opening BINARY mode data connection for Index-byname.Z (3883530 bytes).
226 Transfer complete.
3883530 bytes received in 5.97 secs (6.4e+02 Kbytes/sec)
ftp> get Index-bytime.Z
local: Index-bytime.Z remote: Index-bytime.Z
200 PORT command successful.
150 Opening BINARY mode data connection for Index-bytime.Z (4565985 bytes).
226 Transfer complete.
4565985 bytes received in 6.89 secs (6.5e+02 Kbytes/sec)
Thats over 8 Megabytes in 13 seconds!
What this means is that when your clients requests files or views your
web pages, we can pump data to the network as fast as they can receive it.
Compare this to typical ISPs that have T1 lines, its not even close!
What does all this cost?
A lot. The equipment is not cheap, and there is an enormous amount of time
spent in engineering and network administration. BigBiz has put a lot
of effort into setting up this infrastructure so you wont need to.
When web hosting at BigBiz, you can forget about
any concerns you have about slow
network connectivity.
We can offer to you the equivalent
capabilities of a major internet carrier, at a downright disgustingly
low price. BigBiz will handle the network
administration issues so you can spend your time concentrating on your
business, and not wasting your time solving esoteric computer problems.
Cost comparison
Lets compare the costs of setting up your own internet server
at your premises to hosting at BigBiz.
Suppose you want to create a web site and deliver your
content to customers around the world. You will not want to have
any connection less than a T1. Typical T1 costs are about $5000 setup
and $750-1000 per month. Add to that the costs of a computer and time
someone on your staff spends mucking with the configuration and such,
and you are clearly into $5000+ / month.
If you transfer 5 Gigabytes of data per month, the cost of hosting your
site at BigBiz comes to about $50 per month (many businesses hosted at
BigBiz pay a lot less). You can realize all of the benefits of our
expertise and network connectivity at a fraction of what it would cost
to "do it yourself".
How do we do it
We have placed major up-front investments into our setup. We can pass these
benefits to you and many others, basically dividing down our costs. We
have negotiated volume pricing agreements and can pass these savings to you.
We outsource some of our needs to bring the cost down, like
facility management and network monitoring. We concentrate
on what we do best: setting up web server and networking hardware, software, and
customer service.
As internet presence becomes more important for businesses,
we expect to grow to serve these needs. We are always expanding
our capabilities, looking for additional network bandwidth,
and adding new hardware and software to serve those needs. We are
constantly monitoring new developments in internet and web technology,
like IPv6, new gTLDs, server extensions, and security issues, and will
bring these new technologies to our customers.