Further to my post about AOL 502 Errors it seems this issue may have resolved itself. I have been told that customers are now able to access sites via the AOL browser. Since nothing has been changed between yesterday and today this indicates it is a problem with AOL and not us.

After asking within the industry I have been told that other server administrators have also experienced this problem but it has generally resolved itself within a few hours. Based on this the culprit is likely to be the AOL proxy cache possibly becoming overloaded at peak times or being unable to route to our network temporarily.

I am pleased to announce we have now provisioned a freephone number which can be used to contact us for both sales and support queries.

I want to ensure AGUK continues to provide first class customer support to our customers. This was the main driving point behind getting a freephone number.

By using VOIP technologies and careful consideration of suppliers the cost of providing the freephone service is vastly reduced from what it once was.

Since we announced HTTP Compression across all web servers the response has been great. Many of you are extremely pleased with the bandwidth savings and speed improvements this has brought.

However we have had some reports that AOL users may experience “502 Server Congestion” errors when accessing sites. The servers are in no way congested so this was intriguing me as to what could cause this. After numerous attempts I managed to speak to someone at AOL. While they seemed not very knowledgeable about what I was asking they did give me a hint as to what the problem could be when discussing image compression. Since the problems only started to occur since enabling HTTP compression this became the obvious possible cause.