The scheduled maintenance has been completed.
May 18, 17:55 ACST
All Melbourne VPS nodes have been rebooted.
If any customers are experiencing a problem on the nodes in locations which have already been listed as completed please advise us. Further maintenance on remaining cities will continue later today with updates being posted as applicable.
Apologies to customers affected by the extended downtime on mel3kvm node.
May 18, 13:33 ACST
mel3kvm node has been restored. Some filesystem issues on the root partition caused a failure in the automatic reboot - these have been fixed so services on this node are now restarting.
Maintenance will continue once this node is fully operational and customer services all resumed.
May 18, 13:12 ACST
All Adelaide nodes have been rebooted.
We are currently performing checks on mel3kvm as the OS is not loading after a reboot correctly. All other Melbourne node reboots and other maintenance is paused temporarily while troubleshooting this node is prioritised.
May 18, 12:59 ACST
Sydney, Perth and Brisbane VPS nodes have all been rebooted.
If you are a customer with a service still offline in these locations please check the Solus control panel VNC console to verify your service is online. If you are unable to start the VPS or experiencing any problems please open a support ticket for assistance.
Further updates will be posted as we progress.
May 18, 10:44 ACST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 17, 20:00 ACST
This is affecting VPS services only.
Over the 48 hours following 20:00 ACST on 17th May we will begin rolling reboots of all VPS nodes in all POPs in the following order:
- Hong Kong
Reboots will be performed one node at a time; customers with multiple services will not have multiple services affected at the same time if they are on different nodes and/or in different geographic locations.
This is required to ensure continued security due to high priority software/kernel updates in relation to a recent Intel-CPU related security vulnerability.
Most services are expected to be disrupted for a maximum of 10 to 15 minutes as the underlying hardware reboots.
Apologies for the short notice however the nature of the security patch means a long delay before maintenance is not viable.
If the reboots are completed prior to the 48 hour window this status entry will be closed off.
May 16, 17:23 ACST