4 ms·
As happy as I am to see this post itself, the mistakes made here are pretty appalling. Killing customer accounts by automated action without any human check ju
by Aeolun 7y ago
As happy as I am to see this post itself, the mistakes made here are pretty appalling.
Killing customer accounts by automated action without any human check just seems like a recipe for disaster. Even if you can respond faster to crypto issues, the effects of a false positive are just unacceptable.
Though apparently the human checks at Digital Ocean don’t work either.
- laughinghan 7y agoAccording to the post, that's not what happened? The customer account wasn't terminated by the automated system, but rather by the second Abuse Ops agent. Upon a second review by a different Abuse Operations agent [...] the agent fully denied access back into the account. This action triggered the final “access denied” communication to the customer.
- mintplant 7y agoThat was after the automated process locked access to the account and powered off all associated machines.
- computerex 7y agoRead the post? > The initial account lock and resource power down resulted from an automated service that monitors for cryptocurrency mining activity (Droplet CPU loads and Droplet create behaviors).
- wvenable 7y agoYou're looking at the one false positive instead the potentially thousands of true positives. Those true positives are people using free DO credits to cryptomine on DO. And probably 99.99% of the time the system works as intended. Dealing with bad actors and abusers is not pleasant or easy. This sort of 0.01% case is exactly what developers and sysadmins deal with on a regular basis -- some crazy scenario that lead to a bug you've never experienced before. The correct and only response is to fix the bug (whether it be software or process), offer whatever compensation to the injured parties, and move on.
- Aeolun 7y agoHow much do you think this one instance will hurt DO’s bottom line? I’m prepared to say the lost income potential is massive. Who would ever use them for production if they can arbitrarily decide that your servers need to be powered down?