Amazon Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Amazon Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Sonu Kumar (@sonu_since1998) reported 6 minutes ago

  @AmazonHelp @woohoogifting @PineLabs Amazon support team is too good not like zepto they don't even understand the issue

• 
  Monster 🇺🇸 (@MEGAMAGAMONSTER) reported 12 minutes ago

  @jjstyx @KikiwahT @amazon I’m sorry you’re having this issue too. Seems like it’s time for me to eliminate all business with Amazon.

• 
  Sam Rogers (@RealSamRogers) reported 13 minutes ago

  @JeffAthwart @ThereWBBourbon Buy the 12# can from Amazon and break it down into mason jars. YW

• 
  Breaking News Jack. (@jackmeridan) reported 14 minutes ago

  @Polymarket @amazon a solution to your overheating human problem.

• 
  Tracey Ryniec (@TraceyRyniec) reported 15 minutes ago

  Many have been wondering who can afford to buy the Baby Boomer homes, but what about the tech stock option owners? MSFT is down 25% over the last year. Amazon has underperformed for 5 years. Employees not getting rich from options anymore. Who will buy all those Seattle homes?

• 
  Alec Zakhary (@AlecZakhary) reported 15 minutes ago

  We made an AI the third member of our two-person Amazon business. Its first useful contribution was telling us not to launch anything. Three products entered our research funnel. All three came back NO-GO. That “no” may already have saved us more than the system cost to build. We are developers entering a physical-goods business we don’t yet understand. We didn’t need another chatbot. We needed a teammate who could research markets, process documents, track agreements, and remember why an idea was rejected months later. We had already tried building a personal work hub from nine Markdown files. After one month, it contained zero entries. The problem was not the file format. Recording work simply required more effort than retrieving it was worth. So we kept the files and changed the interface. In two days, we built Vera. She lives in our shared Telegram group and private chats. Her memory is a *** repository that both founders and the agent can commit to. During the first week, Vera: — produced 8 research reports, the largest around 50 KB — recorded 26 decisions with rejected alternatives — converted an XLSX pricing model into an analysis — delivered the team’s Monday briefing automatically The entire infrastructure is 1,388 lines of code. But the most important design decision wasn’t technical: Vera is organized around decisions, not tasks. Every decision records: — what we decided — what we rejected and why — the risks — what would make us reconsider A completed task tells you what happened. A durable decision prevents the team from paying for the same mistake twice. This matters more than the eight reports. Three months from now, we won’t need another AI summary of the same product niche. We’ll need the original verdict, the evidence behind it, and the condition under which that verdict should change. The system also failed in very real ways. One 36 KB analysis became a PDF containing little more than “Done, the report has been saved.” Another finished 59 KB report disappeared after a *** conflict and redeploy. Both failures changed the architecture. Conversation and execution are now separate. Long jobs checkpoint their progress and resume after interruption. That is the difference I keep seeing between agent demos and agent products: A demo proves the model can complete a task once. A product preserves the result, remembers why it matters, and survives being interrupted. We also made one embarrassingly predictable mistake: we spent a day building messaging infrastructure before checking what already existed. We should have bought the transport and built only the differentiated parts—shared team memory and resumable work. The system is still early and deliberately narrow: two allowed users, internal tools only, nothing sensitive. But it already feels less like a chatbot and more like a colleague who remembers the evidence behind every “yes” and every “no.” Which part should I unpack next: the decision memory, the disappearing 59 KB report, or the PDF that contained no report?

• 
  NWO4Lif3 (@NWO4Lif33) reported 18 minutes ago

  @SuperDuperInvst And it’ll pump again with the new CEO w/Amazon experience. Buy down here.

• 
  George Reid (@_GeorgeReid_) reported 20 minutes ago

  We ran an experiment to try and reduce our time-to-hire, which was already exceptionally low And it's all built around a neat WhatsApp strategy which took us over a year to realise First, what are we hiring for? Amazon advertising managers. Because we're processing thousands of applications per month, we built a scalable bespoke ATS that involves 4 rounds of screening. Some of these rounds are automated, and now don't involve a human at all. But, because we were SO fast at processing a candidates application, they weren't expecting the next stage within 30-seconds of applying As such, they click off the tab. Lose the tab. And our reminders to complete the stage perhaps got stuck in junk boxes or whatever. WhatsApp was the answer, where open rates are way higher, but we need permission to WhatsApp, otherwise we'd get in trouble just cold messaging Therefore, we experimented bring a WhatsApp request message inside the profile creation flow during application Now when users are about to complete their application, they just have to drop us a WhatsApp message first our system is built to acknowledge the whatsapp has been received, and associate it inside our ATS with that candidate Which tags them as "whatsapp: on" Which means, we're then free to send them a reminder message later on. We only send 1 reminder a day, for 4 days. And our completion rates skyrocketed. Meaning we're not losing brilliant candidates And we're processing faster than ever Good for them, and good for our clients - who are always hungry to see more validated candidates as soon as possible #itsalwaysdayone

• 
  ashish bhatt (@ashishbhatt22) reported 22 minutes ago

  @AmazonHelp I multiple times shared details every steps on X so now my TRUST on Amazon is down @amazon

• 
  ASHUTOSH SAXENA (@ashu5642) reported 24 minutes ago

  @amazonIN Not provided now again grace period will be over tomorrow still not delivered if any issue facing just drop a call or update or did not accept the order but this is burst services of amazon no any customer support

• 
  MrAckley257 (@StackEmUpAgain) reported 25 minutes ago

  @titus9a @freddavelynn This one Goose will bite if he thinks I'm in danger but the real dangerous one is Marree. She lunged at my gate with an Amazon driver handing me a package and she wasnt bluffing. Just like all Cane Corso. You'll seldom see a Cane Corso that will bluff on a charge. When they growl and their ears pin back they're gonna attack and the won't bluff. When they attack someone is having a terrible bad day.

• 
  X MAN 🇺🇸 (@TwittBoxer) reported 25 minutes ago

  Jeff Bezos needs to fix Amazon for its employees. HR is Horrible performance reviews and PIP programs are being abused by supervisors

• 
  Amazon Help (@AmazonHelp) reported 29 minutes ago

  @pgvcl123 Please copy and paste the link into a different web browser clearing cookies/cache and enabling desktop mode or try to access the link via desktop/laptop to connect with our team. Copy the link > paste the link in any browse > search the link > login to your Amazon account and once logged in, it will display 2 options, one is "continue previous chat" and other is "start a new chat". Click on start a new chat option, and it will connect to our team. Kindly connect with our team via order related account for our team to check and help you accordingly. -Fasi

• 
  benjamin franklin (@reckls) reported 32 minutes ago

  Poor customer service no response for Havells stealth fan issue..it's been 2 weeks no support .bought through amazon... @havellsindia

• 
  Chetan (@satan2986) reported 33 minutes ago

  @AmazonHelp I've already reached out days ago, please issue refund ASAP. @consaff @consumer