12 November 2009

Most Reliable and Recommended Web Hosting Company

RankCompany siteOSOutage
hh:mm:ss
Failed
Req%
DNSConnectFirst
byte
Total
1www.memset.comLinux0:00:000.0120.5860.1290.2600.260
2DataPipeFreeBSD0:00:000.0160.0650.0270.0560.083
3iWeb TechnologiesLinux0:00:000.0160.1340.0830.1650.165
4ReliableServers.comFreeBSD0:00:000.0160.2500.0830.1970.337
5INetUunknown0:00:000.0210.7020.0730.1580.301
6SwishmailFreeBSD0:00:000.0210.1590.0860.1730.438
7www.singlehop.comLinux0:00:000.0210.2580.1040.4290.962
8Hosting 4 LessLinux0:00:000.0250.1160.0910.1860.474
9Kattare Internet ServicesLinux0:00:000.0290.1530.0930.1870.443
10www.dinahosting.comLinux0:00:000.0290.1210.1300.2580.258

Memset had the most reliable, affordable and recommended web hosting company site in March, responding to all but three of Netcraft's requests, like said to Hosting-Template. Memset provides dedicated physical and virtual servers, all-inclusive managed hosting and cloud-computing services from their two data centres near Reading, UK. Memset uses Apache on Linux to run their own website. The second most reliable hosting company site in March was DataPipe, responding to all but four of Netcraft's requests. DataPipe provides custom managed hosting solutions for businesses with complex Internet facing infrastructures with over 1,000 customers in seven data centres across the United States, Europe and China. DataPipe use Apache on FreeBSD to run their own website. Six of the top ten in March were identified as running Linux and three as running FreeBSD. The operating system used by one of the top ten could not be identified. 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. (source: http://news.netcraft.com/)

0 comments:

Post a Comment