3 ms·
Hmmm. I remember a while back when 37s had a piece of hardware die, they posted on their blog slating rackspace for not dealing with it quickly enough. A while
by dabeeeenster 18y ago
Hmmm. I remember a while back when 37s had a piece of hardware die, they posted on their blog slating rackspace for not dealing with it quickly enough. A while later they admitted they did not have a hot standby for the hardware that failed (I seem to remember it was a load balancer, so kind of important).
So basically I call bullshit on this. How about when you have a failure you don't blame a supplier who was not in the wrong? I'll try and find the blog post.
- dabeeeenster 18y agoYep - here it is: http://www.37signals.com/svn/posts/800-what-happened-this-morning http://www.37signals.com/svn/posts/800-what-happened-this-mo... "Naturally, we’re going to have a long, serious talk with our service provider (Rackspace). They’re supposed to be the best in the business, but in this instance they failed us," Then further down in the comments, DHH admits that their LB blew and they didn't have a hot standby: "It was no doubt a mistake not to have a second load balancer sitting ready"
- jayair 18y agohttp://www.37signals.com/svn/posts/698-downtime-notice http://www.37signals.com/svn/posts/698-downtime-notice From first comment on the post.
- jasonfried 18y agoWe shouldn't have blamed Rackspace. Even if it was their fault, it's our responsibility. Our customers pay us, not Rackspace. We learned from that and haven't blamed anyone but ourselves from that point on.
- dabeeeenster 18y agoIsn't it a litte high minded to blog about ways to communicate downtime when the last time you experienced some you blamed your suppliers who were actually blameless?
- eru 18y agoOne hopes people learned from their mistakes.