We are currently weathering both a PSU meltdown and disk failure (with full compliment of side effects) on the main squid-cache.org server. The Squid sysadmin are all working on it as fast as possible.
mail, bzr, rsync went out a few days ago, and while that was still being fixed today DNS followed for a short period taking out access to the working servers. DNS is active again now but it may take some time for other services to resume connectivity.
Mailing lists and public repository access are not yet available. Donations towards the purchase of a new server are greatly appreciated and will allow us to buy better hardware.
Apologies for the inconvenience.
UPDATE: The main website http://www.squid-cache.org/ is alive again.
UPDATE: some progress to report now …
* bzr repository services have been fully resumed.
* www server content updates have been partially resumed. This may result in some temporary inconsistencies between visits to http://www.squid-cache.org and between the main site and mirrors.
* we now have a loose estimate of 10-15 days to get a replacement server.
… and Murhys Law has not finished with us yet:
Some security vulnerabilities were reported this past 10 days. A new squid-3.4.8 package has been released to resolve those. All users relying on SNMP or the pinger helper are advised to upgrade, this link provides a stable download URL while the main site mirroring and FTP services are recovered. Others are not vulnerable, so please wait for our troubles to reside and your usual upgrade channel to provide updates.
The SNMP details can be found here, pinger bugs are still being analysed to decide if they meet the criteria for a CVE allocation.