Most Reliable Hosting Company Sites in April 2010
13th May, 2010
| Rank | Company site | OS | Outage hh:mm:ss |
Failed Req% |
DNS | Connect | First byte |
Total |
|---|---|---|---|---|---|---|---|---|
| 1 | DataPipe | FreeBSD | 0:00:00 | 0.015 | 0.031 | 0.027 | 0.057 | 0.083 |
| 2 | GoDaddy.com Inc | Windows Server 2003 | 0:00:00 | 0.023 | 0.161 | 0.092 | 0.196 | 0.781 |
| 3 | New York Internet | FreeBSD | 0:00:00 | 0.027 | 0.106 | 0.051 | 0.113 | 0.312 |
| 4 | iWeb Technologies | Linux | 0:00:00 | 0.031 | 1.187 | 0.063 | 0.127 | 0.127 |
| 5 | www.dinahosting.com | Linux | 0:00:00 | 0.031 | 0.178 | 0.128 | 0.256 | 0.256 |
| 6 | www.navisite.com | Linux | 0:00:00 | 0.035 | 0.353 | 0.102 | 0.683 | 0.896 |
| 7 | www.netcetera.co.uk | Windows Server 2003 | 0:00:00 | 0.039 | 0.084 | 0.050 | 0.107 | 0.212 |
| 8 | Virtual Internet | Linux | 0:00:00 | 0.039 | 0.173 | 0.054 | 0.162 | 0.329 |
| 9 | ServInt | Linux | 0:00:00 | 0.039 | 0.162 | 0.063 | 0.146 | 0.331 |
| 10 | www.acens.com | Linux | 0:00:00 | 0.046 | 0.298 | 0.129 | 0.440 | 0.845 |
The most reliable hosting company site in April was DataPipe, once again responding to all but four of Netcraft's requests.
DataPipe provides custom managed hosting solutions for businesses with complex Internet facing infrastructures with over 1,000 customers in seven data centres across the United States, Europe and China.
The second most reliable hosting company site in April was GoDaddy, responding to all but six of Netcraft's requests.
GoDaddy is the world's largest domain name registrar, managing more than 40 million domains.
Netcraft measures and makes available the response times of around forty leading hosting providers' sites. The performance measurements are made at fifteen minute intervals from separate points around the internet, and averages are calculated over the immediately preceding 24 hour period.
From a customer's point of view, the percentage of failed requests is more pertinent than outages on hosting companies' own sites, as this gives a pointer to reliability of routing, and this is why we choose to rank our table by fewest failed requests, rather than shortest periods of outage.
Further information on the measurement process and current measurements are available.