AWS needs to blantantly copy Heroku's status system, which is worlds better for people needing fast updates on their infrastructure.
You can at least mitigate it by keeping utilization of your instances below what would be needed to handle load of one zone failing. I suspect to save money, many people are pushing utilization as high as possible.
I can't speak to why Heroku was impacted as much as it was. It could be that they have single points of failure, or run at a utilization level that makes losing a single zone difficult.
Apart from Apple's legendary secrecy, Amazon's EC2 is a solid #2 in terms of impenetrability.
Linode, in comparison, has always been straight-forward, personal, and as honest as a company in that space can be.
What's perhaps odd is Amazon's customer service for their material goods is usually superb.
Is this not a 'service disruption' situation? At the bottom of the page, the yellow icon is associated with 'performance issues'.
If there's one thing that's shocked me about AWS, it's the total failure to acknowledge the severity of service disruptions. Like the above case, or the fact that a 3-hour loss of connectivity is displayed on the service history as a green tick with a small 'i' box: http://oi46.tinypic.com/x5qtch.jpg