An update on last week's customer shutdown incident

Re:An update on last week's customer shutdown incident by andrewstuart on Tuesday June 04, 2019 @09:13PM (#20100691)

Nothing in the statement from Digital Ocean indicates that they won't kill your account or shutdown your systems - that's not the sort of cloud host any company can afford to use.

Cloud providers that kill accounts - or SAY they kill accounts, must be dropped and not used.

The worst thing that should be possible is for your account to be suspended.

AWS, if there is a billing issue, prevents you making changes to your infrastructure via the console until the billing issue is sorted out - this is good and reasonable.

""Peer review of account terminations. For any account appealing a lock, two agents will be required to review the submission prior to issuing a final deny.""

- I can imagine how this plays out:

(service agent 1 turns to next service agent along) 'This looks like a bad account - I think I should shut it down, what do you think buddy?'

(service agent 2) - 'Yep I trust you, shut it down.'

[ Parent | on HN ]

Re:An update on last week's customer shutdown incident by asdfasgasdgasdg on Tuesday June 04, 2019 @10:06PM (#20100934)

> Nothing in the statement from Digital Ocean indicates that they won't kill your account or shutdown your systems - that's not the sort of cloud host any company can afford to use.

There is no cloud that will issue such a promise. If your criterion is that a cloud has to promise that you won't get shut down, you just can't use cloud hosting providers.

[ Parent | on HN ]

Re:An update on last week's customer shutdown incident by nothal on Tuesday June 04, 2019 @09:18PM (#20100714)

The article discusses violating TOS, not a billing issue. I don't think it's unreasonable to disable an account in that circumstance but I agree that deleting images/resources without allowing customers to defend themselves and backup the systems would be unfair.

[ Parent | on HN ]

Re:An update on last week's customer shutdown incident by ben0x539 on Wednesday June 05, 2019 @04:50AM (#20102556)

> The article discusses violating TOS, not a billing issue.

That's not the impression I got. It sounds like the issue was that a account with misinterpreted payment history was showing bitcoin-mining-like usage patterns. Mining is not against the terms of use, they were just erroneously convinced themselves that the customer was not going to pay for it.

[ Parent | on HN ]

Re:An update on last week's customer shutdown incident by ben0x539 on Wednesday June 05, 2019 @01:07PM (#20106585)

I'd like to apologize for the typos in my previous comment that I neglected to notice before the edit window expired.

[ Parent | on HN ]

Re:An update on last week's customer shutdown incident by bcooks on Wednesday June 05, 2019 @10:49AM (#20104952)

Correct.

[ Parent | on HN ]