Live data from Hacker News

AWS us-east-2 outage

news.ycombinator.com

61–70 of 254 posts

Re: AWS us-east-2 outage

#61

Wonder if this is why Zoom is down. Wasn't able to connect just now. The connection proxy/sites were giving 504s.

IIRC Zoom signed up with Oracle Cloud when COVID hit and they needed to scale like crazy.

https://www.oracle.com/customers/zoom/

I'm not sure if Zoom has any Critical infra in AWS though.

Re: AWS us-east-2 outage

#62
post #21

I'm running Terraform and it appears to be stuck now. What do I do??

Depends what it’s stuck doing, but you might ctrl-c it and later manually unlock the state file (by carefully coordinating with colleagues and deleting the dynamo DB lock object if you’re using the s3 backend) when the outage is over.

Thanks, this comment made it very clear to me that I never want to touch a terraform system.

Re: AWS us-east-2 outage

#63

  $ dig news.ycombinator.com
  ;; ANSWER SECTION:
  news.ycombinator.com.   1       IN      A       50.112.136.166

  $ dig -x 50.112.136.166
  ;; ANSWER SECTION:
  166.136.112.50.in-addr.arpa. 300 IN     PTR     ec2-50-112-136-166.us-west-2.compute.amazonaws.com.
saving couple keypresses just in case

Re: AWS us-east-2 outage

#64
Just lost my email provider (https://status.postmarkapp.com/incidents/240161) to this and I'd bet my services are degraded/down. I know it's never a "good" time for an outage but this sure does suck for me right now. We've got an event this weekend and people can't sign up right now to buy tickets/etc.

Re: AWS us-east-2 outage

#65
post #44

Sorry all I jinxed it. Yesterday I was in a meeting and said "The only regional outages AWS has ever had were in us-east-1, so we should just move to us-east-2." Now I guess we have to move to us-west-2. :) Update: looks like it's only one zone anyway, so my statement still stands!

In all seriousness, we've been deploying everything on us-west-2, and it seems to have dodged most of the outages recently. Is there something special about that data center?

Re: AWS us-east-2 outage

#66

Update from AWS: they lost power to (part of?) a single DC in the use2-az1 availability zone. 10:25 AM PDT We can confirm that some instances within a single Availability Zone (USE2-AZ1) in the US-EAST-2 Region have experienced a loss of power. The loss of power is affecting part of a single data center within the affected Availability Zone. Power has been restored to the affected facility and at this stage the major…

Interesting to see it's been a loss of power that caused this. Usually the better datacenters have multiple levels of power redundancy including emergency backup generators.

Re: AWS us-east-2 outage

#68
post #44

Sorry all I jinxed it. Yesterday I was in a meeting and said "The only regional outages AWS has ever had were in us-east-1, so we should just move to us-east-2." Now I guess we have to move to us-west-2. :) Update: looks like it's only one zone anyway, so my statement still stands!

If us-west-2 goes down in the next few days we’ll expect an explanation.

Re: AWS us-east-2 outage

#69

Earlier quoted context omitted.

Depends what it’s stuck doing, but you might ctrl-c it and later manually unlock the state file (by carefully coordinating with colleagues and deleting the dynamo DB lock object if you’re using the s3 backend) when the outage is over.

Thanks, this comment made it very clear to me that I never want to touch a terraform system.

TF makes API calls to the underlying cloud. If those hang, you'll have to wait for them to time out.

Whether TF can update the state & release its locks would depend on where those were hosted. If they're in the downed AZ, then ofc. it can't do that, and manual intervention will be required afterwards. I forget if you can make those objects regional when stored in AWS or not. (You can in some other storages.)

… what would you expect to happen here?

Re: AWS us-east-2 outage

#70
post #65
post #44

Sorry all I jinxed it. Yesterday I was in a meeting and said "The only regional outages AWS has ever had were in us-east-1, so we should just move to us-east-2." Now I guess we have to move to us-west-2. :) Update: looks like it's only one zone anyway, so my statement still stands!

In all seriousness, we've been deploying everything on us-west-2, and it seems to have dodged most of the outages recently. Is there something special about that data center?

Classically, us-east-1 received most of the hate given its immense size (it used to be several times larger than any other) and status as the first large aws data center. It also seemed to launch new aws features first but that may have been my imagination. If true, I'm sure always running the latest builds was not great for stability.

us-west-2 has had outages as well but it is less common, even rare. I've been pushing companies to make their initial deployments onto us-west-2 for over ten years now. I occasionally get kudos messages in my inbox :)

Post reply on HN