Funny. I followed the "down=yes" link and got the "Service unavailable" page, as expected.
Then I clicked on the "down=no" link for fun, and the page partially loaded for me. I refreshed it and got the whole front page loaded. And then one more time and got the "Service unavailable" again...
During my time as an engineer working on Amazon.com, we occasionally experienced outages of various lengths. One of the surprising details about these outages is that they really didn't result in any revenue loss. That is, it appeared that customers would simply wait until the website was available again to make their purchase. I would be surprised if that effect doesn't still happen today especially with the availability of Amazon on a variety of platforms (i.e. customers are comfortable ordering from their phones when they couldn't get to the website from their desktop computers).
That's a really interesting observation and substantiates a suspicion I've had: people generally have a good idea in mind of what they're going to buy and about when they're going to buy it. If at a particular moment the opportunity doesn't present itself, they'll simply delay the purchase until it's possible.
This would apply more to purchases from a specific and exceptional point than those which can be made from multiple providers. Say, my usual lunch spot is closed or out of an item, and I can walk down the street elsewhere (or a drugstore, etc.). However if you're selling hard-to-find exclusive items, or we've got an established relationship and the item isn't something I need right now, I'll simply get it later.
On the macro scale, it makes me suspect that shorter interruptions to service don't have a significant regional financial impact.
I thought for sure I'd have missed it and this would be one of those reports where the service was back up before the story gained traction, but as of 12:07 PM Pacific/US time I cannot navigate to Amazon's home page..
The amazing thing about this for me is that it reminds me that it was only a few years ago that even the biggest sites would have fairly frequent multi-hour outages, but these days it is pretty rare for this sort of thing to happen, particularly on a retail or otherwise direct-money generating site.
It's actually surprising it isn't down more often—internally, everyone has write access to prod and the rule is that if you deploy something to prod you need to be able to roll it back.* Apparently, though, someone has failed on the second item.
* Or so I was told in a job interview with the big A a few years back.
45 minutes of downtime so far, we're seeing mostly 503 responses with an occasional 200 getting through. We've seen a few other smaller outages for amazon.com in the past but this is definitely the longest in at least the last 3-4 years. Details at http://reports.panopta.com/amazon/server/96291
Interesting for all those people chasing "five nines": If 45 minutes today is their only downtime for the year, their annual uptime for 2013 will be just
"5 nines" works out to about 5 minutes of downtime a year: very challenging to achieve.
For reference, 4 nines is about an hour, and 6 nines is only ~30 seconds of downtime a year!
It's January, so not much is being lost here. We're looking at the slowest shopping season of the year. My unscientific estimate based on previous experience in retail would suggest sales are probably 1/50th peak Thanksgiving/Xmas volume.
Still, downtime is money, even if it isn't a world-changing amount of it.
It appears just to be the homepage, but all deep links are unauthenticated. That is: if you were logged in before the site started misbehaving, and use a deep link, you're not logged in on the page that loads.
I remember being in a talk by Dr. Vogels last year and he mentioning that *most of the Amazon.com North America services moved over to AWS in September 2011, many other services outside of NA were yet to move.
Running on AWS doesn't protect you from problems in the applications you're running on AWS. You can `rm -rf /` an EC2 instance and have plenty of problems.
I've been having odd behavior with DynamoDB all day. I wonder if it's related. The AWS Health Dashboard says things are fine, but I'm not so sure: http://status.aws.amazon.com/
Been a while since I've seen the amazon homepage down. Wow.
I know from the e-commerce side, when walmart.com went down last year we saw a traffic increase (enough to actually link to to the outage for walmart). I wonder if it'll happen here.
[+] [-] largehotcoffee|13 years ago|reply
[+] [-] up_and_up|13 years ago|reply
[+] [-] dmn001|13 years ago|reply
[+] [-] pferate|13 years ago|reply
Then I clicked on the "down=no" link for fun, and the page partially loaded for me. I refreshed it and got the whole front page loaded. And then one more time and got the "Service unavailable" again...
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] evanjacobs|13 years ago|reply
[+] [-] dredmorbius|13 years ago|reply
This would apply more to purchases from a specific and exceptional point than those which can be made from multiple providers. Say, my usual lunch spot is closed or out of an item, and I can walk down the street elsewhere (or a drugstore, etc.). However if you're selling hard-to-find exclusive items, or we've got an established relationship and the item isn't something I need right now, I'll simply get it later.
On the macro scale, it makes me suspect that shorter interruptions to service don't have a significant regional financial impact.
Though this is all armchair economics.
[+] [-] sneak|13 years ago|reply
Thanks for sharing a non-obvious data point.
[+] [-] photorized|13 years ago|reply
[+] [-] georgemcbay|13 years ago|reply
I thought for sure I'd have missed it and this would be one of those reports where the service was back up before the story gained traction, but as of 12:07 PM Pacific/US time I cannot navigate to Amazon's home page..
The amazing thing about this for me is that it reminds me that it was only a few years ago that even the biggest sites would have fairly frequent multi-hour outages, but these days it is pretty rare for this sort of thing to happen, particularly on a retail or otherwise direct-money generating site.
[+] [-] adrr|13 years ago|reply
[+] [-] mixedbit|13 years ago|reply
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] JohnFromBuffalo|13 years ago|reply
[deleted]
[+] [-] nbashaw|13 years ago|reply
[+] [-] film42|13 years ago|reply
[+] [-] edanm|13 years ago|reply
Does anyone have statistics for Amazon homepage uptime? I don't remember the last time I heard about Amazon being down.
And an hour after I read Patrick's (patio11) article on the Rails vulnerabilities. It's a scary day indeed.
[+] [-] dhosek|13 years ago|reply
* Or so I was told in a job interview with the big A a few years back.
[+] [-] jasonabate|13 years ago|reply
[+] [-] twistedpair|13 years ago|reply
[+] [-] pjungwir|13 years ago|reply
[+] [-] wikwocket|13 years ago|reply
[+] [-] danvideo|13 years ago|reply
all the internal links seem to be working fine http://www.amazon.com/gp/site-directory/
edit: added less ugly link
[+] [-] philwelch|13 years ago|reply
(cf. http://news.ycombinator.com/item?id=5142851)
[+] [-] lucb1e|13 years ago|reply
[+] [-] atlbeer|13 years ago|reply
[+] [-] dangrossman|13 years ago|reply
[+] [-] up_and_up|13 years ago|reply
61.1 Billion dollars (yearly revenue) / 31556926 seconds = 1936.18 dollars/second
[+] [-] 7rurl|13 years ago|reply
[+] [-] matznerd|13 years ago|reply
On a side note, the first thing I did was google, amazon down, and saw it was (http://www.isitdownrightnow.com/amazon.com.html) then I came here, and I am proud to say, this post was #1.
[+] [-] potatolicious|13 years ago|reply
Still, downtime is money, even if it isn't a world-changing amount of it.
[+] [-] falcolas|13 years ago|reply
[+] [-] smackfu|13 years ago|reply
[+] [-] noname123|13 years ago|reply
[+] [-] jerhewet|13 years ago|reply
[deleted]
[+] [-] khangtoh|13 years ago|reply
http://techcrunch.com/2013/01/31/amazon-com-down-503-service...
It's sad that "tech" bloggers don't research and report on news worthy things anymore, they just take what's on Hacker News and call it news.
[+] [-] rosser|13 years ago|reply
[+] [-] gchucky|13 years ago|reply
[+] [-] dsl|13 years ago|reply
These twitter gems demonstrate the cluelessness of the "hackers": https://twitter.com/NaziGods/status/297074050881183744 https://twitter.com/NaziGods/status/297070145141104641
[+] [-] RyJones|13 years ago|reply
[+] [-] k2xl|13 years ago|reply
[+] [-] jpsim|13 years ago|reply
[+] [-] dm8|13 years ago|reply
[+] [-] ultimoo|13 years ago|reply
[+] [-] ceejayoz|13 years ago|reply
[+] [-] alexakarpov|13 years ago|reply
[+] [-] dtwhitney|13 years ago|reply
[+] [-] jeffbarr|13 years ago|reply
[+] [-] setheron|13 years ago|reply
[+] [-] druiid|13 years ago|reply
I know from the e-commerce side, when walmart.com went down last year we saw a traffic increase (enough to actually link to to the outage for walmart). I wonder if it'll happen here.