Every time (two out of two), by the time I click on "X is down" link, the service/website is working again. Surely there is a better platform for alerting about outages than ycombinator?
Individual availability zones can be identified using the API.<p><pre><code> ec2-describe-reserved-instances-offerings --region
</code></pre>
will tell you what the zone's identifier is.<p>After you list the permanent identifiers, you can match them up to find out if your <i>us-east-1a</i> matches my <i>-1d</i>.<p>This Alestic article shows how to label them all.<p>[0] "Matching EC2 Availability Zones Across AWS Accounts" <a href="http://alestic.com/2009/07/ec2-availability-zones" rel="nofollow">http://alestic.com/2009/07/ec2-availability-zones</a>
EC2 comes with a free Chaos Monkey service. It's called EC2.<p>I know, they're trying to make it reliable and they've got a bunch of very hard problems to solve. That doesn't change the fact that sometimes some of my servers just permanently stop responding to pings until you stop-start them, or get crazy-slow I/O, or get hit by these once-in-a-while-and-always-at-night outages.<p>It's great when you suddenly need a hundred more servers, though.
I got notified by Pingdom that my domain was down before AWS had any info on that status page of theirs. IMHO, they should improve on the latency of their alerts.
I feel like you can't really say you're in the green when you still have customers unable to use your service. My instance is still stuck in failover.<p>"9:39 AM PDT Networking connectivity has been restored to most of the affected RDS Database Instances in the single Availability Zone in the US-EAST-1 region. New instance launches are completing normally. We are continuing to work on restoring connectivity to the remaining affected RDS Database Instances."
I'm running in us-east-1 and my EC2 instances and EBS volumes are still responding ok for the moment...<p>Fingers crossed (just deployed to AWS less than 2 weeks ago).
9:32 AM PDT Connectivity has been restored to the affected subset of EC2 instances and EBS volumes in the single Availability Zone in the US-EAST-1 region. New instance launches are completing normally. Some of the affected EBS volumes are still re-mirroring causing increased IO latency for those volumes.
Interesting enough not only the EBS is down, but ELB can not register instances even if there are not EBS based and completely operational.<p>I have some live instances running without EBS disks that I can not place behind the ELB as it is not working.
Issue #3298392 for EC2 this month. This is ridiculous, so many websites rely on EC2 and it's proving to be extremely unreliable. Cloud computing is definitely not the answer to everything it would seem.
Cpu0 : 0.3%us, 0.0%sy, 0.0%ni, 0.0%id, 99.7%wa, 0.0%hi, 0.0%si, 0.0%st <-- EBS subsystem is completely unreachable. I/O wait times are tanked across the board for me (I'm in US-EAST-1).