Oh no... may be LaLiga found out pirates hosting on AWS?
this is how I discover that is not just Serie A doing this shenanigans. I'm not really surprised
AWS multiple services outage in us-east-1
341–350 of 1001 posts
Re: AWS multiple services outage in us-east-1
#342Just a couple of days ago in this HN thread [0] there were quite some users claiming Hetzner is not an options as their uptime isn't as good as AWS, hence the higher AWS pricing is worth the investment. Oh, the irony. [0]: https://news.ycombinator.com/item?id=45614922
My recommendation is to use AWS, but not the US-EAST-1 region. That way you get benefits of AWS without the instability.
Re: AWS multiple services outage in us-east-1
#343“Based on our investigation, the issue appears to be related to DNS resolution of the DynamoDB API endpoint in US-EAST-1. We are working on multiple parallel paths to accelerate recovery.” It’s always DNS.
It's always US-EAST-1 :)
Re: AWS multiple services outage in us-east-1
#344When did Snapchat move out of GCP?
They might have an implicit dependency on AWS, even if they're not primarily hosted there.
Re: AWS multiple services outage in us-east-1
#345Atlassian cloud is also having issues. Closing in on the 3 hour mark.
Re: AWS multiple services outage in us-east-1
#346Just a couple of days ago in this HN thread [0] there were quite some users claiming Hetzner is not an options as their uptime isn't as good as AWS, hence the higher AWS pricing is worth the investment. Oh, the irony. [0]: https://news.ycombinator.com/item?id=45614922
We've been running our services on Hetzner for 10 years, never experienced any significant outages.
That might be datacenter dependant of course, since our root servers and cloud services are all hosted in Europe, but I really never understood why Hetzner is said to be less reliable
Re: AWS multiple services outage in us-east-1
#347Now, I may well be naive - but isn't the point of these systems that you fail over gracefully to another data centre and no-one notices?
Re: AWS multiple services outage in us-east-1
#348I find it interesting that AWS services appear to be so tightly integrated that when there's an issue in a region, it affects most or all services. Kind of defeats the purported resiliency of cloud services.
Yeah I think there are a number of "hidden" dependencies on different regions, especially us-east-1. It's an artifact of it being AWS' largest region, etc.
why dont they have us east 2, 3, 4 etc. Actually have different cities.
Re: AWS multiple services outage in us-east-1
#349I find it interesting that AWS services appear to be so tightly integrated that when there's an issue in a region, it affects most or all services. Kind of defeats the purported resiliency of cloud services.
I think a lot of its probably technical debt. So much internally still relies on legacy systems in US-East-1, and every time this happens I'm sure theres a discussion internally about decoupling that reliance which then turns into a massive diagram that looks like a family tree dating back a thousand years of all the things that need to be changed to stop it happening.
There's also the issue of sometimes needing actual strong consistency. Things like auth or billing for example where you absolutely can't tolerate eventual consistency or split-brain situations, in which case you need one region to serve as the ultimate source of truth.
Re: AWS multiple services outage in us-east-1
#350SES and signal seem to work again