npm registry also down
AWS multiple services outage in us-east-1
181–190 of 1001 posts
Re: AWS multiple services outage in us-east-1
#182Seems to be really only in us-east-1, DynamoDB is performing fine in production on eu-central-1.
Re: AWS multiple services outage in us-east-1
#183As this incident unfolds, what’s the best way to estimate how many additional hours it’s likely to last? My intuition is that the expected remaining duration increases the longer the outage persists, but that would ultimately depend on the historical distribution of similar incidents. Is that kind of data available anywhere?
Re: AWS multiple services outage in us-east-1
#184DynamoDB is performing fine in production in eu-central-1.
Seems to be really limited to us-east-1 (https://health.aws.amazon.com/health/status). I think they host a lot of console and backend stuff there.
Re: AWS multiple services outage in us-east-1
#185Careful: NPM _says_ they're up ( https://status.npmjs.org/ ) but I am seeing a lot of packages not updating and npm install taking forever or never finishing. So hold off deploying now if you're dependent on that.
Yep. It's the auditing part that is broken. As a (dangerous) workaround use --no-audit
Re: AWS multiple services outage in us-east-1
#186Can't log into tidal for my music
Re: AWS multiple services outage in us-east-1
#187Is there any data on which AWS regions are most reliable? I feel like every time I hear about an AWS outage it's in us-east-1.
If you're using AWS then you are most likely using us-east-1 there is no escape. When big problems happen on us-east-1 it affect most of AWS services.
Re: AWS multiple services outage in us-east-1
#188Only us east 1 gets new services immediately others might do but not a guarantee. Which regions are a good alternative
Re: AWS multiple services outage in us-east-1
#189As this incident unfolds, what’s the best way to estimate how many additional hours it’s likely to last? My intuition is that the expected remaining duration increases the longer the outage persists, but that would ultimately depend on the historical distribution of similar incidents. Is that kind of data available anywhere?
To my understanding the main problem is DynamoDB being down, and DynamoDB is what a lot of AWS services use for their eventing systems behind the scenes. So there's probably like 500 billion unprocessed events that'll need to get processed even when they get everything back online. It's gonna be a long one.
Re: AWS multiple services outage in us-east-1
#190Robinhood's completely down. Even their main website: https://robinhood.com/