I 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 :)
https://aws.amazon.com/compute/sla/
looks like only four 9's
AWS us-east-1 outage
141–150 of 1001 posts
Re: AWS us-east-1 outage
#142booker.com/mindbody random areas are affected
Re: AWS us-east-1 outage
#143Re: AWS us-east-1 outage
#144I worked at a company that hired an ex-Amazon engineer to work on some cloud projects. Whenever his projects went down, he fought tooth and nail against any suggestion to update the status page. When forced to update the status page, he'd follow up with an extremely long "post-mortem" document that was really just a long winded explanation about why the outage was someone else's fault. He later explained that in his…
This gets posted every time there's an AWS outage. It mind as well be a copy pasta at this point.
Re: AWS us-east-1 outage
#145The majority of our errors stem from:
- writing to Firehose (S3-backed)
- publishing to eventbridge
- terraform commands to ECS' API are stuck/hanging
Other spurious errors involving kinesis but nothing alarming. us-east-1
Re: AWS us-east-1 outage
#146Earlier quoted context omitted.
Being dishonest about SLAs seems to bear zero cost in this case?
It's not really dishonest though because there is nuance. Most everything in EC2 is still working it seems, just the console is down. So is it really down? It should probably be yellow but not red.
if you cannot access the control plane to create or destroy resources, it is down (partial availability). The jobs that are running are basically zombies.
Re: AWS us-east-1 outage
#147I worked at a company that hired an ex-Amazon engineer to work on some cloud projects. Whenever his projects went down, he fought tooth and nail against any suggestion to update the status page. When forced to update the status page, he'd follow up with an extremely long "post-mortem" document that was really just a long winded explanation about why the outage was someone else's fault. He later explained that in his…
I can totally picture this. Poor guy.
Re: AWS us-east-1 outage
#148Getting 500 errors across the board on systems trying to hit s3
Ditto
Re: AWS us-east-1 outage
#149Just curious does it still make sense to claim that up time is X numbers of 9? (e.g. 99.999%)
Re: AWS us-east-1 outage
#150[deleted]