http://azure.microsoft.com/blog/2014/12/17/final-root-cause-analysis-and-improvement-areas-nov-18-azure-storage-service-interruption/
The comments sound familiar. 
I had as much to say as anyone, I think, about how to assess the Logos outage. I tried to be even-handed (don't know if I succeeded), but I was somewhat critical.
What's interesting is that MS has taken all the steps folks on these forums suggested that Logos ought to have taken and/or ought to consider taking. None of that is a guarantee that human error or software bugs won't creep in and cause problems like these anyway.
Something for all of us to keep in mind.
Donnie