Choice of Server Locations
24-7 Webs runs servers in Chicago, Atlanta and Dallas, with more cities to come. Having been in the business since 2001, we have had the opportunity to test many major Network Operation Centers and hosting suppliers, some good, some bad and a few who are excellent. We believe we have selected the best of the best in terms of reliability and attention to detail. We did not choose the cheapest available, nor do we load our servers to the breaking point to maximize our returns. Our number one priority is to give you, our customer, a reliable and lightning-fast platform for your website.
Why Would I Care Where my Site is Hosted?
In order for your site to be found on the internet, the data needs to travel from the server to your site visitor along a path on the internet. This path is through a series of routers and each point in the path is called a hop. This path can change at any time for any number of reasons. The shorter the path, the faster the connection. If there is a longer path, there is more possibility of an equipment failure along the route causing your visitor's connection to be slow, delayed, or in rare circumstances unavailable. This does not mean your site is down, it only means that your site visitor's path could be less than perfect resulting in slower performance.
Examples
Here is a traceroute from Melbourne Australia a server in the Dallas Center.
traceroute to 208.101.0.83 (208.101.0.83), 30 hops max, 40 byte packets 1 vlan250.lon-service6.Melbourne.telstra.net (203.50.2.177) 0.347 ms 0.284 ms 0.252 ms 2 TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.telstra.net (203.50.80.1) 0.338 ms 0.43 ms 0.4 ms 3 Bundle-POS1.chw-core2.Sydney.telstra.net (203.50.6.13) 14.842 ms 14.958 ms 15.155 ms 4 Bundle-Ether1.oxf-gw2.Sydney.telstra.net (203.50.6.90) 14.951 ms 14.954 ms 14.961 ms 5 TenGigabitEthernetx-0.syd-core04.Sydney.reach.com (203.50.13.18) 15.416 ms 15.302 ms 15.256 ms 6 i-3-1-0.sydp-core02.bi.reach.com (202.84.144.249) 15.299 ms 15.323 ms 15.173 ms 7 i-9-0-0.sydp-core01.bi.reach.com (202.84.221.89) 15.247 ms 15.29 ms 15.174 ms 8 i-10-2-1.wil-core03.bx.reach.com (202.84.140.29) 164.318 ms 164.396 ms 164.421 ms 9 i-2-1.tlot03.bi.reach.com (202.84.251.185) 164.44 ms 164.55 ms 164.57 ms 10 ge-6-20.car3.LosAngeles1.Level3.net (4.68.111.133) 164.738 ms ge-6-21.car3.LosAngeles1.Level3.net (4.68.111.137) 164.6 ms 164.633 ms 11 vlan79.csw2.LosAngeles1.Level3.net (4.68.20.126) 171.17 ms 164.639 ms 164.931 ms 12 ae-72-72.ebr2.LosAngeles1.Level3.net (4.69.137.21) 165.622 ms 165.231 ms 165.086 ms 13 ae-3.ebr3.Dallas1.Level3.net (4.69.132.78) 196.853 ms 200.716 ms 197.648 ms 14 ae-83-83.csw3.Dallas1.Level3.net (4.69.136.162) 205.192 ms ae-93-93.csw4.Dallas1.Level3.net (4.69.136.166) 209.384 ms 201.804 ms 15 ae-4-99.edge3.Dallas1.Level3.net (4.68.19.200) 197.416 ms 197.715 ms 197.618 ms 16 te2-1.cer01.dal01.dallas-datacenter.com (4.71.198.18) 230.935 ms 231.196 ms 231.176 ms 17 po1.dar01.dal01.dallas-datacenter.com (66.228.118.201) 239.897 ms 229.698 ms 230.297 ms 18 po1.fcr01.dal01.dallas-datacenter.com (66.228.118.154) 238.872 ms 231.05 ms 231.778 ms 19 server506.247webs.com (208.101.0.83) 231.509 ms 231.213 ms 231.541 ms
You can see that it took 19 hops and 231.213 ms (micro seconds).
Here is a traceroute to the same server right from Dallas.
1 ges1-ethernet.Dallas.savvis.net 208.172.128.1 1.462 ms 2 bcr1-ge-7-0-0.dallas.savvis.net 208.172.131.9 1.118 ms 3 cr2-pos0-0-3-2.dallas.savvis.net 204.70.198.109 1.688 ms 4 dpr1-ge-4-0-0.dallasequinix.savvis.net 204.70.196.30 1.272 ms 5 er1-te-2-1.dallasequinix.savvis.net 204.70.204.145 1.327 ms 6 te1-1.cer02.dal01.dallas-datacenter.com 208.175.175.10 1.360 ms 7 po2.dar02.dal01.dallas-datacenter.com 66.228.118.207 1.547 ms 8 po2.fcr01.dal01.dallas-datacenter.com 66.228.118.158 1.616 ms 9.server506.247webs.com 208.101.0.83 1.616 ms
You can see here that it took 9 hops and 1.616 ms. This is a much faster connection, and fewer places for that connection to be interrupted resulting in highly reliable and rocket-fast site content delivery to your customers.
If you would like to run a traceroute to our data centers to see which is best for you here is a list of addresses.
In Atlanta - server208.net
In Chicago- server706.com
In Dallas - server506.com
Not sure how to run a traceroute? Instructions are here:
Running Traceroute from a Windows Computer (new window)
Please be sure you do not ping the server frequently as this could result in your connection to the server being blocked by our sophisticated firewall technology. If you are blocked, please contact the support department. (new window)
Choices for You!
This is just one of the ways the 24-7 Webs offers our customers choices... important choices for your web presence. Check us out. Take the free hosting trial, no credit card information required.