Live data from Hacker News

Digital Ocean NYC2 Droplets Down

news.ycombinator.com

11–20 of 74 posts

Re: Digital Ocean NYC2 Droplets Down

#11

I just created a droplet today, and was trying for the life of me to figure out what I would have done so early on in setting it up to cause it to become unresponsive. Glad to see it's not just me. It's not really a great sign though, as I was hoping to use this fairly frequently. Is this a common occurrence, or do I just have bad luck? If so, I'll definitely have to find another solution.

I'm not too qualified to comment on the hosting market, but I do want to vouch for DigitalOcean as I've never had uptime issues with them until now. They also have always had timely and helpful support and their pricing is obviously competitive.

That being said, near 100% uptime is really desired in this space and I've been scratching my head for the past hour or so wondering why I couldn't connect to my mongo process running on my droplet...maybe I should have tested DO sooner, but the fact that only mongo seemed to be failing (and not postgres for example) made me think I had client and not server issues.

Re: Digital Ocean NYC2 Droplets Down

#16

Having previously left Linode for Digital Ocean due to lower pricing and SSDs, I can safely say Linode both dropped their prices and matched the DO plans with SSDs included. If you want to jump ship, that's the route I'd go for a comparable. I still love DO, but downtime is a no-no when it comes to VPSes.

In the process of switching over now.

Re: Digital Ocean NYC2 Droplets Down

#19

Linode's new offering probably the better choice these days. I get the feeling that DO is just overwhelmed with problems related to their hyper growth - 10% per month on a huge base. http://trends.netcraft.com/www.digitalocean.com

They've done so well to this point keeping up with the growth curve. Hope they don't become crippled by success.

Re: Digital Ocean NYC2 Droplets Down

#20
post #11

I just created a droplet today, and was trying for the life of me to figure out what I would have done so early on in setting it up to cause it to become unresponsive. Glad to see it's not just me. It's not really a great sign though, as I was hoping to use this fairly frequently. Is this a common occurrence, or do I just have bad luck? If so, I'll definitely have to find another solution.

I'm not too qualified to comment on the hosting market, but I do want to vouch for DigitalOcean as I've never had uptime issues with them until now. They also have always had timely and helpful support and their pricing is obviously competitive. That being said, near 100% uptime is really desired in this space and I've been scratching my head for the past hour or so wondering why I couldn't connect to my mongo proces…

I've been using Linode for many years, and DO for some time now (a year? not sure, since I can't even login to their control panel right now and check). I've seen issues on both providers, and dealt with support of both not too infrequently.

I'd still say Linode is miles ahead in terms of expertise and responsiveness. Most of my servers are on Linode for this reason, and only a few on DO.

As a customer I enjoy this competition and would like to keep both players compete - because I'm benefiting from it. So I'm likely to stick to both. But I would still recommend Linode more easily than I would DO.

Post reply on HN