Here’s a recent image of the graph [it updates every hour].

 
Three things strike me first off about this graph:

• The lack of a bell curve. Though, I would explain this by noting that given the percentage of people able to obtain very close to the 8128 maximum sync rate is 37.8% – not the fairest, or most even, distribution of spread. Remember, Enta is a professional ISP attracting net-savvy users; I would hazard a fair guess that a lot of people specifically move to a location that is in good reach of their local exchange – I know i did. When BT releases 21cn i would expect a bell curve to exist around the 6000-10000 mark. Only time will tell, mind.
• As referred to above, Which? magazines continued insistence that broadband provider’s are setting too high a customers’ expectation as to speed’s possible on their ADSL line appear to be inaccurate. Setting aside the reasoning for the graph’s data in point 1, there is a significant proportion of customers on a very acceptable BRAS profile.

  My personal opinion is that Which? magazine is making an issue where there is none. I have never experienced an ISP stating that they will provide 8mbit services, but rather can provide, if your line is suitable. If I was a cynic I would state that Which? are creating publicity for themselves by writing these reports. Unfortunately, I am only adding to their publicity.

• Not directly related to the graph, but to the ISP publishing it: Enta have taken an exceptionally positive step in publishing this data. At a time when ISPs are under-fire (see above), they have chose to make their data public for the world to inspect. Well done, Enta!
   
  NB: I fully recommend Entanet reseller, UK Free Software Network.

Whilst we’re on the subject of downtime, this link details the average website downtime for 2007

The average website downtime in April was almost exactly two hours.

March 2007: 119 minutes (99.73% uptime)
April 2007: 120 minutes (99.72% uptime)

Quite interesting statistics, I thought!

Things to note when not running Apache:

Make sure that /var/lib/awstats/ is chmod'ed to permissions that your webserver can read from. Here’s the cron code I used to make sure awstats updates itself every 10 minutes:

0,10,20,30,40,50 * * * * nobody [ -x /path/to/cgi-bin/awstats.pl -a -f /etc/awstats/awstats.conf -a -r /path/to/access.log ] && /path/to/awstats.pl -config=<domain name> -update >/dev/null

My webserver is securely running as nobody so it’s important the we use the same user to perform the cron job to update awstats’ datafile.

As mentioned previous, the important part here is making sure that this cron job can update files within /var/lib/awstats/. A chmod 640 will provide ample security here, allowing the webserver user to read and write, as well as allowing the group to read the file.

That all done, AWStats is now up and running and providing some interesting statistics..! ;)