Thursday afternoon turned into a shopping nightmare for tens of thousands of Amazon customers. Around 2:30 p.m. ET, the e-commerce giant’s platform started glitching, and by 3:49 p.m., roughly 20,000 users were reporting serious problems. For anyone who’s ever relied on Amazon for quick purchases, this was the kind of disruption that makes you realize how dependent we’ve become on these services.
The scope of the outage wasn’t just a minor hiccup either. Shoppers flooded business forums and social media complaining about checkout failures, payment errors, and prices that kept changing on product listings. Imagine loading up your cart, ready to buy, only to get rejected at payment. Or worse, watching prices jump around like they’re on some kind of digital rollercoaster.
What Actually Broke
Amazon eventually figured out what went wrong. They blamed it on a software code deployment that went sideways. In their statement to Business Insider, the company said: “We have resolved the issue, which was related to a software code deployment, and website and app are now running smoothly.”
A code deployment problem is the kind of thing that happens when you’re pushing updates or changes to live systems. It’s not inherently a huge deal, but when it hits a platform as massive as Amazon, the ripple effects are immediate and painful. By 8 p.m. ET, Downdetector had stopped receiving a flood of complaints, meaning things were back to normal.
Why This Isn’t About Web Services
One thing worth noting: this outage had nothing to do with Amazon Web Services, the company’s cloud infrastructure division. That’s actually important because AWS powers a huge chunk of the internet. When AWS goes down, everything connected to it tends to go down with it.
Back in October 2025, an AWS outage actually knocked out Wordle, Slack, Snapchat, and Reddit all at once. That was caused by a DNS error in Amazon’s Virginia data center. This time? Just the shopping platform itself. Still frustrating for customers, but contained to one part of Amazon’s massive operation.
The technology required to keep something like Amazon running is staggering. When you think about how many transactions, price updates, and inventory checks happen every second, it’s actually surprising these outages don’t happen more often.
What This Means
For casual shoppers, this was just an inconvenience. But for businesses selling through Amazon’s marketplace, a few hours of downtime can mean real lost revenue. And for Amazon itself, every minute of unavailability is a reminder that even the biggest players aren’t immune to system failures.
The real question isn’t whether outages will happen again. They absolutely will. The question is whether companies will ever be honest about how fragile these systems are when so much commerce depends on them staying up. We treat Amazon like infrastructure now, not just a retail platform. And infrastructure is supposed to be reliable.
