Skip to content

Amazon’s Afternoon Outage: What Went Wrong and Why It Matters

brown and black floral box

On Thursday afternoon the giant online retailer went dark for several hours, leaving shoppers staring at error pages that featured the familiar “dogs of Amazon” meme. The trouble started around 2 PM Eastern, when error rates began to climb on monitoring services like Downdetector. By 4 PM the site was reporting roughly 21 000 errors per minute, a spike that slowly receded over the next two hours until the rate fell below 3 100.

During the peak of the incident the main catalog remained reachable, but product pages lost pricing information and the “Buy” button vanished entirely. The problem touched virtually every category, and it appeared the same whether users were in the United States, Europe, or elsewhere.

Amazon’s communications team issued a brief apology via email, acknowledging that “some customers may be experiencing issues while shopping” and thanking people for their patience while the problem was resolved. The tone was measured, but the outage still felt like a major inconvenience for anyone who had planned to place an order that day.

Importantly, the disruption was confined to the retail front end. Amazon Web Services, the cloud division that powers countless websites and apps, continued to run without incident. The contrast is stark; an AWS outage in October 2025 knocked out services for millions, yet the shopping site itself can still stumble on its own.

The hot take here is that Amazon’s retail platform remains a fragile single point of failure, a reality that most users forget until a glitch like this forces a checkout to freeze.

By the early evening the site had largely returned to normal, with product pages once again showing prices and purchase options. The episode serves as a reminder that even the most robust‑looking e‑commerce giants can experience hiccups, and that those hiccups can ripple through the day‑to‑day plans of a global customer base.

Via Amazon appears to be working normally following a major disruption Thursday afternoon