Apache released an update which changed the approach in handling UDS URIs used to proxy connections from Apache to PHP-FPM. This caused a few websites to display Error 500 for a short time before an update patch was released to correct the issue.

All websites have been successfully transferred to the new servers and the servers are fully set up. No issues have arisen so far, so we are marking the servers as "Fully Operational".

We are upgrading to newer servers over the next week. The servers have improved performance, storage, security and reliability. All websites will be transferred over the next 7 days so either Server 1 or Server 2. We anticipate there will be a couple of minutes downtime (in the form of an SSL certificate reissuing for the new DNS records) for each site when we make the transfer. We will manage all DNS and file transfers for you. Please refer to the above section with the status of each server. If all work is complete, the light will be green and it will read "Fully Operational" next to the service.

NGINX upstream connection timeout occurred. The service was restarted and resumed without and problems. Total downtime was 13 minutes from first report. (19:43 - 19:56)

We are upgrading some packages and running security scans on our server today. There is no anticipated downtime.

There was a temporary interruption caused by an OS vendor PHP script being unresponsive. This issue was rectified by restarting the service. No data loss occurred and the system resumed without and problems.Total downtime was 16 minutes from first report. (16:47 - 17:03)

Following the hardware fault, we decided to have all hardware replaced on the server with brand new components. This should minimise the chances of a future hardware fault. As all sites were already pointing to the secondary server, there was no interruption to service. Following a successful server re-image of our primary server, all websites were added back to the primary server and DNS zones were updated to point to the primary server again.There was no downtime during this operation

Our primary server suffered a severe hardware failure which was most likely linked to last months hard drive failure. This resulted in the system to go into kernel shock and was only able to be booted in safe mode. This did not allow our server management platform to load and therefore all services that ran on our server were not operational. The primary server then wrote this issue to the configuration files which was carried through to our secondary server too - resulting in its failure. Fortunately, we were able to install a recovery file from the previous day onto the secondary server and boot as normal. We then ensured that all sites were recovered fully from the backup server and pointed all DNS to the secondary server so all services could resume. Until we can establish what the error with the primary server was, we will run all sited on the secondary server and backup the data to the backup server. There was no data loss as a result of this.Total downtime was 9h 21m from discovery (21:32 11/04/2021 - 06:53 12/04/2021)

Following the hard drive failure, we ran tests on the hard drives to pinpoint any issues. Although there were no serious issues identified, HD0 was running slower than we would like so we decided to replace this with a new one. The new hard drive was then rebuilt using a mirror of HD1 and then the server was rebooted using a full RAID setup again. There was no data loss as a result of this.Total downtime was 4m (10:43 - 10:47)

Our primary server suffered a hard drive failure. As this server has a RAID setup, the second hard drive was recoverable. The system was then rebooted using the second hard drive. We will run tests on the failed hard drive to identify what the issue was. There was no data loss as a result of this.Total downtime was 2h 21m from discovery.

Our servers has scheduled maintenance to install essential security updates Expected downtime for up to 5 minutes while this is carried out.Total downtime was 5m (20:01 - 20:06)

Our servers has scheduled maintenance to install essential security updates. Expected downtime for up to 30 minutes while this is carried out.Total downtime was 24m (00:16 - 00:40)