Our teams noticed multiple nodes stuck on internal tasks (reboot, stopping, archiving...).
We are currently focused on getting it solved as fast as possible, and will update this status as soon as we have additional details to share.
We are truly sorry for any inconvenience caused.
28/01/19 1830Z (1930LT)
The issue has been resolved and servers are now starting/archiving as expected.
28/01/19 1530Z (1630LT)
The product team has identified the root cause and is working on a fix.
We do not have a precise ETA yet, but will update this status asap.