Nonetheless, just because you haven't been affected, doesn't mean other have not been, or still aren't.
They dealt with the resulting capacity imbalances by randomly remapping AZs for new accounts, but AFAIK they're never publicly acknowledged this so most people aren't aware. Instead they should have just started charging more for resources requested explicitly in those zones until people fixed their poorly written software.
This statement is false. AZs map directly to physical facilities. If you and I both ask for instances in us-east-1b they will have lower ping times than if one of us has an instance in us-east-1c.
Disclaimer: I used to work for AWS.
"Q: How can I make sure that I am in the same Availability Zone as another developer? We do not currently support the ability to coordinate launches into the same Availability Zone across AWS developer accounts."
http://aws.amazon.com/ec2/faqs/#How_can_I_make_sure_that_I_a...
If AZs map directly to physical facilities, how does that FAQ make sense?
We're straining to read the tea-leaves here, rather than AWS just telling us what they've built.