Using <i>very</i> naïve calculations, it looks like they lost up to $5 million in revenue because of this.<p><a href="http://www.wolframalpha.com/input/?i=%28Amazon.com%27s+annual+revenue+%2F+%28minutes+in+a+year%29%29+*+49+minutes" rel="nofollow">http://www.wolframalpha.com/input/?i=%28Amazon.com%27s+annua...</a><p>(This ignores a lot of important factors: not all pages being down, it happening in peak US hours, not accounting for the uninterrupted AWS revenue, having to purchase new hardware, damaged brand, etc)
For a potential reason why this might not make any difference to Amazons revenue/sales/whatever one should read this gem of a past by John Allspaw (Ops whiz kid for those who have no idea who he is) :: <a href="http://www.kitchensoap.com/2013/01/03/availability-nuance-as-a-service/" rel="nofollow">http://www.kitchensoap.com/2013/01/03/availability-nuance-as...</a>
> Site outages are never good things but feel particularly shaky when they are linked to e-commerce sites or other places where user data is stored.<p>Or, you know, when we've trusted the affected company in turn to run the infrastructure for so many of our businesses.