Today my monitoring alerted me that the server on DO is down. Checking in the console I found the droplet in a stopped state. Started it back normally, DO support team replied in a ticket that droplet was killed by Out-of-memory on the hypervisor. Luckily this resulted in just a minor corruption of MySQL tables. I’d like to know if this event is considered “ordinary” by DO team, as support tried to upsell optimized droplet to me as a “cure”. Anyone else experienced this? I find this incident very disturbing, even more so because droplet was not started back automatically after being killed.
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!
Hey there,
This is not “ordinary” behavior. What you describe was a hypervisor malfunction. I’ll provide more details in the ticket.
Eris
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.