Amazon Outage After Code Deployment Disrupts Checkout
Hours-long March 5 outage disrupted checkout and product pages; Amazon attributed it to a software code deployment and said services were later resolved.
CNBCAmazon says hours-long outage was triggered by 'software code deployment'
Business InsiderAmazon is down in an apparent outage affecting tens of thousands of shoppers
CNETAmazon Was Down for Thousands, but Seems to Be Back
ARS TechnicaAmazon appears to be down, with over 20,000 reported problems
USA TODAYIs Amazon down? Tens of thousands report problems with website
Overview
Amazon said an hours-long outage on March 5 was caused by a "software code deployment."
Reports on Downdetector spiked around 2 p.m. ET on March 5 and peaked between roughly 18,000 and 22,000 users, indicating widespread disruption to shopping that day.
Users reported checkout failures, fluctuating or incorrect prices, and problems with product pages and Amazon Fresh, and Amazon's support account said it was working to resolve the issue.
Downdetector data showed the largest share of complaints related to checkout, with report shares cited between 38% and 50%, and error-report peaks were reported between about 20,804 and 21,754.
Reports declined by late afternoon and Amazon said the incident was largely resolved by 8 p.m. ET, with Amazon Web Services described as functioning normally.
Analysis
Center-leaning sources frame the outage as significant yet contained: they use scale-focused terms like 'retail behemoth' and 'huge news', prioritize corporate and DownDetector metrics, highlight an Amazon Help apology without independent technical analysis, and structure the story from user inconvenience toward corporate reassurance and recovery numbers.
FAQ
Amazon attributed the hours-long outage to a software code deployment.
Users reported disruptions to checkout, product pages, fluctuating or incorrect prices, and Amazon Fresh.
Downdetector reports spiked around 2 p.m. ET, peaking between 18,000 and 22,000 users, with the largest share of complaints (38% to 50%) related to checkout.
Reports declined by late afternoon, and Amazon stated the incident was largely resolved by 8 p.m. ET on March 5.
Amazon Web Services was described as functioning normally during the incident.
