Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Anybody else EC2 issues on us-east-1?

news.ycombinator.com

Post reply on HN
Print view View original

21–30 of 50 posts

Re: Ask HN: Anybody else EC2 issues on us-east-1?

#21

Post by cstejerean »

us-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 for everyone else that doesn't need the bleeding edge, why not just run your instances in us-west-2 or us-east-2 for example? I've run services in us-west-2 for years and I've never had to deal with fallout from an AWS outage.

Re: Ask HN: Anybody else EC2 issues on us-east-1?

#22

Post by koolba »

cstejerean wrote: post #21

us-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…

Because we want to be colo with everybody else that's on us-east-1. It makes for lower latency, higher transfers, and when shit hits the fan none of your customers notice that your SaaS product is down because they can't access their entire site!

Re: Ask HN: Anybody else EC2 issues on us-east-1?

#23

Post by debaserab2 »

cstejerean wrote: post #21

us-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.

Re: Ask HN: Anybody else EC2 issues on us-east-1?

#24

Post by leesalminen »

amichal wrote: post #17

check https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-... when this happens... As of now it says for me "04:36 PM PDT We are investigating network connectivity issues for some instances in a single Availability Zone in the US-EAST-1 Region. 04:58 PM PDT We can confirm that some instances are unreachable and some EBS volumes are experiencing degraded performance in a single Availability Zone in the US-EAST…

Had a similar issue earlier today with Rackspace's version of EBS.

Re: Ask HN: Anybody else EC2 issues on us-east-1?

#25

Post by [deleted] »

leesalminen wrote: post #24
amichal wrote: post #17

check https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-... when this happens... As of now it says for me "04:36 PM PDT We are investigating network connectivity issues for some instances in a single Availability Zone in the US-EAST-1 Region. 04:58 PM PDT We can confirm that some instances are unreachable and some EBS volumes are experiencing degraded performance in a single Availability Zone in the US-EAST…

Had a similar issue earlier today with Rackspace's version of EBS.

[deleted]

Re: Ask HN: Anybody else EC2 issues on us-east-1?

#28

Post by misframer »

misframer wrote: post #19
vacri wrote: post #14

Earlier quoted context omitted.

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...

Re: Ask HN: Anybody else EC2 issues on us-east-1?

#29

Post by encoderer »

Cronitor saw our customers first impacted at 4:29, largely recovered by 5:04.

Another interesting thing is that AZ identifiers are randomized from customer-to-customer so when people report their failures, like here in this thread, it can sometimes seem like a problem is region-wide when in fact it's isolated to an AZ.

Post reply on HN