4 ms·

I am DO customer, yesterday when I heard this story it felt scary step by DO with no regard for customers as original tweet said, "Nothing but radio silence fro

by mohsinr 10y ago

I am DO customer, yesterday when I heard this story it felt scary step by DO with no regard for customers as original tweet said, "Nothing but radio silence from @digitalocean while 38k sites remain down. Demoralizing." So It was not Radio Silence but 5 full days notice in advance with multiple notices. Thank you for updating us about the other side of the story.

djsumdog 10y ago
Has Suge responded to this claim by Digital Ocean? I wonder if these e-mails just got flushed into an endless e-mail bucket. That's the issue when you build a service hosted on a service (DO, AWS, Rackspace). You could have thousands of customers, but if you miss one complaint about one customer, the whole thing goes boom. It's more of an argument for content creators hosting on the platform controlled by the data centre owners. For Surge, and other large hosting platforms, it's an argument for them hosting their own dedicated servers in a data centre (which of course, raises the barrier to entry and costs for these types of solutions).
- sintaxi 10y ago
  we provide more specifics on timeline here https://news.ycombinator.com/item?id=12010521 https://news.ycombinator.com/item?id=12010521
- Kephael 10y ago
  When dedicated server providers don't react to complaints, complaints are instead sent to their upstream transit providers. Dutch based hosting provider Ecatel is an example that quickly comes to mind where their upstream providers simply stopped peering with them due to content issues. Hosting providers typically do not like the overhead that comes with handling DMCA and similar requests, servers that are very high risk should ideally operate with their own ASN and peering arrangements. Most hosting providers I have dealt with expect abuse resolution within 24 hours, five days is a very long time for abuse issues to be handled.
sintaxi 10y ago
We responded within 22 minutes of the original complaint and have been in frequent contact with Digital Ocean over the course of the 5 days including a phone call only hours before where they asked us to either remove the content or fill out a counter claim. They redacted the counterclaim request and shut us down 39minutes later followed by 1 hour of radio silence. 5 days had elapsed from the time the original takedown request came in until our network was disabled but there was plenty of correspondence in between and when we had last spoke to Digital Ocean it was still an open issue. We provide more specifics on timeline here https://news.ycombinator.com/item?id=12010521 https://news.ycombinator.com/item?id=12010521

by mohsinr 10y ago

djsumdog 10y ago

Has Suge responded to this claim by Digital Ocean? I wonder if these e-mails just got flushed into an endless e-mail bucket. That's the issue when you build a service hosted on a service (DO, AWS, Rackspace). You could have thousands of customers, but if you miss one complaint about one customer, the whole thing goes boom. It's more of an argument for content creators hosting on the platform controlled by the data centre owners. For Surge, and other large hosting platforms, it's an argument for them hosting their own dedicated servers in a data centre (which of course, raises the barrier to entry and costs for these types of solutions).

sintaxi 10y ago
we provide more specifics on timeline here https://news.ycombinator.com/item?id=12010521 https://news.ycombinator.com/item?id=12010521
Kephael 10y ago
When dedicated server providers don't react to complaints, complaints are instead sent to their upstream transit providers. Dutch based hosting provider Ecatel is an example that quickly comes to mind where their upstream providers simply stopped peering with them due to content issues. Hosting providers typically do not like the overhead that comes with handling DMCA and similar requests, servers that are very high risk should ideally operate with their own ASN and peering arrangements. Most hosting providers I have dealt with expect abuse resolution within 24 hours, five days is a very long time for abuse issues to be handled.

sintaxi 10y ago

We responded within 22 minutes of the original complaint and have been in frequent contact with Digital Ocean over the course of the 5 days including a phone call only hours before where they asked us to either remove the content or fill out a counter claim. They redacted the counterclaim request and shut us down 39minutes later followed by 1 hour of radio silence. 5 days had elapsed from the time the original takedown request came in until our network was disabled but there was plenty of correspondence in between and when we had last spoke to Digital Ocean it was still an open issue. We provide more specifics on timeline here https://news.ycombinator.com/item?id=12010521 https://news.ycombinator.com/item?id=12010521