I wonder how many 9s AWS is going for. Can't be a lot of 9s anymore.
Nine Fives is the new Five Nines!
Tell HN: AWS appears to be down again
151–160 of 646 posts
Re: Tell HN: AWS appears to be down again
#152If you haven't seen yet, news is it was a power loss: > 5:01 AM PST We can confirm a loss of power within a single data center within a single Availability Zone (USE1-AZ4) in the US-EAST-1 Region. This is affecting availability and connectivity to EC2 instances that are part of the affected data center within the affected Availability Zone. We are also experiencing elevated RunInstance API error rates for launches wi…
another example of a single dc in a single AZ rendering an entire region almost unusable. This has shades of eu-central-1 all over again.
Re: Tell HN: AWS appears to be down again
#153Earlier quoted context omitted.
Nobody ever got fired for using AWS.
If you rely solely on east 1 maybe?
AWS doesn't follow their own advice about hosting multi-regional.
When us-east-1 is sufficiently borked the management API and IAM services in all regions tend to go down with it.
Static infrastructures usually avoid the fallout, but anyone dependent on the API or otherwise dynamically created resources often get caught in the blast regardless of region
Re: Tell HN: AWS appears to be down again
#154The prevailing wisdom throughout the last couple of years was:
“ditch your on-prem infrastructure and migrate to a major cloud provider”
And its starting to seem like it could be something like:
“ditch your on-prem infrastructure and spin up your own managed cloud”
This is probably untenable for larger orgs where convenience gets the blank check treatment, but for smaller operations that can’t realize that value at scale and are spooked by these outages, what are the alternatives?
Re: Tell HN: AWS appears to be down again
#155Earlier quoted context omitted.
Does your server at home handle similar traffic to that of US-East-1 since you're comparing uptime? Simiarly, my laptop, if I keep it plugged in the wall, and enable httpd on localhost, will surely have better uptime than any of the top clouds. I'd bet that it'd have 100% uptime if I plugged in a UPS and cared for traffic on my local network only.
Your home ISP has 100% uptime? That's incredible.
Lets be real here, we don't need anywhere near 100% ISP uptime to beat AWS over the last couple months...
Re: Tell HN: AWS appears to be down again
#156Re: Tell HN: AWS appears to be down again
#157Is there a history of AWS downtimes available somewhere? This makes what, three times in as many months? edit: The question isn't necessarily AWS specific, just any data on amount of downtime per cloud provider on a timeline would be nice.
I have tons of this kind of data due to my side project, StatusGator. For some services like the big cloud providers I have data going back 7 years.
There indeed has been an uptick in AWS outages recently. You can see a bit of the history here: https://statusgator.com/services/amazon-web-services
Re: Tell HN: AWS appears to be down again
#158Earlier quoted context omitted.
If you rely solely on east 1 maybe?
AWS doesn't follow their own advice about hosting multi-regional. When us-east-1 is sufficiently borked the management API and IAM services in all regions tend to go down with it. Static infrastructures usually avoid the fallout, but anyone dependent on the API or otherwise dynamically created resources often get caught in the blast regardless of region
I didn't hear any reports of that happening in the most recent outage. The console was inoperable but you could work around using regional console host names.
Re: Tell HN: AWS appears to be down again
#159Earlier quoted context omitted.
Your us-east-1b may be the parents us-east-1c. The letters are randomised per AWS account so that instances are spread evenly and biases to certain letters don't lead to biases to certain zones.
Huh, that's interesting. Didn't know that, but makes sense.
It's pretty cool. If I recall, they call it "shuffle sharding."
Re: Tell HN: AWS appears to be down again
#160Earlier quoted context omitted.
AWS might be smart enough not to make that strategic blunder. They won't want to draw attention to the inaccuracies of their status page.
Perhaps, but the status page could exist within legal boundaries with a few trivial changes anyway. Why not just do that?
No one cares, including Amazon. This webpage isn't profiting off them. There is no valuable IP here being stolen.
Amazon has much bigger legal issues to focus on than some satire.