It's the second time in less than a week that AWS have failed to update their status page during service disruption and then filed it under 'increased error rates'.

Don't get me wrong, I love AWS and use it every day, but it's a little insulting to pretend that things haven't gone wrong when they quite obviously have.

I know Amazon aren't the most transparent company in the world but why even bother having a status page if everyone has to turn to twitter to validate the outage?

Last night while sitting around waiting for cloudfront to come back so I could get on with my work I turned to HN to give me a bit of reading material. My word, sooooo many of the articles linked to on the front page were missing their static assets because of the AWS outage. Would be really interesting to know what percentage of the internet was affected.

I'm really freaking tired of the AWS Status page using the green "info" marker for major outages.

bottom line: always CNAME your asset domain.

This is incredibly upsetting. Amazon publishing false status reports for public consumption is directly equivalent to libeling every single customer they have, simultaneously.

I was trying to register a new domain during this outage. When my registrar's site wasn't loading correctly, I dug around and discovered they use AWS. I then checked Amazon's AWS status page to see if they were the culprit.

Nothing but green icons across the board.

Amazon having the audacity to tell such a gargantuan lie seemed inconceivable, so I was absolutely convinced that the problem was the registrar's fault. I decided the registrar must have become shoddy at some point without me noticing, and so I made a "to-do" note for myself to switch to another registrar this weekend.

If I hadn't happened to stumble across this HN submission, the registrar I use would have lost a long-time customer due to Amazon publishing a maliciously false status page for AWS.

Is there some way to do a fallback if the DNS server is down?

Also if my host is down can I "quickly" try another host? I know that it's possible in my own app, but can I tell a browser to do it, as a web publisher?