22 Aug 2016
18:31 UTC
Paul Cammish
It looks like all Cloud Servers have been successfully restarted on new heads, and everything has returned to normal.
As the servers are now running on a different head, we don't expect any further issues from this.
The affected head will remain offline while diagnostics are performed and the underlying issue resolved.
22 Aug 2016
18:26 UTC
Paul Cammish
We experienced an issue just after 18:30 where the disk array for one of the cloud heads stopped responded and switched to read-only.
After some checks, this initially didn't impact the functionality of the VMs as their disks are on separate servers, but it did meant they would not be controllable, and may have behaved erratically.
However, we have since taken the head down to investigate the issue, and enable management of the Cloud Servers, which unfortunately means closing them and restarting them on other hardware.
All affected Cloud Servers are all be rebooting now on a different head, and we expect them to be back up in the next few minutes if not already.