Most Reliable Hosting Company Sites in February 2010

Rank Company site OS Outage
hh:mm:ss
Failed
Req%
DNS Connect First
byte
Total
1 www.navisite.com Linux 0.000 0.779 0.033 0.552 0.656
2 DataPipe FreeBSD 0:00:00 0.005 0.397 0.035 0.061 0.091
3 INetU unknown 0:00:00 0.005 0.524 0.050 0.106 0.186
4 Hosting 4 Less Linux 0:00:00 0.011 0.428 0.105 0.220 0.560
5 www.singlehop.com Linux 0:00:00 0.016 0.205 0.052 0.342 0.570
6 www.dinahosting.com Linux 0:00:00 0.016 0.115 0.089 0.182 0.182
7 New York Internet FreeBSD 0:00:00 0.021 0.054 0.031 0.070 0.195
8 Virtual Internet Linux 0:00:00 0.021 0.617 0.078 0.210 0.443
9 www.memset.com Linux 0:00:00 0.021 0.616 0.080 0.160 0.160
10 Hostbasket Windows Server 2008 0:00:00 0.021 0.377 0.083 0.177 0.177

See full table

NaviSite had the most reliable hosting company site in February, responding to all of Netcraft's requests.

NaviSite, providers of managed hosting and application management solutions, sold its Lawson/Kronos Managed Application Service business this month in order to "focus on providing Enterprise-class cloud computing for large organisations with complex environments". NaviSite uses Apache on CentOS to run its own website.

The second most reliable hosting company site in February was DataPipe, responding to all but one 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. DataPipe use Apache on FreeBSD to run their own website.

Six of the top ten in February were identified as running Linux, two as running FreeBSD and one running Windows Server 2008.

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.