Rank Company site OS Outage hh:mm:ss Failed Req% DNS Connect First byte Total 1 INetU FreeBSD 0:00:00 0.012 0.126 0.053 0.129 0.337 2 Rackspace F5 Big-IP 0:00:00 0.019 0.118 0.056 0.113 0.113 3 www.codero.com Linux 0:00:00 0.019 0.197 0.063 0.348 0.616 4 www.singlehop.com Linux 0:00:00 0.023 0.178 0.074 0.520 0.852 5 Virtual Internet Linux 0:00:00 0.027 0.207 0.048 0.099 0.099 6 Server Intellect Windows Server 2008 0:00:00 0.027 0.066 0.080 0.163 0.404 7 Multacom FreeBSD 0:00:00 0.027 0.141 0.105 0.217 0.595 8 www.netcetera.co.uk Windows Server 2008 0:00:00 0.031 0.105 0.045 0.094 0.190 9 Swishmail FreeBSD 0:00:00 0.031 0.102 0.051 0.102 0.268 10 ServInt Linux 0:00:00 0.035 0.208 0.062 0.129 0.321
INetU was this month's most reliable hoster, failing to respond to only three of Netcraft's requests. The hoster has a consistently good record, last month ranking third and regularly appearing in the top ten. INetU offers managed hosting services and prides itself on its high level of customer service.
Second place this month is Rackspace, which offers managed, cloud and application hosting from its nine datacentres in the U.S., the U.K. and Hong Kong. Rackspace offers "Fanatical Support" allowing customers to contact the company 24 hours a day.
Codero ranked third this month, with only five failed requests in November. Codero appeared in the top ten hosters in September and October but this is the first time it has been in the top three. The company offers dedicated and managed hosting aimed specifically at the needs of small businesses.
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.
Information on the measurement process and current measurements is available.
Just a few hours after having its DNS servers terminated by a US company, WikiLeaks has anounced a move to a Swiss domain: wikileaks.ch. The domain is registered by the Pirate Party of Switzerland and it currently points to a single IP address in Sweden.
This move increases the resilience of the WikiLeaks site. Unlike wikileaks.org, the wikileaks.ch domain is not registered with a US company and is thus less likely to bow to pressure from the US government.
WikiLeaks also points out that "Free speech has a number", referring to the Swedish IP address that can be entered into a browser's address bar (http://188.8.131.52). The Swedish website does not host any WikiLeaks content; instead, it redirects browsers to an IP address in France, which does host the content (http://184.108.40.206)
French company OVH has now delegated a block of 16 IP addresses to WikiLeaks, which suggests more than a temporary relationship between the two organisations:
inetnum: 220.127.116.11 - 18.104.22.168 netname: WIKILEAKS
Curiously, the wikileaks.ch domain is configured to use EveryDNS.net as a DNS provider. This is the same US company that terminated DNS services for the wikileaks.org domain earlier today. It could be interesting to see what happens next in this cat and mouse game.
Real-time performance graphs for wikileaks.ch can be viewed here.
WikiLeaks has been taken down again. Around 04:00 GMT this morning (Friday), DNS lookups on the wikileaks.org domain stopped working, effectively cutting the domain off from the whole internet. Neither cablegate.wikileaks.org nor www.wikileaks.org can currently be resolved to an IP address.
WikiLeaks later tweeted that the domain was "killed" by US company EveryDNS.net. This was a potential weakness that Netcraft identified back in October, when WikiLeaks temporarily stopped using US-based web servers to host the Iraq War Logs content.
Earlier this week, Joe Lieberman of the United States Senate Committee on Homeland Security and Government Affairs had encouraged other companies to terminate their relationship with WikiLeaks. It is unclear whether this influenced EveryDNS.net's decision, as they claim it was due to the DDoS attacks against the domain. A statement from EveryDNS.net said, "The termination of services was effected pursuant to, and in accordance with, the EveryDNS.net Acceptable Use Policy." EveryDNS.net claims to have provided sufficient warning to WikiLeaks, noting that, "Any downtime of the wikileaks.org website has resulted from its failure to use another hosted DNS service provider."
The committee issued another press release yesterday, announcing their intention to go after WikiLeaks by amending the Espionage Act. Lierberman accuses "Julian Assange and his cronies" of hindering their war efforts and creating a hit list for enemies.
WikiLeaks could get their sites up and running again by using different DNS servers, such as the French ones used for the Iraq War Logs in October. However, the wikileaks.org domain is still registered with a US company, Dynadot LLC, which could be 'persuaded' by the government to prevent such modifications, or even suspend the domain.
Amazon has finally pulled the plug on WikiLeaks, leaving the whistle-blowing website unavailable until the traffic was redirected to Europe. WikiLeaks first directed the traffic to Sweden, and then included a second server in France. WikiLeaks announced the move on their Twitter stream:
The United States Senate Committee on Homeland Security and Government Affairs subsequently issued a press release announcing that Amazon had severed ties with WikiLeaks. The introduction to this announcement clearly states that Amazon.com decided to terminate its relationship with WikiLeaks, although the government may have spurred this decision by reportedly asking, "Are there plans to take the site down?"
The committee contacted Amazon on Tuesday after reading press reports that the WikiLeaks site was being hosted by Amazon. The site was taken down by Amazon the following morning. This could suggest that the government was able to exert some influence on the decision – WikiLeaks had been using Amazon's EC2 hosting service since October, when the Iraq War Logs were published. The cablegate site also used EC2 from the moment it was launched on Sunday.
Incidentally, two sentences in Committee Chairman Joe Lieberman's statement may have been added as an afterthought, or added by someone else, as it appears in a slightly different colour to the rest of the text in the statement:
The chairman encouraged foreign companies to make the same decision as Amazon, although whether this will happen remains to be seen.
WikiLeaks is now served from two IP addresses in Europe: one is hosted by Bahnhof Internet in Sweden, and the other is at OVH in France. Both www.wikileaks.org and cablegate.wikileaks.org are being served from these IP addresses, and have been showing good response times since the move.
Real-time performance graphs for both sites are available here:
Despite still being developed, HTML5 is already in use on more than 1% of the world's websites.
Netcraft's December Web Server Survey found the HTML5 DOCTYPE on 1.06% of homepages. An additional 0.05% of sites made use of new HTML5 features without explicitly declaring the correct DOCTYPE.
HTML5 is the next major revision of the HTML standard, and looks set to supersede HTML 4.01 and XHTML 1.1 with its support for video and audio playback. Microsoft has recently shifted its strategy on Silverlight as a cross-platform solution and now wants to implement standards-based HTML5 really, really, really well in Internet Explorer 9.
Earlier this year, Google also announced that it was shifting effort towards bringing their now-deprecated Gears API capabilities into HTML5 standards. Google's Chrome browser uses the same WebKit rendering engine as Apple browsers, with Apple boasting support for HTML5 on each of its new mobile devices and Macs.
Desktop browser support for the full set of new features in HTML5 is still rather patchy, although it should be noted that the HTML5 specification is still a working draft and subject to change. Many web designers will be reluctant to use the newest features just yet, as a significant fraction of their visitors will be unable to enjoy the content as it was intended. This is clearly demonstrated by the rarity of HTML5 elements such as canvas (appearing directly on only 0.012% of homepages), video (0.011%) and audio (0.003%).
In the December 2010 survey we received responses from 255,287,546 sites.
This month's largest change in market share was seen by nginx, which gained 0.59 percentage points and now serves 6.62 percent of the hostnames in the web server survey. The increase of 1.85M hostnames is mainly due to 656k Savvis hostnames moving from lighttpd to nginx, and 452k new hostnames on BurstNet.
The biggest losses in market share this month were seen by Microsoft, which lost 0.48 percentage points (but gained 85,564 hostnames), and lighttpd, which lost 0.32 percentage points. Many of the 761K hostnames lost by lighttpd can be explained by the large number of Savvis hostnames moving to nginx. The other major web server vendors all gained hostnames whilst losing small amounts of market share.
Open source HTTP accelerator Varnish gained 545k hostnames. A recent blog post on the varnish site identifies WikiLeaks as one particularly prominent user of the software, with both cablegate.wikileaks.org (performance graph) and warlogs.wikileaks.org (performance graph) served by Apache via Varnish.Total Sites Across All Domains
August 1995 - December 2010Market Share for Top Servers Across All Domains
August 1995 - December 2010
Developer November 2010 Percent December 2010 Percent Change Apache 148,085,963 59.36% 151,516,152 59.35% -0.01 Microsoft 56,637,980 22.70% 56,723,544 22.22% -0.48 nginx 15,058,114 6.04% 16,910,205 6.62% 0.59 14,827,157 5.94% 14,933,865 5.85% -0.09 lighttpd 2,070,300 0.83% 1,308,935 0.51% -0.32