|1||New York Internet (NYI)||FreeBSD||0:00:00||0.000||0.521||0.053||0.107||0.107|
|4||Hyve Managed Hosting||Linux||0:00:00||0.000||0.148||0.084||0.168||0.168|
|9||CWCS Managed Hosting||Linux||0:00:00||0.005||0.292||0.080||0.163||0.163|
New York Internet (NYI) had the most reliable hosting company website in September 2019, responding to all of Netcraft’s requests. This is the fourth time NYI has appeared in the top 10 in 2019. NYI offers bare metal, cloud and colocation services in its US data centers, and recently expanded into the Chicago market with the acquisition of a new data center.
The next five hosting company sites also responded to all of our requests, and are separated in the ranking by their average connection time. Second-placed EveryCity has had 99.998% uptime since Netcraft started monitoring 5 years ago and is the only site Netcraft is monitoring that is powered by SmartOS.
Third place was close with ServerStack claiming the position with an average connection time of 83.6ms—just half a millisecond faster than Hyve Managed Hosting in fourth place. ServerStack has now appeared in the top 10 for five consecutive months.
In sixth place, Choopa.com failed to respond to a single request but had the fastest average connection time of 5.2ms. This was closely followed by Rackspace, with an average connection time of 5.5ms.
FreeBSD and SmartOS appear in first and second place in September, with New York Internet (NYI) and EveryCity. The eight hosting company sites that complete the top 10 are powered by Linux.
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.