|4||Hyve Managed Hosting||Linux||0:00:00||0.005||0.093||0.068||0.141||0.141|
|9||New York Internet||FreeBSD||0:00:00||0.010||0.289||0.024||0.048||0.049|
Both Webair and Swishmail responded to all of our requests in November 2017, but the faster average connect time for Webair means it takes the top spot. Webair is a US-based provider of fully managed hosting solutions and has appeared in the top ten a total of seven times in 2017, also taking the top spot in May. Swishmail, a provider of email and web hosting solutions using FreeBSD, has appeared in the top ten five times in 2017.
The six websites ranking third to eighth each failed to respond to only a single request in November. vXtream and Hyve (in third and fourth places) have both made their tenth appearances in the top ten in 2017 – vXtream was absent only in March, while Hyve narrowly missed out by ranking 11th in January. London based vXtream recently acquired Qube Managed Services contracts and infrastructure including presence in datacentres in London, New York and Zurich. Hyve places fourth with an average connect time of 68ms, 2ms slower than vXtream, it offers fully managed cloud hosting from datacentres in the UK, US and China.
Pair Networks owns its own datacentre in Pittsburgh and also offers space in the datacentre of a partner in Denver, it is one of the three websites in the top ten to be run on FreeBSD.
Linux is once again the most prevalent operating system in use for the top ten websites, with seven of the ten websites using it. FreeBSD is the operating system of choice for the remaining three.
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.