Live data from Hacker News

"DigitalOcean Killed Our Company"

twitter.com

531–540 of 620 posts

Re: "DigitalOcean Killed Our Company"

#531
post #370
post #322

Earlier quoted context omitted.

If a cloud service is supposed to be ready for production, then customers should be safe to assume that they will not simply be shut down, especially not without warning. Otherwise, the provider must make clear that the service is only for hobby use and not for commercial use.

Every single major cloud service provider will shut you down without notice if they detect obvious fraud.

What kind of fraud do you have in mind and do you know of a case in which, for example, Azure switched off an enterprise customer due to unusual usage patterns?

Re: "DigitalOcean Killed Our Company"

#533

Earlier quoted context omitted.

Agreed. I actually had to reread that a few times because I could not believe that someone actually approved of that text. That text suggests larger organizational problems within the company.

If you explain why, you give the actual abusers clues as to how to avoid detection. It's common place behaviour for companies to _not_ reveal details.

It's a spectrum; being opaque and stone-cold to that degree is shitty customer service.

Re: "DigitalOcean Killed Our Company"

#534

Earlier quoted context omitted.

I know many engineers who are not that fluent in English whom you would never contemplate qualifying as illiterate; you would quickly see that (1) they're encumbered by English and (2) are obviously extremely proficient technically, and literate. People who would make gratuitous grammatical mistakes but have read more classics than the average American college graduate. I can easily count many just thinking of it.

You're arguing here against something I didn't say. You took one word from my statement -- "illiterate" -- and built a whole new argument around it which was never mine to begin with. I don't think you're doing it intentionally, I suspect it's just because you have a particular sensitivity on this subject. Either way I don't think I can say anything here that'll get a fair treatment from you.

Not that person, but you said this:

> There is functionally no difference between trying to interact with talented support staff who aren't fluent in your language, and trying to interact with illiterate support staff.

That statement reeks of ignorance. It seems you have almost no experience with other languages than your own, or you would know that communicating while being non-fluent or with a non-fluent works just fine most of the time. Sometimes misunderstandings happens and it can be a bit slower but that is all.

Re: "DigitalOcean Killed Our Company"

#535
When will the wheel turn again, when we learn it is best to have at least one copy of your Data in your hand? Not your Cloud VM, Server Rented somewhere, but actually in a HDD within your own premises.

Re: "DigitalOcean Killed Our Company"

#536
I am sorry they had this problem. Stories like this about edge cases with cloud deployments make my conviction stronger to always: 1) have a data backup plan that uses a different cloud provider unless you have so much data that you can’t afford the extra bandwidth and storage costs. 2) if possible don’t rely on unique cloud platform services and be ready to bring a system up quickly on another service provider.

Re: "DigitalOcean Killed Our Company"

#537

This is probably going to get buried in the replies, but I had a similar experience with DigitalOcean about a year ago with my account getting permanently locked with very little explanation and no way of getting it back. It's still locked to this day. I was just a student using my Github student package credit, but I was pretty appalled by the service from DO and vowed never to buy from them. Unfortunately, my ticke…

“Warmest regards”.

Wow. F*ck you too.

Re: "DigitalOcean Killed Our Company"

#538
post #102
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."

You'll be surprised how many companies are "all in" on AWS or Google Cloud, including ALL backups.

Indeed. I'd urge everyone here to pay attention how many sites/companies are dead in the water the next time there is a full blown AWS outage and see if they are as quick to heave the same criticisms at those fortune 500 companies that they are at this two man operation.

What happened w/ Digital Ocean is inexcusable, and has potentially dire consequences for two individuals livlihood. In the immediate aftermath of such an event, focusing on the devs percieved lack of disaster preparedness seems petty.

Re: "DigitalOcean Killed Our Company"

#539

Earlier quoted context omitted.

Should we be concern about our 40+ droplets with DO now? We built our business on DO, we really can go bankrupt as well as our 30+ clients if anything like this happens to us. Please change your support system ASAP otherwise we will be switching to another platform. We are expecting a very serious response from you.

Do not use DO. The very fact that their default automated response to spam is prod downtime is unacceptable. It requires so many failures in understanding the service being provided across the company for this decision making process to have ever actualized that there is no reasonable expectation of safety or trust from DO at this point.

Every cloud company has anti abuse systems that will limit your access to their APIs / take down your machines if abuse is suspected - for example if it looks like you're mining bitcoin. Your prod isn't any different from your staging for them

Re: "DigitalOcean Killed Our Company"

#540
I really liked https://hyper.sh, they provided hosting for running Docker containers. They handled this same case by having a limit on every account by default. When I requested to increase that limit, they asked about my workload, I explained them briefly, they allowed the limit increase and all was good.
Post reply on HN