|3||XILO Communications Ltd.||Linux||0:00:00||0.006||0.184||0.059||0.118||0.118|
|10||Hyve Managed Hosting||Linux||0:00:00||0.017||0.092||0.056||0.116||0.116|
ServerStack had the most reliable hosting company website in January 2018, with the only site to respond successfully to each of Netcraft's requests. Its website appeared in the top 10 five times in 2017, and a total of 46 times since its inclusion in 2012. The hosting company, which operates three data centres in the US and Europe, provides managed hosting and was co-founded by brothers Moisey and Ben Uretsky, who later went on to start cloud provider DigitalOcean.
The next five hosting company sites each had only a single failed request, with the tie being broken by average connect time. Of these five, vXtream's Qube site had the quickest average connect time (53ms), earning it second place. vXtream, which recently acquired Qube, offers managed hosting, colocation, and cloud-based solutions from data centres in Zurich, London and New York. Its website, qubenet.net, has appeared in the top 10 a total of ten times in 2017. The sites belonging to XILO, Memset, pair Networks, and CWCS were ranked 3rd, 4th, 5th, and 6th according to their average connect times.
Hyve Managed Hosting's site continues its top 10 streak, now having been amongst the top 10 most reliable hosting company sites for 12 consecutive months. It claims 10th place this month, with three failed requests but a fast response time. Hyve's website has sustained a 100% uptime record since Netcraft began monitoring it in 2016.
Linux is the most popular operating system this month, being used by nine of the top ten hosting companies. FreeBSD also makes an appearance as Pair Networks's OS of choice.
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.