Live data from Hacker News

"DigitalOcean Killed Our Company"

twitter.com

461–470 of 620 posts

Re: "DigitalOcean Killed Our Company"

#461

Earlier quoted context omitted.

"you're responsible for doing all your own offsite backups" That's going to be true no matter which cloud provider you choose. Their ToS almost certainly include terms which allow them to kick you off and refund any monies for any reason whatsoever. Good luck if you bought into their entire ecosystem and can't move elsewhere on a whim.

That's going to be true no matter which cloud provider you choose My company provides services to fortune 100 companies, and we host literally petabytes of data on their behalf in Amazon S3, but we don't have offsite backups. We (and they) rely on Amazon's durability promise. We do offer the option of replicating their data to another cloud provider, but few customers use that service -- few companies want to pay ove…

I don't know the data you're holding. If it is sensitive data, like customer anything, would it infact make sense not to have offsite backup?

Reasoning: Your contract with Amazon promises durability and I'm sure there's a service level agreement with penalty/liability clauses. By implementing a redundant backup, you're replicating something that you don't legally need to have, double-or-more due diligence on the offsite backup security/credentials, and in case of a failure of Amazon create a grey area with clients "Do you have the data, or do you not?"

In short, there could be a very good business reason not to do offsite backups.

Re: "DigitalOcean Killed Our Company"

#462
post #250

Earlier quoted context omitted.

Accidents can happen. Don't really blame Digital Ocean for the accidental locking but this response is insane: https://pbs.twimg.com/media/D76ocofXoAY_xB5.png

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.

Re: "DigitalOcean Killed Our Company"

#463

Earlier quoted context omitted.

You've got an additional problem though, which is that this tells us you have two support channels: one that doesn't work (i.e. yours, the one you built), and one that does (Twitter-shaming). The first channel represents how you act when no one's watching; the second, how you act when they are. Most people prefer to deal with people for whom those two are the same.

I think it says a lot that this CTO joker flew in, regurgitated the standard-issue "we will endeavor to do better" apology and left without answering any of the very legitimate follow-up questions. I would never deal with an organisation that behaves like these guys.

Is there any response that would satisfy you?

Re: "DigitalOcean Killed Our Company"

#464
post #270

As DigitalOcean's CTO, I'm very sorry for this situation and how it was handled. The account is now fully restored and we are doing an investigation of the incident. We are planning to post a public postmortem to provide full transparency for our customers and the community. This situation occurred due to false positives triggered by our internal fraud and abuse systems. While these situations are rare, they do happe…

Are you aware that Viasat has blacklisted a huge amount of Digitalocean /24 subnets? I can't access many of my servers when I'm on a satellite connection in addition to other websites hosted on Digitalocean. I've talked with the Viasat NOC and they told me they were blocking Digitalocean subnets due malware.

This is probably worth it's own post, it would be very interesting to see more detail. I'm also probably certain that this is also not exclusive to DO.

Re: "DigitalOcean Killed Our Company"

#465

Earlier quoted context omitted.

I think it says a lot that this CTO joker flew in, regurgitated the standard-issue "we will endeavor to do better" apology and left without answering any of the very legitimate follow-up questions. I would never deal with an organisation that behaves like these guys.

Is there any response that would satisfy you?

It's been 7 hours, some follow up answers would be nice...

Re: "DigitalOcean Killed Our Company"

#466
Over the years, I have moved most of my VPS to vultr, and now only 1 droplet left in DO. This story again proves my mistrust towards them. I don't like AWS because it's too complicated for my use, but now I think we better have some backups.

Re: "DigitalOcean Killed Our Company"

#467

This exact same thing happened to me last year. I accessed my account abroad and they perma banned me. Support was useless and even with evidence did not believe who I was. I then somehow convinced them to give me temp access, which in my opinion is even worse. They didn't believe me about who I was and then gave me temporary access to an account. DO can't be trusted when their support team could so easily be sociall…

> They didn't believe me about who I was and then gave me temporary access to an account.

What???

Re: "DigitalOcean Killed Our Company"

#468
post #196

Earlier quoted context omitted.

I've been on Linode for 8+ years now (moved there from Slicehost when Rackspace swallowed them up) and their service (not necessarily customer support) has significantly degraded. Not sure I blame them though. They've become far more popular since I started with them and are probably doing their best to grow... but I no longer recommend them as I used to. Just my experience though.

That's how I feel about Scaleway. Scaling customer service is no easy task especially technical companies that require agents to have some understanding of the product.

I drop all traffic from Scaleway, they do not care about abuse coming from their network: https://badpackets.net/ongoing-large-scale-sip-attack-campai...

Re: "DigitalOcean Killed Our Company"

#469

Earlier quoted context omitted.

That's going to be true no matter which cloud provider you choose My company provides services to fortune 100 companies, and we host literally petabytes of data on their behalf in Amazon S3, but we don't have offsite backups. We (and they) rely on Amazon's durability promise. We do offer the option of replicating their data to another cloud provider, but few customers use that service -- few companies want to pay ove…

I don't know the data you're holding. If it is sensitive data, like customer anything, would it infact make sense not to have offsite backup? Reasoning: Your contract with Amazon promises durability and I'm sure there's a service level agreement with penalty/liability clauses. By implementing a redundant backup, you're replicating something that you don't legally need to have, double-or-more due diligence on the offs…

Regardless of durability if you lose your customers data are you sure you will have customers paying you to keep you in business while you figure out liability?

Re: "DigitalOcean Killed Our Company"

#470

Earlier quoted context omitted.

Yeah there might be some unpleasant internal conversations following that event

An unpleaseant conversation with his pillow. It's a two people company and he is the only technical person.

I'm talking about DO, not the affected company
Post reply on HN