Digital Ocean NYC2 Droplets Down
And counting. Second time in about a week and during prime time hours. If it doesn't get up quickly or if happens again to NYC2 in the next few weeks may be time to reconsider DO for hosting production sites. I love them, and glitches happen, but twice in a row clients have a hard time swallowing.
73 comments
[ 4.2 ms ] story [ 142 ms ] threadhttp://netalyzr.icsi.berkeley.edu/cli.html
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.
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.
I still love DO, but downtime is a no-no when it comes to VPSes.
http://trends.netcraft.com/www.digitalocean.com
I've used DO in the past for quick spin-ups, and they're great for that. But for long running applications I'd stay away. Was actually considering DO for a new project, but this kind of tipped the scales the other way.
If you're looking to switch, I think Linode gives you the best bang and reliability for your buck. Have also used Rackspace for a previous startup. A bit more pricey, but also a great service if you're considering switching.
If that's not what you're talking about, I apologize, but I've been using Linode for years (often with very compute-intensive projects) and I haven't seen what you're talking about.
Hell, I've gotten DDoS'd for like 2 Gbps and they were like "Oh, ya, its fine."
So, can you explain more about what happened?
I agree with harpastum. I think you're confusing automatic email notifications based on your own settings with Linode support. I feel like you have to seriously abuse their infrastructure to get them to contact you.
Disclaimer: has been a happy Linode customer for over 4 years now.
I was not confusing automated emails with direct contact from Linode support. I fully understand and can appreciate the need to be a "nice neighbor" in a shared environment but what baffles me is:
1) Linode doesn't have the capability to actually enforce any sort of quota or limit. It's 2014, there's been numerous advancements in the area of virtualized servers in the past decade. cgroups is a very easy way that works across xen, kvm and lxc.
2) Linode doesn't publish these arbitrary limits nor give guidance on which node size comes with what acceptable usage levels.
It's their job to limit resources on your node, not your job to self-limit. Asking you to limit resources because it's "affecting other customers' performance" is not only outrageous, but also unfair with the other customers being impacted.
This reminds me of the late 90's [1], when web hosting meant sharing the same box with hundreds of other customers, and very limited tools to enforce limits. When you had a resource hog, the only option was really to get them to reduce usage, or move them to a separate box (which wasn't as easy as today).
[1] ps: I know this well; used to have a web hosting company at the time. We had to frequently move customers around, and in some cases to terminate their contracts - e.g., porn sites. But this was a good 10 years before Xen become commonplace.
Anything I have that uses that level of disk i/o I don't run in a VPS which would explain why I've never noticed before.
1) I don't know enough to talk about resource limiting that Linode might do. There might be a reason they don't want to or can't use it with their infrastructure.
2) I agree, they could publish some guidelines for resource usage, but this is hardly baffling. I'd guess most of the customers just don't hit this problem, so there's no need to list all of the limitations.
I can agree that DO isn't suited for production apps, but Linode isn't either. They're both VPS playgrounds.
I never had problems with DO that weren't resolved promptly.
Just a note, Linode is very US-centric anyway... (and that one London location doesn't make it international very much)
Glad to see the ProjectWonderful ads providing something, even if its small btw. :)
For context: I'm a happy Digital Ocean customer (as well as Rackspace and others). I like their services and consider them a great value for the money. I've also gotten multiple developer friends into using them. But I don't let them be a single point of failure for anything critical.
Things like saltstack (saltstack.org) make this mega-easy.
May I ask what your clients are paying?
Maybe the answer is to charge them more instead of giving them a low price (an assumption on my part of course which is why I ask what you are getting for this) and some implicit guarantee of uptime.
For example we had some customers some time ago who were pooled on a shared IP address for sending SMTP service. Occasionally they would experience problems with mail reputation on that shared IP. If they complained about that would simply explain that that was the drawback of a shared IP and that they could always upgrade to a service level where they got a unique IP and could establish their own reputation.
Now I'm tempted to drive to New York and punch them each in the face.
PEAK downtime.
EDIT: $160 refund. Maybe just a Charlie horse.
Yes it costs money but things like this are avoidable. Every single Datacenter on the planet has downtime and/or performance issues from time to time. Hell, one of the places I have a dedi at had its network performance drop by 50% for about 15 minutes while they did emergency maintenance.
Things like this are going to happen as long as you depend on one provider.