Hello world
AWS multiple services outage in us-east-1
321–330 of 1001 posts
Re: AWS multiple services outage in us-east-1
#322hello world
Re: AWS multiple services outage in us-east-1
#323LOL making one db service a central point of failure, charge gold for small compute instances. Rage about needing Multi AZ, make the costs come onto the developer/organization. But, now fail on a region level, so are we going to now have multi-country setup for simple small applications?
We maybe distributed, but we die united...
Re: AWS multiple services outage in us-east-1
#324Signal is down for me
Yes. https://status.signal.org/
> Signal is experiencing technical difficulties. We are working hard to restore service as quickly as possible.
Re: AWS multiple services outage in us-east-1
#325I like that we can advertise to our customers that over the last X years we have better uptime than Amazon, google, etc.
Just yesterday I saw another Hetzner thread where someone claimed AWS beats them in uptime and someone else blasted AWS for huge incidents. I bet his coffee tastes better this morning.
Re: AWS multiple services outage in us-east-1
#326Why would us-east-1 cause many UK banks and even UK gov web sites down too!? Shouldn't they operate in the UK region due to GDPR?
Integration with USA for your safety :)
Re: AWS multiple services outage in us-east-1
#327Choosing us-east-1 as your primary region is good, because when you're down, everybody's down, too. You don't get this luxury with other US regions!
One unexpected upside moving from a DC to AWS is when a region is down, customers are far more understanding. Instead of being upset, they often shrug it off since nothing else they needed/wanted was up either.
Re: AWS multiple services outage in us-east-1
#328Snow day!
Re: AWS multiple services outage in us-east-1
#329[deleted]
Re: AWS multiple services outage in us-east-1
#330To everyone that got paged (like me), grab a coffee and ride it out, the week can only get better!
Burn that SLO, next persons problem eh!