Most Reliable Hosting Company Sites in September 2014

Rank Performance Graph OS Outage
DNS Connect First
1 Qube Managed Services Linux 0:00:00 0.004 0.086 0.023 0.046 0.046
2 Inc Linux 0:00:00 0.013 0.149 0.012 0.200 0.205
3 Memset Linux 0:00:00 0.013 0.111 0.055 0.132 0.217
4 Linux 0:00:00 0.013 0.242 0.080 0.159 0.159
5 Swishmail FreeBSD 0:00:00 0.022 0.124 0.073 0.144 0.186
6 ServerStack Linux 0:00:00 0.022 0.081 0.076 0.151 0.151
7 Datapipe FreeBSD 0:00:00 0.030 0.102 0.016 0.032 0.048
8 EveryCity SmartOS 0:00:00 0.030 0.083 0.054 0.107 0.107
9 Logicworks Linux 0:00:00 0.030 0.143 0.073 0.152 0.340
10 Pair Networks FreeBSD 0:00:00 0.030 0.219 0.082 0.166 0.579

See full table

Qube had the most reliable company site in September with only a single failed request. This is the fourth time this year that Qube has made it to first place, nudging ahead of Datapipe's track record this year. Qube offers a Hybrid cloud service, where physical servers and equipment are integrated with its cloud hosting with a secure connection between the two networks.

The second most reliable hosting company site belonged to GoDaddy, the world's largest domain registrar, and had only 3 failed requests in September. Memset and dinahosting also had only 3 failed requests and thus they were ranked by average connection times.

In third place is Memset. Memset was last ranked in the top 10 in June 2013 when it achieved 9th place with 6 failed requests. Memset offers its customers a Perimeter Patrol service, which involves regular scanning of Memset servers to highlight security vulnerabilities.

Linux was still the most popular operating system of choice, used by 6 of the top 10, followed by FreeBSD which was used by 3. EveryCity, however, uses SmartOS, a community fork of OpenSolaris geared towards cloud hosting using KVM virtualisation.

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.