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
AWS us-east-1 outage
31–40 of 1001 posts
Re: AWS us-east-1 outage
#32Re: AWS us-east-1 outage
#33It seems that only console is having the problem CLI works fine
I'm having CLI issues as well, they're using the same APIs under the hood. For example, I'm getting 503 errors for cloudwatch DescribeLogGroups.
Tried a few cli commands seems to be working fine for me. Maybe it is not for everyone or maybe It is just the start of something very worse. :(
Re: AWS us-east-1 outage
#34I love that every time this happens, 100% of the services on https://status.aws.amazon.com are green.
I don't see why they couldn't provide an error rate graph like Reddit[0] or simply make services yellow saying "increased error rate detected, investigating..."
Re: AWS us-east-1 outage
#35Can't SSM into ec2 in us-east-1
Re: AWS us-east-1 outage
#36We're not down and we're in us-east-1... maybe there is more to this issue?
I think could just be the console?
Re: AWS us-east-1 outage
#37Re: AWS us-east-1 outage
#38I love that every time this happens, 100% of the services on https://status.aws.amazon.com are green.
Those five 9s don't come easy. Sometimes you have to prop them up :)
Re: AWS us-east-1 outage
#39It'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"...)
Yeah, I tend to go off of https://downdetector.com/status/aws-amazon-web-services/
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.
Re: AWS us-east-1 outage
#40Running anything on us-east-1 is asking for trouble...