Amazon.com experienced a technical disruption on March 5, 2026, impacting user access to checkout functions, account dashboards, and product detail pages for several hours. The issue resolved by late evening without confirmed data breaches or prolonged service degradation.
- Outage occurred on March 5, 2026, affecting Amazon.com's checkout, account, and product pages
- Duration: approximately 4 hours, with service restored by 18:30 UTC
- No data breach or financial loss confirmed; root cause identified as a configuration error
- AMZN stock declined 0.6% during the event, with no broader market ripple
- Impact was isolated to Amazon’s platform, with no reported cascading effects on AAPL or CL=F
- Internal systems detected elevated error rates in checkout and account microservices
Amazon's primary online retail platform encountered a system-wide technical failure on March 5, 2026, disrupting access to core e-commerce functions for a significant portion of its user base. Customers reported widespread difficulties in loading product detail pages, accessing account settings, and completing purchases through the checkout process. The outage began at approximately 14:30 UTC and persisted for roughly four hours before service was gradually restored. The incident affected users across multiple regions, though no regional pattern in outage duration or severity was observed. Internal monitoring systems indicated a spike in error rates across Amazon's web services, particularly in the checkout and account management microservices. While no data compromise was reported, the disruption occurred during a peak shopping window, potentially impacting conversion rates and customer satisfaction. Despite the outage, Amazon’s parent company, Amazon.com, Inc. (AMZN), saw only a modest intraday stock movement, with shares declining 0.6% during the affected period. The broader technology sector, including peers Apple (AAPL) and energy benchmarks such as West Texas Intermediate crude (CL=F), remained largely unaffected, indicating the issue was contained within Amazon’s infrastructure and did not signal systemic risk. The company confirmed the resolution was achieved through a controlled system rollback and restart of critical backend services. Amazon has not released a detailed root cause analysis at this time, but internal communications indicate the failure stemmed from a configuration error in a core routing component. The incident underscores the importance of resilience in high-traffic digital platforms, particularly as e-commerce volumes remain near record levels.