|4||Kattare Internet Services||Citrix Netscaler||0:00:00||0.010||0.568||0.124||0.250||0.250|
|6||Hyve Managed Hosting||Linux||0:00:00||0.014||0.102||0.048||0.102||0.102|
|7||XILO Communications Ltd.||Linux||0:00:00||0.014||0.227||0.054||0.107||0.107|
Netcetera had the most reliable hosting company site in March 2017, retaining its first place spot from February. Netcetera’s site once again successfully responded to all of Netcraft’s requests, with an average TCP connection time of 63 milliseconds. This continues Netcetera’s strong performance from the past year: its site has placed in the top ten in eight out of the past twelve months, including three first places.
Memset, Webair, and Kattare‘s sites each had two failed requests this month, placing their sites second, third and fourth based on average connection times. Memset is a UK-based provider of dedicated and cloud hosting services, operating data centres near London and another in the US West-Coast area. Webair is a New York-based hosting provider which offers fully managed cloud and infrastructure solutions, with data centres in New York, Los Angeles, Montréal and Amsterdam. This is Webair’s second consecutive appearance in the top ten in 2017.
Anexia, Xilo, and Netcetera have consistently placed in the top ten so far in 2017. All three serve their company sites from Linux machines, and this remains the most common operating system used amongst the other top ten hosting companies’ sites. In March, nine out of ten of the most reliable hosting companies’ websites were powered by Linux, with the remaining one, operated by Kattare, using Citrix Netscaler.
Netcraft measures and makes available the response times of around forty 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.