Most Reliable Hosting Company Sites in April 2011

Rank Company site OS Outage
DNS Connect First
1 Rackspace F5 Big-IP 0:00:00 0.008 0.120 0.063 0.127 0.127
2 Linux 0:00:00 0.015 0.081 0.043 0.088 0.088
3 Windows 0:00:00 0.015 0.067 0.071 0.143 0.288
4 Datapipe FreeBSD 0:00:00 0.019 0.124 0.008 0.019 0.026
5 New York Internet FreeBSD 0:00:00 0.019 0.167 0.063 0.126 0.341
6 Linux 0:00:00 0.027 0.114 0.064 0.142 0.344
7 INetU unknown 0:00:00 0.031 0.097 0.039 0.101 0.242
8 Hosting 4 Less Linux 0:00:00 0.035 0.122 0.096 0.195 0.422
9 Linux 0:00:00 0.039 0.076 0.007 0.047 0.080
10 Linux 0:00:00 0.039 0.215 0.061 0.136 0.260

See full table

Heading the table for April with only two failed requests from any of the performance monitors during the month was Rackspace. Rackspace provides managed and cloud hosting from nine datacentres in the U.S., the U.K. and China. Rackspace frequently features in Netcraft's top ten most reliable hosting companies, having appeared five times in the last year.

Second most reliable this month was Qube, a London-based hosting company which also has datacentres in New York and Zurich. Qube provide managed hosting, managed colocation and cloud hosting for a wide variety of customers, particularly in the areas of finance and new media. Although Qube has previously appeared in the top ten, this is the first time the hosting company has made it to the top three.

The third most reliable hosting company in April was Netcetera. Netcetera experienced the same number of failed requests as Qube, but had a longer average connection time. Netcetera provides a wide range of colocation, hosting and cloud services to customers throughout the world.

Five of the top ten sites this month were running on Linux, two were running on FreeBSD, and one on Windows. Rackspace's site, which performed best this month, is hosted on F5 Big-IP.

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. In the event the number of failed requests are equal then sites are ranked by average connection times.

Information on the measurement process and current measurements is available.