If you read the update and root cause analysis, this wasn't a redundancy issue. It was caused by a software bug, one that couldn't be fixed by more hardware. Developers had to build a fix, test it, and deploy it. This resulted in substantial delays, as many of us should be able to understand.

However it also appears that MS wasn't as forthcoming initially, at least according to Gartner: http://blogs.gartner.com/kyle-hilgendorf/2012/03/09/azure-outage-customer-insights-a-week-later/

Apparently MS is offering credit for the day, which is something: http://www.zdnet.com/blog/microsoft/microsoft-to-provide-azure-users-with-33-percent-credit-for-february-outage/12154