All slices on node 17 are confirmed online and operational.
The node was rebooted due to human error and there were difficulties bringing the node back online due to a hardware glitch. Our engineers have resolved all issues and everything is back online.
As always, if you feel your slice is still affected, please call the support line or open a ticket so we can review the issue.
Our cluster engineers have identified the problem and are bringing affected slices back online. We expect full resolution shortly, and will update when we confirm all slices on node 17 are back online.
Node 17, one of the slice host nodes, has failed with a cause as yet unconfirmed. Our sysadmins are looking into it now.
There was a minor issue with the mysql50-2 slice which we resolved in under a minute.
We experienced a load spike on one of the database servers on ey01 (mysql50-2). Only customers on that database server were affected. The database outage lasted for approximately 15 minutes, but did result in some sites being inaccessible. Everything is operating normally now.
We have been alerted to an issue on mysql50-2 on ey01. We will update shortly.
All slices affected by the ey00-n00 issue have now been rebooted and are up and running. There was an initial issue getting the slices back up, but this has been resolved and will be implemented in the future to ensure it won’t happen again.
We’re currently bringing up the slices on this particular node.
It currently looks like the node has lost connection to the SAN. Our sysadmins are currently working on this issue.
We’re currently experiencing an issue on ey00 n00 and some customers may be experiencing issues with their site. We’ll update as soon as we have more information.
