Search on Amazon.com seems to be broken too. This doesn't appear to just be affecting their AWS revenue.
I've had issues login-in at amazon.com too... and IMDB is also down
AWS us-east-1 outage
391–400 of 1001 posts
Re: AWS us-east-1 outage
#392Earlier quoted context omitted.
It's certainly affecting a wider range of stuff from what I've seen. I'm personally having issues with API Gateway, CloudFormation, S3, and SQS
> We are experiencing API and console issues in the US-EAST-1 Region
I read it as console APIs. Each service API has its own indicator, and they are all green.
Re: AWS us-east-1 outage
#393I love that every time this happens, 100% of the services on https://status.aws.amazon.com are green.
[deleted]
Re: AWS us-east-1 outage
#394I'm now getting failures searching for products on Amazon.com itself. This is somewhat surprising, as the narrative always was that Amazon didn't do a great job of dogfooding their own cloud platform.
My Amazon order history showed no orders, but now is showing my orders again - so stuff seems to be getting either fixed or intermittent outages.
Re: AWS us-east-1 outage
#395It seems a bit long to fix! They probably paint themselves in a corner just like facebook few weeks ago. This make me think; Could it be that one day the internet will have a total global outage and it will take few days to recover?
If we have a total global outage, Stack Overflow will be unavailable, and the internet will never be fixed. :) Mostly joking, I hope...
Re: AWS us-east-1 outage
#396I suspect the ex-Amazonian PragmaticPulp cites was let go from Amazon for a reason. The COE process works, provided the culture is healthy and genuinely interested in fixing systemic problems. Engineers who seek to deflect blame are toxic and unhelpful. Don't hire them!
Re: AWS us-east-1 outage
#397Earlier quoted context omitted.
That sounds like the exact opposite of human-factors engineering. No one likes taking blame. But when things go sideways, people are extra spicy and defensive, which makes them clam up and often withhold useful information, which can extend the outage. No-blame analysis is a much better pattern. Everyone wins. It's about building the system that builds the system. Stuff broke; fix the stuff that broke, then fix the t…
I don't think engineers can believe in no-blame analysis if they know it'll harm career growth. I can't unilaterally promote John Doe, I have to convince other leaders that John would do well the next level up. And in those discussions, they could bring up "but John has caused 3 incidents this year", and honestly, maybe they'd be right.
> I have to convince other leaders that John would do well the next level up.
"Yes, John has made mistakes and he's always copped to them immediately and worked to prevent them from happening again in the future. You know who doesn't make mistakes? People who don't do anything."
Re: AWS us-east-1 outage
#398Haha my developer called me in panic telling that he crashed Amazon - was doing some load tests with Lambda
If he actually knows how to crash Amazon, you have a new business opportunity, albeit not a very nice one...
Re: AWS us-east-1 outage
#399Ah, this might explain why my AWS requests were so slow, or timing out, this afternoon.
Re: AWS us-east-1 outage
#400Earlier quoted context omitted.
If you count any time AWS is having a problem that impacts our production workloads then I think it's about 5:1. Dealing with "AWS is down" outages are easy because I can just sit back and grab some popcorn, it's the "dammit I know this is AWS's fault" outages that are a PITA because you count yourself lucky to even get a report in your personalized dashboard.
Yep. Random aside: any chance you are related to the Calculus on Manifolds Spivak?
Nope, just a fan. It was the book that pioneered my love of math.