We've had to unfortunately reboot your Droplet xxxdb due to an issue on the underlying physical node where the Droplet runs.

We are investigating the health of the physical node to determine whether this was a single incident or systemic.

If you have any questions related to this issue, please send us a ticket. https://cloud.digitalocean.com/support

Happy coding, DigitalOcean -----------------------------------

What I no so happy about this..

a. Didn't give me advance notice, so that I can prepare cutover from other droplets.

b. Although they claim they have rebooted my droplet, they didn't check if the droplet booted correctly, in fact, this particular instance been down for more then 3 hours.

c. Worst, somehow during reboot the droplet to new HW, the system revert the droplet to original kernel, resulted a lot of underlying services not working... I have to spend another 2-3 hours to setup new droplet again.

d. After I complains this to their support people, and explain this is totally not acceptable, as the whole server been setup for a very important client of me, and for unplanned downtime, we have to pay huge fine. Their Director then credit me USD20. Discounting the fact I have to pay the fine, additional time to setup the droplet..

------------

I ask around my friend who use Digital Ocean before, all have bad experience using DO, some droplet will reboot to READ only, some of droplet is lost forever..

Conclusion, use DO for your development/testing server...Never Never use it for your production server, at least not yet.