By that argument, the customers of Heroku who weren't prepared to handle Heroku's failure were at fault. They should have had alternate rails hosting lined up.
Re:Heroku's AWS outage post-mortem
by jasonlotito on Wednesday April 27, 2011 @12:02PM
(#2489930)
Amazon is at fault to Heroku. However, Heroku isn't talking to Amazon here, they are talking to their customers. Heroku is at fault to those customers. In turn, those customers are at fault to their users. Heroku can't pass the buck to Amazon, and those customers can't pass the buck to Heroku for their downtime (They can, but it's still their responsibility).
Re:Heroku's AWS outage post-mortem
by RyanKearney on Wednesday April 27, 2011 @02:07AM
(#2488567)
Well it depends on what Heroku's SLA was, if any. If Heroku stated 100% uptime grantee, then Heroku would be to blame for not living up to their 100% uptime. If Heroku said hey listen, we can't guarantee any amount of uptime so be prepared and someone were to host some "mission critical" information on Heroku then yeah it would be the customers fault.
In this example, think of Amazon as Comcast and Acme Corp as Heroku. Heroku wasn't prepared to handle this type of failure, so they're at fault.