Maybe azure was hosting some services there, getting ddos'd and all.
AWS us-east-1 down
31–40 of 331 posts
Re: AWS us-east-1 down
#32us-east-1 seems to be very 'special' compared to the other regions - I wonder if they will ever align it with the rest of them.
I think a lot of companies just do everything there and pinky promise one day they'll go multi-region.
Re: AWS us-east-1 down
#33I wonder if this is a coincidence or if us-east-1 is simply down enough that I'm just experiencing selection bias; but I posted a poll on twitter earlier today: https://twitter.com/dijit/status/1668678588713824257 Contents: > Has anyone ever actually had customers accept an outage because AWS was down; or is this just cloud evangelicalism copium? > [ ] Yeah, outages free pass > [ ] No, they say to use AZ's
> No, they say to use AZ's Using 3 AZs in us-east-1 won't save you. I guess a demanding customer would have said 'you should have implemented disaster recovery so you could failover to us-east-2' but that's easier said than done. The more regional AWS services you adopt, the bigger the impact is. How does one recover from a regional outage if their pipeline is in that region?
What I did once I was in the position of _having_ to provide that level of support, was to run the pipeline in a third region, different from the "prod" ones. That way, worst case you can't do deployments during the outage...
Another alternative studied was to use a thirdparty ci/cd service, outside of our network. It was discarded bc you never know where that would actually run
Re: AWS us-east-1 down
#34Why is it always us-east-1 though?
I have always stayed away from that region because it seems significantly less reliable than other regions.
Re: AWS us-east-1 down
#35I'm sure aws re:Inforce starting has nothing to do with it... https://reinforce.awsevents.com/livestreams/
Re: AWS us-east-1 down
#36this happened less than an hour after I altered our prod scheme, thought I brought down production, what a relief
I had a similar reaction. Oh no WTF, how did i break that?! Then my buddy texted me about us-east-1 being down. Then i thought "Oh thank god, this shitshow is someone else's fault."
Re: AWS us-east-1 down
#37us-east-1 seems to be very 'special' compared to the other regions - I wonder if they will ever align it with the rest of them.
Yep, it has issues so frequently. I wonder how many companies/teams start using AWS and blindly choose us-east-1 without realizing what they're getting into.
It's also quite annoying sometimes that some things _need_ to be in us-east-1, and if e.g. you are using Terraform and specify a different default region, AWS will happily let you create useless resources in regions that aren't us-east-1 that then mysteriously break stuff because they aren't in this one blessed region. AWS Certificate Manager (ACM) certificates are like this, I believe.
Re: AWS us-east-1 down
#38For those wondering: Currently PDT is 7 hours behind UTC. AWS can do so many things, reporting critical outage updates in UTC is not one of those things.
> AWS can do so many things, reporting critical outage updates in UTC is not one of those things.
Thank you for reminding me about one of my biggest mildest annoyances from working at AWS.
Re: AWS us-east-1 down
#39For those wondering: Currently PDT is 7 hours behind UTC. AWS can do so many things, reporting critical outage updates in UTC is not one of those things.
I thought it uses your browser time zone, is it not?
Re: AWS us-east-1 down
#40Why is it always us-east-1 though? I have always stayed away from that region because it seems significantly less reliable than other regions.
I thought I read that this is where they deploy new changes first. Can anyone confirm?