Digital Ocean killed my droplets and gives a vague reply

I actually moved over to Linode because of similar anomalies. I had a container I was running my personal site from. Paid my bill on time every month. Got distracted with work and hadn't updated it in a while. One day I go to check on it and the site is down. Head to DO to restart it... and it is just gone. Like it never existed. Didn't even bother trying to communicate with them I was so angry. Been really happy with Linode.

This is not unique, unfortunately. I have been battling with them for the last two months now and I am in the process of moving everything away from DigitalOcean. Something has changed over there and they have zero tolerance concerning everything.

My account was overdue by $10 (after being paid on time for close to 5 years), I asked for a deadline extension of 1 week and it was declined. They have already turned off all of my droplets and are now threatening to delete everything with no recourse within the next three days.

Again, not unwilling to pay, I was merely asking for an extension by 7 days for $10 and they declined my request.

I have been frustrated a bit with them as well because in the last few months, more often than not, a droplet hangs without any issues and they cannot tell us why. The only way is to reboot it. We were paying them over 5K/Month for some of our services and now I am moving everything to AWS EC2. Yes, I know that AWS can have its own issues but i have found their support to be better and so far more reliable infra than DO. I love DO for its simplicity and cost but lost trust recently due to those "droplets hanging suddenly" issues.

That bites.

At the same time, this is why the concept of "business continuity" exists. If you are running a hobby-level service, it may not be worth the trouble, but for anything where the continued existence of the service truly matters, you should have a plan in place of what to do when (not if) your host blows up and leaves you with nothing. That should include the ability to re-launch the code/database/server/whatever on a new host, and restore the latest data backup to that new host.

I get that planning ahead for such things increases the work to launch a service - but anything short of it means you are not in control of your own destiny.

You actually made me go look (I have a droplet as a Wireguard VPN, that I too use only rarely):

    $ uptime
    10:40:45 up 654 days, 11:32,  1 user,  load average: 0.08, 0.02, 0.01

I can't use it for getting to Streaming sites when abroad (they all blacklist DO's IP blocks), but it works for just about anything else and it's got really fat pipes.

Had trouble signing up for Digital Ocean, called up their support team, got a really bad response and decided I'll just blacklist them.

If they were giving me trouble during sign up then what hope was there for support afterwards?

Probably your server leaked, just move on. AWS lightsail is good enough.

Are you saying that is the only message you got? Maybe you got compromised?

Have you tried reaching out to them?

So go to any provider website, order bare metal server where proxmox installation will cover your requirements. Own VPS hosting is always better then cloud vps.

Tell HN:

Not your machines, not your servers