Live data from Hacker News

Stop Using Digital Ocean Now: The Aftermath

serdardogruyol.com

11–20 of 102 posts

Re: Stop Using Digital Ocean Now: The Aftermath

#11
> DigitalOcean requested me to send a paper which authorizes them to disclose the information in public. It was midnight here in Turkey and i was asleep.

> And now after nearly 10 hours or so i still haven’t heart from DO

What about timezone differences? You were asleep, they could be, too.

Re: Stop Using Digital Ocean Now: The Aftermath

#12

OP, can you please confirm whether or not you made this post quoting a reply from Digital Ocean in the previous thread, as [1] claims you did? Now i've received an answer from DO. I seriously dont know how i did a DDos. Here it's. Greetings, Based upon the tcpdump results, I have again confirmed that your droplet was indeed performing a Denial of Service attack. With this information, we are unable to restore service…

The thing is that they wanted to stay private when i posted this so i immediately removed and now waiting for them. By the way i received that response after 2 hours of the topic opening. They weren't answering me at all before HN post

Re: Stop Using Digital Ocean Now: The Aftermath

#14
Wait... did I miss something or did you send snailmail and expect a response within 10 hours?

Also I am nowhere close to being a lawyer but I'm pretty sure if they disclosed your private information on here without your written permission you could sue them probably for more than either of these 2 posts are worth against them.

Re: Stop Using Digital Ocean Now: The Aftermath

#16

> DigitalOcean requested me to send a paper which authorizes them to disclose the information in public. It was midnight here in Turkey and i was asleep. > And now after nearly 10 hours or so i still haven’t heart from DO What about timezone differences? You were asleep, they could be, too.

That's a possibility. But at this time yesterday they were really really active.

Re: Stop Using Digital Ocean Now: The Aftermath

#17
Some months ago a tried to open an account with DO, but my account was blocked by DO before creating a droplet because my dad, who has the same name as I do, had already used the service. DO wanted me to verify my identity, address, etc.

I can't stand such friction, so I stayed with AWS, who have never had an issue with having a customer with very similar or equal name to another. Clearly, there is something wrong in DO's identity/fraud detection process, and even more wrong is the fact that they are locking user's production accounts without any warning at all.

Re: Stop Using Digital Ocean Now: The Aftermath

#18
post #9

Funny that DO's public response was to demand permission to discuss the case publicly , when apparently they had not discussed it with the customer concerned!

I think that is the appropriate public response. Not discussing it with the customer is obviously an inappropriate private response.

Re: Stop Using Digital Ocean Now: The Aftermath

#19
post #9

Funny that DO's public response was to demand permission to discuss the case publicly , when apparently they had not discussed it with the customer concerned!

I think they have. The customer in question simply didn't put it in his blog post. I feel as though the customer may be presenting the facts in such a way to make DO look bad. I don't see anywhere in his blog post about his DDOS attack. His server was shutdown because it was running a DDOS attack. My guess is that his server got owned...

People get disproportionally mad when their server gets shutdown, for a service that charges $5 a month for a VPS. Most people probably wouldn't get angry at Netflix if they cancelled their $7 a month account, but shutting down a VPS feels like a personal attack.

If you pay $5 a month for a service, don't expect a customer representative to hold your hand and debug your server troubles.

Re: Stop Using Digital Ocean Now: The Aftermath

#20
post #17

Some months ago a tried to open an account with DO, but my account was blocked by DO before creating a droplet because my dad, who has the same name as I do, had already used the service. DO wanted me to verify my identity, address, etc. I can't stand such friction, so I stayed with AWS, who have never had an issue with having a customer with very similar or equal name to another. Clearly, there is something wrong in…

I ran into the same problem just last week when I tried to make an account to try it out.

I added a credit card to my account without a promotion code, but later on found out about the new promotion they are doing (free $10). I realized that you cannot enter a promo code if you didn't do it the first time you add payment to an account, even if the account is otherwise still new (I didn't do anything with it after adding the payment card).

So I de-activated my account, and made another one, entered the same payment info but with the promo code this time. Then my account was instantly locked for using the same credit card, and I received an email shortly after citing section 2.6 of their ToS which prohibited users from using the same payment card on multiple accounts (even though my previous account was de-activated).

Their trial/promo code system really needs to be revamped as I spent way more time figuring out how to put the code in than actually trying out their product. Also their fraud detection system is perhaps too sensitive? I mean I should be able to re-use payment cards if my old account was de-activated...

Post reply on HN