raiyu

60 ms·

601.
by raiyu 13y ago
Hi, Thanks for inquiring, but this hackernews title is very misleading. We take customer satisfaction very seriously at DigitalOcean. It wasn't one complaint, but 76, and it wasn't immediate, but 4 days with no responses that led
602.
DigitalOcean droplet console rewritten in Go(digitalocean.com)
80 points by raiyu 13y ago|28 comments
603.
by raiyu 13y ago
Agreed, this highlights a larger issue that we've been dealing with as we've grown to over 100,000 customers and the platform has evolved. When you have a singular product with a very narrow focus, say Instagram, it allows you to
604.
by raiyu 13y ago
We love to hear feedback from customers because it allows us to refine the product. From our internal metrics we know that providing an automatic snapshot recovery function is essential given the number of times its been implemented but we
605.
by raiyu 13y ago
Hi Folks, Just wanted to clarify the issue for anyone who didn't have the time to read the full gist. When we first started DigitalOcean we occasionally received tickets from customers about recovering a droplet that they had destroyed
606.
by raiyu 13y ago
Thanks for the feedback, one thing to remember is that the other companies mentioned in this thread have had quite a few years to put their products and service together. We spent most of last year dealing with the challenges of scale as we
607.
by raiyu 13y ago
If an IP continuously receives abuse complaints it is blacklisted by various services which can then lead to mail undeliverability issues or other problems which is why we are very pro-active on any abuse complaints that we receive and forw
608.
by raiyu 13y ago
We forward any abuse complaints that we receive to the owner of the account and ask that they handle them. We try not to interpret the law as that is not our specialty of course, we are simply saying that we would like that customers use th
609.
by raiyu 13y ago
Thanks for the great question. We are actually profitable on every virtual server that we sell. The reason we raised our seed round is that our growth began to outstrip our ability to acquire hardware and grow the business at the rate at wh
610.
by raiyu 13y ago
We try to provide the best cloud experience possible and part of that is following up on abuse complaints, otherwise we end up with blacklisted IPs and other issues that impact customer service. There are occasional weird situations like th
611.
by raiyu 13y ago
Completely agree with you, we definitely broke a few promises. We ran into this problem because we were used to our development cycle that we had in 2012, but in 2013 our growth really took off and we spent most of our time working on scali
612.
by raiyu 13y ago
There are two droplet limits, one is the number of droplets that you can spin up which you can see in your settings page: https://cloud.digitalocean.com/settings The second is if a customer signs up using Paypal we restric
613.
by raiyu 13y ago
You hit the nail on the head. We provided, and more specifically, I, directly did, estimates on when we launch certain features. Unfortunately those deadlines have come and gone. That was because those estimates were rooted in timeframes ar
614.
by raiyu 13y ago
We are seeing some issues with the network transit providers that we selected in Singapore where some of the traffic is being routed optimally. Bryan has been working hard on determining the best mix of network transit providers and peering
615.
by raiyu 13y ago
We can confirm that there are large issues on Level3's network we've had to pull them from the routing mix until they get everything resolved and stabilized. Thanks, Moisey cofounder DigitalOcean
616.
by raiyu 13y ago
Certainly, if you would like to draft up a quick letter absolving us from our privacy policy in regards to your account, scan it, and email it to contact @ do then we can provide the full details here.
617.
by raiyu 13y ago
Our privacy policy prevents us from disclosing any account or personal information so we can not speak to this customers situation publicly. If the customer would authorize this disclosure then we can discuss it publicly. Otherwise, as much
618.
Marketing isn't Advertising ... and it's not Evil(medium.com)
1 points by raiyu 13y ago|0 comments
619.
by raiyu 13y ago
When it comes to pure throughput there's unfortunately no way around physical proximity, but glad to hear the rest of your projects are on DO =]
620.
by raiyu 13y ago
Glad we got you to stick around! =]
621.
by raiyu 13y ago
Awesome, glad to hear that the experience turned around for you. We do have a ton of articles in our community section to help you get started as others have mentioned: https://www.digitalocean.com/community
622.
by raiyu 13y ago
As we were scaling up our network we ran into a few issues and had to work with our vendors to resolve them. Quoted metrics for support for ARP and MAC addresses on devices didn't match what we were seeing in production but we were abl
623.
DigitalOcean Wants To Challenge Amazon, Linode With Focus On Simplicity(techcrunch.com)
77 points by raiyu 13y ago|37 comments
624.
by raiyu 13y ago
There were three images that didn't like to regenerate host keys on their own when they were missing on the initial boot and we've update them today so it should all be cleared up now. Thanks!
625.
by raiyu 13y ago
Depending on the size of your existing DB and the workload getting a larger sized VM - 16+GB you should see significant performance improvement. Because it's hourly you can spin up and test and if it doesn't suit your needs will b
626.
by raiyu 13y ago
Have you integrated something like Puppet or Chef into your workflow to ease the pain of spinning up specific servers such as app, db, workers, etc.?
627.
by raiyu 13y ago
This was resolved, thanks for highlighting it, need to get this uservoice entry updated. Also we launched two factor auth recently. We take security very seriously. Thanks
628.
by raiyu 13y ago
You hit the nail on the head =] The growth has been fantastic and we are super excited. Unfortunately managing it requires as much work as engineering new features. The good news is we've been hiring and growing the team and we're
629.
by raiyu 14y ago
There was write-up from another customer who migrated from Heroku to DigitalOcean http://matteodepalo.github.io/blog/2013/03/07/how-i-migrated...
630.
DigitalOcean's New Control Panel and Transparent Design Process(digitalocean.com)
4 points by raiyu 14y ago|0 comments

More ›