Dude has no disaster recovery plan, so he throws a public hissy fit like a spoiled child. Public shaming as a customer support proxy is shameful. It’s a form of manipulation.
"DigitalOcean Killed Our Company"
61–70 of 620 posts
Re: "DigitalOcean Killed Our Company"
#62It's interesting how many companies simply shut down service rather than say give a warning and wait for a response (or at least start a clock). Granted that would require people to communicate and use some form of reason. Even DMCA for all its warts fires up a warning and has a response mechanism (granted other issues there).
"It's interesting how many companies simply shut down service rather than say give a warning and wait for a response (or at least start a clock)." I'm sure many people have started their companies firmly convinced that they'll give plenty of warnings and never automatically shut anything down. The problem is, you rapidly discover that doesn't scale, not even on a human level. You send your notice. 48 hours later, you…
This is exactly why AWS has relatively low default account limits, and you have to open a support ticket to raise them. It's largely to prevent run-away costs from surprising the customer.
Re: "DigitalOcean Killed Our Company"
#63Who is good about not locking accounts or taking similar actions? Apple and Google are both notorious for blocking things for no reason, is AWS or Azure any better?
Re: "DigitalOcean Killed Our Company"
#64Looks like Moisey Uretsky personally intervened fairly quickly: https://twitter.com/moiseyuretsky/status/1134547532149854208
That said, any company, especially one working with Fortune 500's, should have DB backups in at least two places. If they'd had the data, they could have spun up their service on a different hosting provider relatively easily.
Re: "DigitalOcean Killed Our Company"
#65It's interesting how many companies simply shut down service rather than say give a warning and wait for a response (or at least start a clock). Granted that would require people to communicate and use some form of reason. Even DMCA for all its warts fires up a warning and has a response mechanism (granted other issues there).
They locked my account, without refunding the ~$200 balance, with no reason given except "We reviewed the account and found it matches unusual patterns associated with violations of our Terms of Service and Acceptable Use Policy." When asked, they would not reveal which terms were violated.
No warning was given, and no way to retrieve any data. Fortunately nothing essential was lost.
Re: "DigitalOcean Killed Our Company"
#66I can understand why a cloud platform would proactively disable workloads that appear to be acting dangerously. At the same time it seems quite unreasonable that there's no mechanism for a customer to get their data back when their account is unilaterally shut down.
Re: "DigitalOcean Killed Our Company"
#67You know, there is usually an easy way to mitigate this. When you create an account, be sure to supply business information e.g EIN in the USA and see if you can do invoice billing. Once you get set-up as a business, most providers assume you know what you are doing. These sorts of things tend to slip through the cracks. If you are running is a business capacity, make sure you treat everything like any other business…
> Once you get set-up as a business, most providers assume you know what you are doing.
Is there any evidence for this? For all we know his DO account was set up as a business.
Re: "DigitalOcean Killed Our Company"
#68Earlier quoted context omitted.
Really? Big European VPS hosts like OVH just turn off your stuff until the problem goes away. Hardly fly-by-night.
Hmm, I've done lots of stuff on OVH that other hosts consider abusive, with nary a word of complaint from OVH. OVH seems to have this whole automation thing down cold, monitoring boxes for dying components and letting me run hog wild on their VMs without limit... The one time I used their phone support, the guy I got was fairly helpful. They seem like a hands off company overall.
If you get DDOS'd they will stick your VMs in a black hole until the traffic stops to protect their network, no matter how much you plead with them.
Good practice, actually, but it's something people usually get frustrated with and they're literally famous for doing it.
Re: "DigitalOcean Killed Our Company"
#69I’m certainly getting downvoted for this. Not at all trying to blame the original posters and victims: While they seem great for hobbyist and small business sites, there’s no way I’d trust Fortune 500 client business to something like DigitalOcean. I just don’t see the benefits over a more established operation like AWS, Azure or GCP. Saving $50 here and there isn’t worth it.
Your "established operations" are more expensive and GCP is newer than DO. Plus, getting the attention of someone to restore your account is probably easier in DO than in a faceless giant company like Amazon, Microsoft or Google.
AWS support is a lot more responsive even if you are not a big source of revenue. One time when I had an issue, I directly reached out to our startup program point of contact and they made sure everything was resolved by constantly following up with the interval team responsible and keeping me in the loop
Re: "DigitalOcean Killed Our Company"
#70Dude has no disaster recovery plan, so he throws a public hissy fit like a spoiled child. Public shaming as a customer support proxy is shameful. It’s a form of manipulation.
[deleted]