Live data from Hacker News

AWS us-east-1 outage

status.aws.amazon.com

61–70 of 1001 posts

Re: AWS us-east-1 outage

#62

Azure, 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

They can do this without an alliance. They very intentionally choose not to do it.

Every major company has moved away from having accurate status pages.

Re: AWS us-east-1 outage

#65
We make heavy usage of Kinesis Firehose in us-east-1.

Issues 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

#67
post #13

I 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? :)

Something like that has impacted the status page in the past. There was a severe Kinesis outage last year (https://aws.amazon.com/message/11201/), and they couldn't update the service dashboard for quite a while because their tool to do manage the service dashboard lives in us-east-1 and depends on Kinesis.

Re: AWS us-east-1 outage

#70

This 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.

Especially if enough Amazon internal tools rely on it - would be funny if there were a repeat of the FB debacle where Amazon employees somehow couldn't communicate/get back into their offices because of the problem they were trying to fix
Post reply on HN