[romanhotsiy]

It's funny that the first place I go to learn about the outage is Hacker News and not https://status.aws.amazon.com/ (it's still reports everything to be "operating normally"...)

[bmcahren]

I made sure our incident response plan includes checking Hacker News and Twitter for actual updates and information.

As of right now, this thread and one update from a twitter user, https://twitter.com/SiteRelEnby/status/1468253604876333059 are all we have. I went into disaster recovery mode when I saw our traffic dropped to 0 suddenly at 10:30am ET. That was just the SQS/something else preventing our ELB logs from being extracted to DataDog though.

[unethical_ban]

So as of the time you posted this comment, were other services actually down? The way the 500 shows up, and the AWS status page, makes it sound like "only" the main landing page/mgt console is unavailable, not AWS services.

[albatross13]

Yeah, I tend to go off of https://downdetector.com/status/aws-amazon-web-services/

[murph-almighty]

I always got the impression that downdetector worked by logging the number of times they get a hit for a particular service and using that as a heuristic to determine if something is down. If so, that's brilliant.

[taf2]

Now 57 minutes later and it still reports everything as operating normally.

[mijoharas]

It shows errors now.

[1-6]

Community reporting > internal operations

[authed]

I usually go on Twitter first for outages.