|6||Hyve Managed Hosting||Linux||0:00:00||0.004||0.096||0.062||0.128||0.128|
|7||Qube Managed Services||Linux||0:00:00||0.004||0.150||0.063||0.126||0.126|
Four hosting companies responded successfully to all of Netcraft’s requests during May: Webair, Swishmail, ServerStack and Hivelocity.
Webair had the lowest average connection time out of the four, and so took first place in May’s rankings. This is the first time the cloud hosting company’s site has topped Netcraft’s Most Reliable Hosting Company Sites ranking, but marks its fourth consecutive month in the top ten. Webair recently announced a partnership with Microsoft to offer Azure ExpressRoute, which creates a direct network connection between Webair and the Microsoft Cloud.
Swishmail‘s site has retained its second place position in Netcraft’s ranking from April. Similarly to last month, Swishmail narrowly missed out on the top spot based on its average connection time despite having as many successful requests. The US-based company provides FreeBSD-based email and web hosting services.
ServerStack came in third, with a slightly longer average connection time than both Webair and Swishmail’s site, but still no failed requests. ServerStack offers fully managed services which include software installation, proactive monitoring, automated backups, performance optimisation, troubleshooting, and virtualisation.
Hivelocity came fourth after responding successfully to all of Netcraft’s requests. The hosting provider has three US-based data centres: two in Tampa, Florida and a third one in Atlanta.
Linux continues to be the predominantly used operating system, powering eight of the top ten sites. The only exceptions are Swishmail and Pair Networks which both run FreeBSD.
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.