Ask HN: DigitalOcean Destroyed All My Data, Any Legal Recourse?
I will follow up with a long post documenting timeline etc and all correspondence with them (it's not that much since they never respond). I have been a (paying) DigitalOcean user for more than 2 years for personal projects, and recently convinced a start-up that I work for in Tokyo to move off of Heroku and onto Digital Ocean. Everything fine for 2 months, then all of a sudden I get user reports that the site is down. I check and my account is locked and all it says is to submit a support ticket. No warnings of an issue, not even a mail saying that they turned off instances etc, just silently they lock my account. I submit a ticket and they don't resopnd for a week, I submit another, finally after 5 weeks, yes 5 weeks, I get a response saying that I login from too many locations and the lock is now removed, but they destroyed all instances. How can this even be anything close to standard practice to without warning destroy all instances of a paying user for over 2 years?! All databases everything completely gone forever. I guess this goes to show why you should always not trust 1 cloud provider, but this is just so incredible to me that they can on a whim without warning or justification just destroy all your data, is there any legal recourse against this?
27 comments
[ 4.5 ms ] story [ 60.4 ms ] threadIn any case, this is a horrible thing for a business to do to a paying customer.
I want to caution other commenters that many of these stories have turned out to not be what they first appear.
In my opinion you lost your data because you didn't make backups.
Treat it as a temporary server that can disappear at any time, have automated backups and streaming database replication, then have an automated restore script that you test periodically.
If the server goes down, restore somewhere else.
You store the data in a different place to DO, maybe at home or a cheap VPS somewhere else.
But laws are really complicated and I don't even attempt to understand them.
If this service was successful and profitable, I can't imagine waiting 5 weeks. I'd be in full nerd rage after 1/2 day of being down, and would be spinning up new servers on another provider.
Curious to see the full post though before jumping to more conclusions.
I did go into full nerd rage because I can't believe they would do this to a startup, I had the critical stuff running in <1hr on Linode, but took a day for everything to be rebuilt since I had to redo everything w/out access to backups or images.
Always happy to chat live with you, just open up a ticket or email me at the address above.
(1) Gitlab/Github for source code (almost free)
(2) automysqlbackup (or similar) to an S3 bucket for your database (very cheap) using S3FS
(3) Make sure you have a way to reproduce your entire server environment using fabric, ansible, chef, puppet (or Docker images) that is also in source control
If you have PROD code, this is normally called DR (Disaster Recovery)
I realize that is vague, but it's a bit of a difficult thing to discuss without exposing private data. If I so much as say "Just don't do X" then I'm effectively saying Client A did X. Tough waters to navigate.
I hope that helps a bit at least.
At least in Tokyo I know plenty of people who are running PG on DO in a docker instances and just doing backups on DO cause its cheaper than something like heroku managed PG so if I was one of them (I kept my data layer off of DO) I would be completely destroyed by this. So I tell everyone I know now at meetups about this experience and so happy to share specific details.
They told me I log on from multiple locations (OMG I have a laptop and work while I travel, busted) and that I had a gmail address on my account.
The most agregious thing is that if their trigger happy "security and trust" flagger flags you, there is no warning where they reach out to you, they just destroy your instances, don't tell you about that either until you logon and are asked to file a ticket if you want your account unlocked...then a month later will unlock it for you but everything nuked.