Live data from Hacker News

"DigitalOcean Killed Our Company"

twitter.com

91–100 of 620 posts

Re: "DigitalOcean Killed Our Company"

#91

Not even surprised by the way Digital Ocean have handled this. They pulled something similar on me back in 2014 at a previous company I used to work in. They essentially shut down my account and did not even let me get my backups out.

It seems like there should be a middle-ground between all-on and all-off. If I'm paying customer, I should be able to access my account in some capacity even if some abuse related issue closes off server access.

Re: "DigitalOcean Killed Our Company"

#92
post #40

Best Twitter comment (grammar errors and all): "And if your full business relies on one tech partner (no offsite backups) your not doing your tech job right."

Well, what can we say, they're not wrong.

Ideally partners should be trusted (and trustful), in practice, they aren't

Though trusting DO/AWS/GCP, etc is much more reliable, than, let's say, betting your whole business on somebody's proprietary API (like an FB game, an Linkedin API something, etc)

Re: "DigitalOcean Killed Our Company"

#93
post #62
post #42

Earlier quoted context omitted.

"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.

I accidentally left a 24xlarge instance running for a month without realizing it and they looked at the activity and were totally cool about zeroing the bill for that instance for the month. Basically gave me us a $2000 credit.

It does probably help that I said I would be careful not to do that again and had already put in a CloudWatch Alarm to automatically power-off the instance after a set period of idleness before filing the ticket.

Re: "DigitalOcean Killed Our Company"

#94
post #6

I’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.

I think it's the opposite. The cofounder intervened and the access was restored. This would never happen with Google or Amazon -- once they lock you out, your entire business is permabanned, and you won't be able to reach any human with authority to help you.

Re: "DigitalOcean Killed Our Company"

#95
post #40

Best Twitter comment (grammar errors and all): "And if your full business relies on one tech partner (no offsite backups) your not doing your tech job right."

I mean, sure, but it sounds like it’s a 1-man technical operation.

Being just one person is no excuse. I am a 1-man technical operation too, and I know that backups have to be stored on two different locations.

Re: "DigitalOcean Killed Our Company"

#96
post #42
post #2

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). 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…

For the customer, there is a big difference. Hitting an API to send an email and a text 48hrs before shutting down services is a common courtesy and easily automatable.

The host should throttle resources in the interim if its at risk of running up massive bills or adversely impacting other clients. None of this is breaking new ground, there isn't a good reason for large hosts to act like shit.

Re: "DigitalOcean Killed Our Company"

#97
post #40

Best Twitter comment (grammar errors and all): "And if your full business relies on one tech partner (no offsite backups) your not doing your tech job right."

I agree. Putting all your eggs in one basket these days indicates poor decisions or risk assessment.

> Digital Ocean "Trust and Safety"

Does this phrase give anyone else the heebie-jeebies? They deliberately locked his account without looking at previous metrics over the previous months to conclude this was obviously not a concern, and why?

Things that have crossed my mind:

Is their automatic system was poorly tuned? Was this deliberately initiated? If so, why?

Re: "DigitalOcean Killed Our Company"

#98
post #82

Does anybody know what they actually do? I dug around to find a Wayback version that actually had text. I understand the words on their own, but when put together I get nothing: https://web.archive.org/web/20181030015237/https://raisup.co...

Sounds like they give companies a feed of startups they might be interested in acquiring?

Re: "DigitalOcean Killed Our Company"

#100
post #22

Earlier quoted context omitted.

The number of employees shouldn't be the deciding factor when you are a tech company that apparently has fortune 500 companies as customers. I'm not talking 5 9's redundancy. I'm talking grab a backup once a week or something, anything, to help mitigate a scenario like this. According to the thread, they lost ~1 year of data. That should be unfeasible to a company serving customers, let alone Fortune 500 customers. D…

Plenty of one man companies have Fortune 500 customers. Most are ran like the startup in question, as basic disaster mitigation is overhead. Don't expect the world from one guy keeping a company afloat, unless you enjoy disappointment.

From my experience you don't have fortune 500 companies as a customer as a >50person,>5mil revenue company. You may have employees from such companies paying you via their business credit card, but will never get through real procurement without documented SLA procedures which are required to prevent a scenario exactly like this.
Post reply on HN