4 ms·
Looks like troubles in only one availability zone.
by thezilch 16y ago
Looks like troubles in only one availability zone.
- mechanical_fish 16y agoThat seems to be incorrect. We have problem children in us-east-1b, -1c, and -1d.
- justinsb 16y agoAWS randomize the zones per account, so "your" -1b is not necessarily the same as "my" -1b. I'm only seeing problems in my -1c. Are you seeing 3 zones failing all under the same account? If multiple AZs are down, AWS are going to have some serious explaining to do...
- jedberg 16y agoWe (reddit) are seeing failures in all zones.
- redthrowaway 16y agoIf memory serves, Amazon's reporting of what zones are experiencing problems has been...optimistic...in the past.
- nlo 16y ago"AWS randomize the zones per account" Interesting. This is news to me. I found some more info here (Google cache since alestic.com is presently unreachable): http://webcache.googleusercontent.com/search?q=cache:0jxzyFj0J7wJ:alestic.com/2009/07/ec2-availability-zones&hl=en&gl=us&strip=1 http://webcache.googleusercontent.com/search?q=cache:0jxzyFj...
- dangrossman 16y agoAmazon RDS's most expensive feature is automatic, instant Multi-AZ failover to protect against this kind of situation. It's not working quite like that, which the AWS status page acknowledges. This is a major failure.
- justinsb 16y agoAWS have now confirmed that this affects multiple availability zones. From the status page: "..impacting EBS volumes in multiple availability zones in the US-EAST-1 region"
- justincormack 16y agoThats not good. The whole point of multiple AVs is for them to not fail at the same time. Suggests some dependencies that should not be there perhaps, or at least some correlation of something, like software upgrades. Looking for a good explanation of this; one AV going down is not a problem and should not impact anyone who is load balancing.