AWS us-east-1 outage
61–70 of 1001 posts
Re: AWS us-east-1 outage
#62Azure, Google Cloud, AWS and others need to have a “Status alliance” where they determine the status of each of their services by a quorum using all cloud providers. Status pages are virtually useless these days
Every major company has moved away from having accurate status pages.
Re: AWS us-east-1 outage
#63It seems that only console is having the problem CLI works fine
Re: AWS us-east-1 outage
#64Re: AWS us-east-1 outage
#65Issues started ~1:24am ET and resolved around 7:31am ET.
Then really kicked in at a much larger scale at 10:32am ET.
We're now seeing failures with connections to RDS Postgres and other services.
Console is completely unavailable to me.
Re: AWS us-east-1 outage
#66For example, the sign-up page appears to be working: https://portal.aws.amazon.com/billing/signup#/start
Are websites that run on AWS us-east up? Are the AWS CLIs working?
Re: AWS us-east-1 outage
#67I love that every time this happens, 100% of the services on https://status.aws.amazon.com are green.
Makes you wonder if they have to manually update the page when outages occur. That'd be a pretty bad way to go, so I'd hope not. Maybe the code to automatically update the page is in us-east-1? :)
Re: AWS us-east-1 outage
#68Re: AWS us-east-1 outage
#69Makes me glad I am in us-east-2.
Re: AWS us-east-1 outage
#70This got me thinking, are there any major chat services that would go down if a particular AWS/GCP/etc data centre went down? You don't want your service to go down, plus your team's comms at the same time.