Skip to main content [aditude-amp id="stickyleaderboard" targeting='{"env":"staging","page_type":"article","post_id":631499,"post_type":"story","post_chan":"none","tags":null,"ai":false,"category":"none","all_categories":"business,cloud,","session":"B"}']

Amazon down: Product pages coming up Error 400 (bad request)

amazon-boxUpdated 1:16 p.m. Pacific

Amazon.com and you’re (not) done? Well, for a while today.

[aditude-amp id="flyingcarpet" targeting='{"env":"staging","page_type":"article","post_id":631499,"post_type":"story","post_chan":"none","tags":null,"ai":false,"category":"none","all_categories":"business,cloud,","session":"B"}']

Amazon.com was not exactly down, but the site might as well have been. All product searches were coming up error 400, though as for 1:16 p.m. Pacific today, it appears as if the problem has been fixed.

Twitter is blowing up about the problem, which is more than a little embarrassing for a company that prides itself on providing uptime assurance in the cloud for thousands of web-based businesses:

AI Weekly

The must-read newsletter for AI and Big Data industry written by Khari Johnson, Kyle Wiggers, and Seth Colaner.

Included with VentureBeat Insider and VentureBeat VIP memberships.

Realistically, however, this is not a cloud failure or a web serving error. It’s a programming or configuration error, a bad request being sent to the server. Amazon should have it fixed shortly.

VentureBeat's mission is to be a digital town square for technical decision-makers to gain knowledge about transformative enterprise technology and transact. Learn More