Slashdot Mirror
US Amazon.com Website Down For Over 1 Hour
CorporalKlinger writes "CNET News is reporting that Amazon's US website, Amazon.com, has been unreachable since 10:30 AM PDT today. As of posting, visiting www.amazon.com produces an 'Http/1.1 Service Unavailable' message. According to CNET, "Based on last quarter's revenue of $4.13 billion, a full-scale global outage would cost Amazon more than $31,000 per minute on average." Some of Amazon's international websites still appear to be working, and some pages on the US Amazon.com site load if accessed using HTTPS instead of HTTP."
It works just fine for me right now.
Also now you are Slashdotting it!
That whois lookup says absolutely nothing... I could add amazon.com.myserver.net as a dns record too, and it would have nothing to do with the lookups for amazon.com. The trick is to use whois to see what IP address www.amazon.com currently points at.
However, as has been pointed out, HTTPS works, so it's defininitely not a DNS issue. More likely someone along the chain corrupted a pooling link to the main http server and it propogated. I've done the same thing on apache2 servers in the past and had the same result; https still works fine, but http returns an error on key pages.
Of course, it's not a hack.
A fully-qualified DNS domain name ends with a dot, so you should type 'whois amazon.com.' instead.
Those "hacked" results you are getting are just bogus amazon.com.foo.bar. subdomains.
throw new SuccessException("Sig read successfully");
Well, if you worked there in the last 2 years you'd know that the giant monolithic app is dead and not mourned. I drew the short straw and had to sit in all day on the con call when they were taking it down area by area.
I still have more fans than freaks. WTF is wrong with you people?
GP meant a single ~1GB binary, not 900 million binaries. See Obidos
GP is approximately 3 years out of date. See Gurupa
Since I can't give any details directly, I'll let wiki do it.
Not particularly. Their S3 and EC2 services are completely seperate from their webserver. All throughout this outage, S3 and EC2 have been running flawlessly, as usual. If anything, this is a great reflection on how resilient their clusters are.
CNET has updated the post to include a statement from Amazon.com that the outage is over. The total downtime was something like 5 hours. From the CNET follow-up article:
"But as to the explanation, the company only hinted that its complicated computing infrastructure was, unsurprisingly, a culprit.
'Amazon's systems are very complex and on rare occasions, despite our best efforts, they may experience problems. We work to minimize any disruption and to get the site back as quickly as possible," the company said, declining to comment further.'"