"Degraded performance," is a fairly off-handed way of putting what they're experiencing. First RDS connectivity went down the tube, and then EBS followed, finally the EC2 console is failing to operate properly (for me, in US-EAST region at least).

Of course, as soon as I read the report that the issue was confined to one AZ, I looked to move my server over to another AZ. Oh yes, two were full and refused new instances, and then surprisingly, new requests for the other AZs never were received or operated on - and now the console is failing. It's a bit more than just "slow EBS" if that's what you were thinking.

- edit: said ec2 twice in the second sentence, corrected to say ebs.

No. Amazon just understates the issues. Reddit, Heroku etc. all have problems.

Even if they do understate the issue, It's limited to US-EAST 1, and is an EBS issue. Saying that EC2 is "down" because of this is totally off the mark - I've got dozens of EBS volmes in EAST 1 that are unaffected, plus all of the other zones that are operating normally...

EC2 instances are affected by the EBS issues. But you're right, it's not correct that EC2 is "down".

Not all instances are EBS backed.

EC2 is not down. My EC2 sites are all functioning.

All my instances across 3 zones are functioning normally.

From what I'm seeing, if your root disk is on EBS and your SSH keys are there, you cannot SSH into those hosts right now.

Also, the availability zones are disparate in terms of what they can support. A great number of my instances are in 1d because of unavailability in others.

Note that the region-1[a b c d & such] designations are randomized per account; my us-east-1d won't (necessarily) be the same as yours or anyone else's.

Ah, I didn't know that. Thanks!

If you're relying on individual servers to have drives which never fail you're doing reliability wrong.