Most Reliable Hosting Company Sites in April 2019

Rank Performance Graph OS Outage
hh:mm:ss
Failed
Req%
DNS Connect First
byte
Total
1 www.choopa.com Linux 0:00:00 0.000 0.294 0.005 0.020 0.020
2 www.viawest.com Linux 0:00:00 0.000 0.489 0.005 0.230 0.230
3 GoDaddy.com Inc Linux 0:00:00 0.000 0.452 0.006 0.024 0.026
4 One.com Linux 0:00:00 0.000 0.395 0.084 0.191 0.191
5 www.dinahosting.com Linux 0:00:00 0.000 0.300 0.090 0.180 0.180
6 Rackspace Linux 0:00:00 0.004 0.689 0.007 0.018 0.018
7 Hyve Managed Hosting Linux 0:00:00 0.004 0.187 0.065 0.137 0.137
8 CWCS Managed Hosting Linux 0:00:00 0.004 0.300 0.074 0.152 0.152
9 New York Internet (NYI) FreeBSD 0:00:00 0.009 0.568 0.059 0.118 0.118
10 Netcetera Linux 0:00:00 0.009 0.225 0.085 0.169 0.169

See full table

The most reliable hosting company site in April 2019 belonged to Choopa.com - it responded to all of Netcraft's requests and had the fastest average connection time of 4.597ms. Choopa.com provides cloud hosting, dedicated servers, colocation and managed services from its primary data centre in Piscataway, New Jersey, and also has facilities in Los Angeles, Amsterdam and Tokyo. ViaWest.com, in second place, also responded to each of Netcraft's requests and had an average connection time of 4.601ms. The top two are therefore separated by just 0.004ms after taking the average over nearly 23 thousand requests.

The next three hosting company sites in the top 10 also responded to each of Netcraft's requests in April: GoDaddy, One.com and DinaHosting. These sites were separated by their average connection times of 6ms, 84ms and 90ms, respectively. DinaHosting is a Madrid-based hosting company with services including cloud, dedicated and reseller hosting.

Linux dominates the top 10 in April, with nine of the top 10 sites using the operating system. FreeBSD makes an appearance in ninth place.

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