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!
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.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Click below to sign up and get $100 of credit to try our products over 60 days!