amazonlogo11Amazon.com is back up and running. We’ve updated this post with details.

Original story:

Online shoppers take notice: Amazon.com is down. This appears to have happened just before noon on Monday. We’re looking into this now, so check back for more updates.

On Friday night, all of Google’s services went down for five minutes. The New York Times also went down for two hours last week, and GitHub also experienced outages.

Update, 12:15 P.M. PST

Now when you try to go to Amazon.com, this message appears:

amazonoutage

We’re still trying to find out more about this. Check back here for updates.

Update, 12:20 P.M. PST

Now here’s the new message you get when going to Amazon.com:

amazonoutage2Here’s the text, which includes a hyperlink to the Amazon.com homepage:

We’re very sorry, but we’re having trouble doing what you just asked us to do. Please give us another chance–click the Back button on your browser and try your request again. Or start from the beginning on our homepage.

The three pieces of media to the right of the error message are quite odd: A children’s book called I’m Sorry … My Bad! by Bradley Trevor Greive, another kids book called Oops: A Diaper David Book by David Shannon, and a 2008 horror movie called Grave Mistake.

Update, 12:28 P.M. PST

Amazon Fresh is also down. You get a blank screen with the text “<UnknownOperationException/>” when going to the Amazon Fresh website:

amazonoutage3

Update, 12:33 P.M. PST

Looks like Amazon.com is back up. We’ve contacted Amazon to find out more about this, but it appears everything is back to normal. Hallelujah, shoppers.

But the real question is … how much did Amazon just lose in revenue for the 40 minutes or so that it went down?

Previously on GeekWire: An open letter to Jeff Bezos: A contract worker’s take on Amazon.com

Like what you're reading? Subscribe to GeekWire's free newsletters to catch every headline

Job Listings on GeekWork

Find more jobs on GeekWork. Employers, post a job here.