It's weird, I see actually most of my issues coming from instances located in `eu-west-1a`, whereas `eu-west-1b` and `eu-west-1c` look fine.
That doesn't apply here though. Instances that are already up are experiencing DNS resolution issues because the Amazon-provided DNS service (which is distinct from Route53) is failing
What you see as zone A is not what I see as zone A (maybe). When you sign up for an account, AWS assigns your zone A to one of the 3 available zones:
zone X (real) : your A (virtual) : my C (virtual)
zone Y (real) : your B (virtual) : my B (virtual)
zone Z (real) : your C (virtual) : my A (virtual)
Edit: one of the few articles (other than HN comments) that explains it https://alestic.com/2009/07/ec2-availability-zones/
All I can say is "WHAAAAAAT?!"
You've made me question my reality. Take an upvote for that alone.
I myself was in the middle of a release when all this happened. "I'll just release this thing" I said, "will only take 20 minutes" I said....
An Availability Zone is represented by a region code followed by a letter identifier;
for example, us-east-1a. To ensure that resources are distributed across the Availability
Zones for a region, we independently map Availability Zones to identifiers for each
account. For example, your Availability Zone us-east-1a might not be the same location
as us-east-1a for another account. There's no way for you to coordinate Availability
Zones between accounts.
Complicated networks are complicated, I suppose