Most Reliable Hosting Company Sites in April 2012

Rank Company site OS Outage
DNS Connect First
1 Datapipe FreeBSD 0:00:00 0.003 0.047 0.014 0.029 0.049
2 INetU Windows Server 2008 0:00:00 0.007 0.090 0.081 0.243 0.481
3 Linux 0:00:00 0.010 0.153 0.041 0.088 0.097
4 Kattare Internet Services Linux 0:00:00 0.010 0.193 0.148 0.298 0.597
5 Swishmail FreeBSD 0:00:00 0.014 0.136 0.071 0.143 0.344
6 Multacom FreeBSD 0:00:00 0.014 0.219 0.130 0.262 0.767
7 Qube Managed Services Linux 0:00:00 0.017 0.091 0.034 0.070 0.070
8 Linux 0:00:00 0.017 0.192 0.081 0.167 0.175
9 Pair Networks FreeBSD 0:00:00 0.017 0.334 0.091 0.185 0.644
10 Linux 0:00:00 0.021 0.157 0.061 0.355 0.626

See full table

The most reliable hosting company for April was Datapipe, which topped the table seven times in 2011. The company offers a wide range of hosting services and has been rapidly expanding into cloud computing during the past few months. Datapipe has infrastructure spread across the globe; they have data centres in New Jersey, San Jose, Iceland, London, Shanghai, and Hong Kong. Their U.S. data centres are powered exclusively by renewable energy sources.

For the third time so far this year INetU have taken second place. INetU offers dedicated managed hosting services and cloud hosting services from data centres in both the United States and Europe.

Choopa – a New Jersey based company advertising 100% uptime and 0% packet loss guarantees – appears in third position for the second consecutive month.

Linux was used by five of the most reliable hosting companies, including Choopa; four used FreeBSD including the most reliable, Datapipe; and the second most reliable provider, INetU, used 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. 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.