Hacker News Reader

Comment by swvjeff | Hacker News Reader

us-east-1b seems to be affected for me.

4:36 PM PDT We are investigating network connectivity issues for some instances in a single Availability Zone in the US-EAST-1 Region.

View on HN

I'm having problems in us-east-1c

The AZ names are different for each account.

Wow, how did I not know this? Thanks for the info.

They randomise the AZ letters, because humans tend to shove things in 'a' before anywhere else - it's a psychological load-balancer.

If you want to figure out which of your AZs corresponds to another account's AZs, you can compare spot-prices, which are individual per AZ. Also, for some reason, my account doesn't have a 'b', just a-c-d-e. Weird.

They also introduced us-east-1f, and it's the same for everyone because it's new :).

Not sure why I was downvoted. This was mentioned in an issue of Last Week in AWS [0].

[0] https://snarkive.lastweekinaws.com/issue_14-_US-East-1_Drops...

Interesting that the idea is to distribute load across the zones (because people default to using A), but Google Cloud zones are uniform across all accounts and it seems to work for Google.

Interesting! Do you know anywhere I can read more about this?

Yep, it's in the documentation [0].

[0] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-reg...

Thanks! did not know that.

1d here

I heard that aws actually scrambled availability zones... so your 1a might be my 1c, etc.. Haven't confirmed it, but the comments seem to bear that out.

It's in the documentation [0].

[0] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-reg...

Reply on news.ycombinator.com