Most Reliable Hosting Company Sites in December 2010

Rank Company site OS Outage
DNS Connect First
1 Swishmail FreeBSD 0:00:00 0.012 0.223 0.099 0.198 0.495
2 ServInt Linux 0:00:00 0.015 0.487 0.102 0.207 0.514
3 Linux 0:00:00 0.015 0.247 0.106 0.400 0.609
4 Hosting 4 Less Linux 0:00:00 0.015 0.188 0.113 0.228 0.448
5 Multacom FreeBSD 0:00:00 0.023 0.205 0.113 0.230 0.584
6 iWeb Technologies Linux 0:00:00 0.035 0.302 0.095 0.226 0.226
7 Linux 0:00:00 0.035 0.420 0.105 0.582 0.966
8 Linux 0:00:00 0.035 0.184 0.106 0.213 0.213
9 Rackspace F5 BIG-IP 0:00:00 0.043 0.193 0.092 0.186 0.186
10 Iomart plc. Linux 0:00:00 0.046 0.186 0.102 0.212 0.492

See full table

The most reliable host this month was Swishmail which responded to all but three of Netcraft's requests. Swishmail ranked ninth last month and has been present in the top ten since October. They primarily offer business level email and web hosting solutions.

In second place this month was ServInt which responded to all but four of our requests. The company specialises in offering managed hosting and has climbed from tenth position after entering the top ten last month. This good performance could perhaps have been a factor in the decision to host with ServInt a fortnight ago.

Ranking third this month was Logicworks which also failed to respond to four requests. The host was last present in the top ten in October when it came in at number seven. Logicworks provide a variety of cloud and managed hosting solutions.

Seven of December's top ten hosting company sites run Linux, two run FreeBSD and one runs F5 BIG-IP.

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.