Shared Hosting Issue
Timeline · 1 update
- investigating Jun 29, 2026, 01:26 AM UTC
We are investigating an issue with the shared hosting server (web0). Accounts have been live-sync'd to a backup server and service is currently restored.
AllHost had 6 outages in the last 2 years, averaging 0.2 incidents per month.
There were 6 AllHost outages since November 11, 2025. Each is summarised below. Incident details, duration, and resolution information.
We are investigating an issue with the shared hosting server (web0). Accounts have been live-sync'd to a backup server and service is currently restored.
"Sumatra" LON0 HV is undergoing an emergency restart to resolve issues following an update. Service should be fully restored within the next 15 minutes. 00:46: Issues are being investigated, the emergency maintenance window is being extended until 01:30 UTC+1 at this time. 01:15: All virtual servers are powering back up now. Service is expected to be fully restored within the next 15 minutes. 01:30: All virtual servers are back up again now. Please contact our support team if you have any outstanding issues.
Various servers are being restarted to apply critical security updates. If your service is unavailable for more than 2 minutes after 13:45 UK Time, please open a case with our support team.
We are currently investigating an issue affecting partial incoming network connectivity to services from certain locations/ISPs. UPDATE: Issues appear to have subsided, we are monitoring the performance and awaiting information of the root cause from the network carrier.
We are investigating service unavailability for services on LON-HV1. 11:39 - This appears to have been a datacentre network connectivity issue affecting the rack that this server is located in. Services should be restored now.
We are currently investigating an issue with one our servers in the Coventry datacentre. 23:42 Update: The server is back online and services should be restored. We will continue to look into the original cause of the server interruption. Post-mortem: We believe the issue was caused by a storage device soft lock-up. This server previously had over 500 days over time and we are considering the issue to be transient. Should our monitoring detect anything untoward or any further unexpected issues occur, then we will start planning a hardware replacement.