Twilio seems to be affected as well
AWS multiple services outage in us-east-1
201–210 of 1001 posts
Re: AWS multiple services outage in us-east-1
#202Re: AWS multiple services outage in us-east-1
#203Re: AWS multiple services outage in us-east-1
#204It's fun watching their list of "Affected Services" grow literally in front of your eyes as they figure out how many things have this dependency. It's still missing the one that earned me a phone call from a client.
Re: AWS multiple services outage in us-east-1
#205Re: AWS multiple services outage in us-east-1
#206Re: AWS multiple services outage in us-east-1
#207Re: AWS multiple services outage in us-east-1
#208Is 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.
Also we use Docker Hub, NPM and a bunch of other services that are hosted by their vendors on us-east-1 so even non AWS customers often can't avoid the blast radius of us-east-1 (though the NPM issue mostly affects devs updating/adding dependencies, our CI builds use our internal mirror)
Re: AWS multiple services outage in us-east-1
#209Re: AWS multiple services outage in us-east-1
#210Their status page ( https://health.aws.amazon.com/health/status ) says the only disrupted service is DynamoDB, but it's impacting 37 other services. It is amazing to see how big a blast radius a single service can have.