AWS's own management console sign-in isn't even working. This is a huge one. :(
AWS multiple services outage in us-east-1
141–150 of 1001 posts
Re: AWS multiple services outage in us-east-1
#142Seems to be upsetting Slack a fair bit, messages taking an age to send and OIDC login doesn't want to play.
Re: AWS multiple services outage in us-east-1
#143Considering the history of east-1 it is fascinating that it still causes so many single point of failure incidents for large enterprises.
Re: AWS multiple services outage in us-east-1
#144Docker is also down.
Re: AWS multiple services outage in us-east-1
#145Presumably the root cause of the major Vercel outage too: https://www.vercel-status.com/
No wonder, when I opened Vercel it showed a 502 error.
Re: AWS multiple services outage in us-east-1
#146The internal disruption reviews are going to be fun :)
The fun is really gonna start if the root cause of this somehow implicates an AI as a primary cause.
Re: AWS multiple services outage in us-east-1
#147Impossible to connect to JIRA here (France).
Login issues with Jira Cloud here in Germany too. Just a week after going from Jira on-prem to cloud
Re: AWS multiple services outage in us-east-1
#148To everyone that got paged (like me), grab a coffee and ride it out, the week can only get better!
To everyone who was supposed to get paged but didn't, do a postmortem, chances are your service is running via Twilio and needs migrating elsewhere.
Re: AWS multiple services outage in us-east-1
#149Internet, out.
Very big day for an engineering team indeed. Can't vibe code your way out of this issue...
Re: AWS multiple services outage in us-east-1
#150Happened to be updating a bunch of NPM dependencies and then saw `npm i` freeze and I'm like... ugh what did I do. Then npm login wasn't working and started searching here for an outage, and wala.