And what a surprise it's US-EAST-1 again...
AWS us-east-1 down
21–30 of 331 posts
Re: AWS us-east-1 down
#22I 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?
Re: AWS us-east-1 down
#23this happened less than an hour after I altered our prod scheme, thought I brought down production, what a relief
Re: AWS us-east-1 down
#24Re: AWS us-east-1 down
#25Re: AWS us-east-1 down
#26Re: AWS us-east-1 down
#27EDIT: thanks to those of you who have signed up in the past few minutes! Let us know if you have any feedback.
Re: AWS us-east-1 down
#28AWS can do so many things, reporting critical outage updates in UTC is not one of those things.
Re: AWS us-east-1 down
#29Re: AWS us-east-1 down
#30yep can't even get into console to diagnose / troubleshoot / fix