Most Reliable Hosting Company Sites in July 2017

Rank Performance Graph OS Outage
hh:mm:ss
Failed
Req%
DNS Connect First
byte
Total
1 Qube Managed Services Linux 0:00:00 0.000 0.135 0.063 0.124 0.124
2 Memset Linux 0:00:00 0.000 0.137 0.063 0.244 0.387
3 New York Internet FreeBSD 0:00:00 0.004 0.279 0.019 0.041 0.148
4 Bigstep Linux 0:00:00 0.004 0.132 0.063 0.129 0.129
5 XILO Communications Ltd. Linux 0:00:00 0.004 0.213 0.070 0.139 0.139
6 Netcetera Linux 0:00:00 0.004 0.092 0.079 0.159 0.160
7 www.dinahosting.com Linux 0:00:00 0.004 0.194 0.082 0.164 0.165
8 Hivelocity Linux 0:00:00 0.004 0.156 0.084 0.168 0.168
9 One.com Linux 0:00:00 0.008 0.190 0.037 0.106 0.106
10 Hyve Managed Hosting Linux 0:00:00 0.008 0.084 0.061 0.127 0.127

See full table

Qube Managed Services takes July 2017's top position for most reliable hosting company site, with its site successfully responding to all requests. Qube operates from three data centres — in the City of London, Zurich, and Manhattan, New York - offering managed hosting, colocation, and cloud-based solutions.

Memset's site also successfully responded to all requests in July, as it did in June. However, its average TCP connect time was less than a millisecond slower than Qube's, granting Memset second place in July. Memset is a UK-based hosting company with a 99.998% uptime over 3 years, and 100% uptime over the past 6 months.

New York Internet gained third place with only one failed request. New York Internet is the only hosting provider in July's top 10 list to use a non-Linux operating system to power its website, being powered instead by FreeBSD.

Hyve Managed Hosting continues its top 10 streak, now having been in the top 10 for six consecutive months.

Netcraft measures and makes available the response times of around thirty 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.