Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
I have the same behavior here … <br> <br>made : <br>sudo service apache2 stop <br>sudo service mysql stop <br>halt <br> <br>and after some minutes still active … only resolved after : shutdown + power off. <br>is this the right way to do it ?
I have had the same problem. I have dealt with it clicking “Power Off” once I know it is already turned off and the status is updated almost immediately. Once you have done that, you can boot it again.
The backend will automatically check the state of the virtual servers and update them as necessary, whether you do a halt or a shutdown it will still be checked the same why by the hypervisor and should make no difference. <br> <br>Occasionally we’ve seen some backlogs on the scheduler which delays this processing so the state of the server in the Cloud may not be accurately reflecting the live state of the server and we’re working on improving the time it takes for the Cloud to register a change in state. <br> <br>If it happens frequently please open a ticket.