51–60 of 71 posts
The Route53 (AWS DNS service) is 100% SLA: http://aws.amazon.com/route53/sla/ I would hope they honor this dns issue under the same guidelines although its technically not the route53 service we are paying for.
I'm curious if the root cause of this is software failure or external attack. Aws is clearly at the point in size and competence that hardware failures are unlikely as root cause.
The opposite might also be true: Amazon might now have reached a point in size where they can't scale further upwards without losing visibility and control of part of their hardware.
It's all speculation anyway.
[deleted]
The status page icon for CloudFront turns red when HN comments reach 100.
What's everyone using to monitor external asset hosts? Is anyone dynamically switching between them, or failing back to local assets?
Is there a RoR Gem / configuration that will serve assets locally if an external asset host name doesn't resolve or times out?
It's a decent idea, but it would be better to do client-side. For this sort of event, knowing that the name resolves on the server doesn't give you any confidence it will resolve for the client. What would be really nice is if you could specify a fallback host in your DNS prefetch, and the browser would make it "just work."
Half the internet is down, Amazon.com is flapping, the AWS website doesn't have any assets, and status.aws has a Green checkmark with a little (i), 40 minutes after the problems start?! I love AWS but they really need to improve their procedures for communicating during outages. If your parent companies' billion dollar site can be affected in any way on the night before black friday, and even your own site is down, a…
We've built our systems to recover from failure states once we know there is a problem. AWS's inability to do that reliably is forcing us to own the problem ourself, and as a result, we will probably migrate away to use cheaper boxes in the cloud.
On the positive side, RDS has been solid.
From what I can see myself and from twitter feed, the issue looks resolved. But the AWS status page is still not reporting any update.