Earlier quoted context omitted.
I'm having problems in us-east-1c
The AZ names are different for each account.
Thanks! did not know that.
Ask HN: Anybody else EC2 issues on us-east-1?
31–40 of 50 posts
Re: Ask HN: Anybody else EC2 issues on us-east-1?
#32us-east-1 is the region that has most issues. Every time you hear about an AWS outage it's typically just us-east-1, and it brings down half the internet. It's really puzzling why everyone keeps hosting their projects in us-east-1. The advantage of that region is that it tends to get new instance types and services first. And if you need to be on the bleeding edge, then you have to agree to deal with some risks. But…
Only two regions have good availability for AWS services.
For example, email (SES). Only Virgina and Oregon. And Oregon goes down too.
If all you needed was VPS, you'd probably find better offerings elsewhere.
Re: Ask HN: Anybody else EC2 issues on us-east-1?
#33us-east-1 is the region that has most issues. Every time you hear about an AWS outage it's typically just us-east-1, and it brings down half the internet. It's really puzzling why everyone keeps hosting their projects in us-east-1. The advantage of that region is that it tends to get new instance types and services first. And if you need to be on the bleeding edge, then you have to agree to deal with some risks. But…
I think you answered your own question. In the case of AWS, sometimes being "bleeding edge" means you're allowing amazon to scaffold infrastructure with a new service that you'd otherwise have to deal with yourself. For a small company, an AWS service being bleeding edge is still a lot more resilient than doing it yourself.
[deleted]
Re: Ask HN: Anybody else EC2 issues on us-east-1?
#34us-east-1 is the region that has most issues. Every time you hear about an AWS outage it's typically just us-east-1, and it brings down half the internet. It's really puzzling why everyone keeps hosting their projects in us-east-1. The advantage of that region is that it tends to get new instance types and services first. And if you need to be on the bleeding edge, then you have to agree to deal with some risks. But…
us-east-1 pricing (for EC2, S3, etc.) is usually lower than other regions
Re: Ask HN: Anybody else EC2 issues on us-east-1?
#35Amazon are starting to push 'new' features and services to Ohio pretty quickly if you still need a non-Virginia AWS East Coast location.
Re: Ask HN: Anybody else EC2 issues on us-east-1?
#36This is exactly why you should design your services to run in multiple availability zones to mitigate issues like this. We run our most critical services in at least 3 availability zones and we are moving the rest of our services soon as well. While these problems are unfortunate, it is part of relying on Amazon to manage resources.
Always plan for service degradation and look for ways to mitigate against issues like this.
Re: Ask HN: Anybody else EC2 issues on us-east-1?
#37Earlier quoted context omitted.
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.
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.
Re: Ask HN: Anybody else EC2 issues on us-east-1?
#38us-east-1 is the region that has most issues. Every time you hear about an AWS outage it's typically just us-east-1, and it brings down half the internet. It's really puzzling why everyone keeps hosting their projects in us-east-1. The advantage of that region is that it tends to get new instance types and services first. And if you need to be on the bleeding edge, then you have to agree to deal with some risks. But…
> It's really puzzling why everyone keeps hosting their projects in us-east-1.
I've been using Amazon for 4 years, and this is the first time I hear their us-east-1 is more "cutting edge" and less reliable than all the other zones. This isn't even listed on their page describing these zones: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-reg...
Re: Ask HN: Anybody else EC2 issues on us-east-1?
#39us-east-1 is the region that has most issues. Every time you hear about an AWS outage it's typically just us-east-1, and it brings down half the internet. It's really puzzling why everyone keeps hosting their projects in us-east-1. The advantage of that region is that it tends to get new instance types and services first. And if you need to be on the bleeding edge, then you have to agree to deal with some risks. But…
> It's really puzzling why everyone keeps hosting their projects in us-east-1. I've been using Amazon for 4 years, and this is the first time I hear their us-east-1 is more "cutting edge" and less reliable than all the other zones. This isn't even listed on their page describing these zones: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-reg...
It's pretty common knowledge that us-east-1 is the most unreliable region. Also the oldest which helps explain why.
Re: Ask HN: Anybody else EC2 issues on us-east-1?
#40us-east-1 is the region that has most issues. Every time you hear about an AWS outage it's typically just us-east-1, and it brings down half the internet. It's really puzzling why everyone keeps hosting their projects in us-east-1. The advantage of that region is that it tends to get new instance types and services first. And if you need to be on the bleeding edge, then you have to agree to deal with some risks. But…
> It's really puzzling why everyone keeps hosting their projects in us-east-1. I've been using Amazon for 4 years, and this is the first time I hear their us-east-1 is more "cutting edge" and less reliable than all the other zones. This isn't even listed on their page describing these zones: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-reg...
Of course it's not listed. They're not going to say "this is our first region and it runs on some pretty old hardware and hacked together configurations so we recommend you don't use it."