|5||Netcetera||Windows Server 2012||0:00:00||0.017||0.061||0.084||0.168||0.169|
|7||Kattare Internet Services||Linux||0:00:00||0.022||0.181||0.119||0.268||0.576|
|10||Hyve Managed Hosting||Linux||0:00:00||0.030||0.229||0.066||0.130||0.132|
Datapipe had the most reliable hosting company website in April, responding successfully to all of Netcraft's requests; Datapipe has now featured in the top ten for eight consecutive months, and has maintained 100% uptime over the last nine years. In April, Datapipe announced that it had become one of the first AWS Managed Service Provider Partners, certifying that Datapipe "[offers] proactive monitoring, automation, and management of their customer's AWS environment".
With just a single failed request, GoDaddy came in second place. GoDaddy, the world's largest registrar, recently listed on the New York Stock Exchange, bought the GDDY.com domain name to match its stock ticker symbol, and will announce its first quarter 2015 results on 12th May.
ServerStack came in third place in April, narrowly missing second place with just a single failed request separating it from GoDaddy. ServerStack provides managed hosting services to enterprises, targeting companies spending more than $10,000 per month on hosting. Its data centres are based in San Jose, New Jersey and Amsterdam.
Once again, Linux was the most popular operating system for hosting company sites, powering 7 of the top 10 websites. Windows Server 2012, SmartOS and Citrix Netscaler all appear once each.
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.