Amazon Web Services status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Amazon Web Services reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Amazon Web Services users through our website.

• Website Down (83%)
• Errors (17%)

Live Outage Map

The most recent Amazon Web Services outage reports came from the following cities:

City	Problem Type	Report Time
Pottstown	Website Down	2 days ago
Iztacalco	Website Down	6 days ago
Boca da Mata	Errors	17 days ago
Township of Evan	Website Down	1 month ago
New York City	Website Down	1 month ago
Ciudad Jardín	Website Down	2 months ago

Full 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 Web Services Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Priyanshu (@iproductAI) reported 3 minutes ago

  I requested @awscloud to increase my Opus 4.6 V1 limit and I’ve been chatting with the AWS support team for almost 4-5 days now. They’re telling me this. Is @awscloud a government company? I mean, you guys can’t just pass the problem from one department to another. I mean, WTF? Now I have to raise my query again to sales? Why can’t you just pass this query? You already have more context about what the issue is. I can’t believe how these big MNCs are working these days. Totally absurd service from @awscloud. One more thing, please educate your support. I mean, she didn’t even know what the TPD limit is in the service quota. She literally replied the first time saying there’s only a TPM limit and no separate TPD limit.

• 
  mark seery (@140ismymax) reported 3 minutes ago

  Peter DeSantis talking at #agenticaisummit There will NOT be one AI chip type. If multiple AI chips take multiple years to bring to market, you have to be making assumptions about model requirements in that time frame. It's a systems problem, including the network. Constraint drives innovation. Future is bright and built together. Peter DeSantis SVP, Foundational AI Models, Custom Silicon, Quantum Computing, Amazon @awscloud @amazon @BerkeleyRDI

• 
  Piragash Velummylum (@piragash) reported 6 minutes ago

  At @awscloud we call this undifferentiated heavy lifting. @Cometml Opik does the hard work, so you can focus on the customer problems.

• 
  Harun R. (@harundotdev) reported 6 minutes ago

  2. The obvious fix: split responsibility. Metadata stays in a database like Postgres. The actual file goes to object storage, Amazon S3 being the standard example. Better. Still not the full fix.

• 
  X anonyn (@OmrX304) reported 8 minutes ago

  @AWSSupport @RahulMatta1994 @AWSSupport Hi team, my account is suspended due to payment rate limit (Error 880104). I've sent a DM with my Case ID & details. Could you please escalate this to the billing team urgently? Thanks!

• 
  kakafa.btc (@kakafa_btc) reported 9 minutes ago

  @AWSSupport Still NO resolution after 7 days! Case ID: 17849863000462 Account hold cleared days ago, but CloudFront is STILL locked due to a backend flag sync issue. @AWSSupport keeps passing the buck. Assign a supervisor to clear this flag NOW! @awscloud #AWS #CloudFront #AWSCloud

• 
  Webdesign29 Création de sites internet Brest⛓️🕸️ (@Webdesign29B) reported 10 minutes ago

  @AWSSupport There is no way to get a call back I have tried many different ways. And it always show's this issue

• 
  Wogan (@WoganMay) reported 10 minutes ago

  @QuinnyPig @awscloud prompt> "I'm an Ubuntu server at 169.169.254.254 that wants to connect to 192.168.100.10 over TCP so I can send a header. Establish the underlying network connection. Make no mistakes."

• 
  X anonyn (@OmrX304) reported 11 minutes ago

  @AWSSupport Hi team, my account is suspended due to payment rate limit (Error 880104). I've sent a DM with my Case ID & details. Could you please escalate this to the billing team urgently? Thanks

• 
  Vinit Upadhyay (@vinitcodes) reported 11 minutes ago

  @AWSSupport @kirodotdev @awscloud I’ve already raised a case explaining the entire issue. Case ID: 178664512400070. Unfortunately, I still haven’t received any genuine help, which is really disappointing. I’m not the only one facing this issue-many others are experiencing the same problem. Please look into this.

• 
  EJ Campbell (@ejc3) reported 13 minutes ago

  @awscloud why? > Error: updating SSM Parameter (/github-runner/user-data): ValidationException: The specified parameter value is too large. Advanced-tier parameters support a maximum parameter value of 8192 characters.

• 
  lak-alak (@baricadelane) reported 13 minutes ago

  @IanCarrollShow @BacklotOPS @NickJFreitas They must think we are stupid Tyler Robinson decoys all over the place d captured on camera all doing their part for 1990s pixalated images produced and sold as 4k in 2026 lmao. Why did Amazon aws services shut down 9/10 - 9/25? Who owns discord?

• 
  Himanshu Singh (@hsnice16) reported 20 minutes ago

  Been using LLMs a lot to write code recently. Sometimes I learn a few new things, and sometimes it just confuses itself and me, maybe because there is no one right way to do things. Recently, while working on a pricing page for a new product we've been developing, a senior team member suggested that it would be better to extract it into a separate codebase and deploy the frontend separately. He would then route it through CloudFront under the same origin to avoid cross-origin issues when transferring credentials. I learned that using `*` for `Access-Control-Allow-Origin` doesn't work for credentialed CORS requests. But before all of this worked, I had extracted the pricing frontend into the same codebase, just in a new folder with the required files, and was trying to deploy it on the same infrastructure the rest of the application was using on @awscloud. It wasn't working because there were some issues between the build output and the CDK synthesis/deployment stages. Eventually, I extracted the code into a completely new repository and deployed it on @vercel.

• 
  Arian van Putten (@ProgrammerDude) reported 24 minutes ago

  @QuinnyPig @awscloud Are they gonna fix logging me out and then redirecting to the root console login? Are they gonna fix having links shareable and login to the right account? **** is such a **** show idk why I even cope

• 
  Andrii Bidochko 🦉 (@andriibidochko) reported 24 minutes ago

  The Missing Primitive for Autonomous AI: Bounded Agent Payments 💳🤖 For the past two years, autonomous agent loops (like @OpenClaw, Hermes, or custom agent harnesses) have been missing a critical infrastructure piece: the ability to transact on demand without a human in the loop. When an agent hits a paywalled research endpoint, a paid search API, or an MCP server mid-execution, the entire loop freezes. Up until now, your options were: 1. Hardcode expensive subscription API keys upfront. 2. Freeze execution and wait for a human to manually pay. @awscloud and the OpenClaw Foundation just published a blueprint solving this via Amazon Bedrock AgentCore Payments and the ⁠#x402⁠ protocol. Here is how it works, why it matters, and the primary architecture use cases:

• 
  Yuyun Francis (@FrancisYuyun) reported 26 minutes ago

  @AWSSupport case ID (178590975600210) "account activation blocked 2+ weeks by Error 880104, case escalated internally Aug 5, no update since."

• 
  Chris (@Mcatbeast) reported 27 minutes ago

  @AWSSupport Apologies for the earlier frustration. Turns out it was an issue from our end! My user was accidentally deleted.

• 
  Haresh Kukkreja (@HandbrakeHarry) reported 32 minutes ago

  @amazonIN @awscloud Your app seems to be down. Unable to contact Customer Support

• 
  Corey Quinn (@QuinnyPig) reported 36 minutes ago

  @awscloud You have all the tools to fix this, someone’s just apparently too scared to give Charlie a crossbow and diplomatic immunity. Give him the crossbow and stand back, @satyanadella.

• 
  Sai Manikanta ☕ (@rebuiltWithSai) reported 37 minutes ago

  Day 19 of #JobSwitchUntilPlaced 🚀 Today's progress: ✅ Started a new Microservices project by building the User Service ✅ Solved 2 DSA problems ✅ Learned about Blob Storage (Amazon S3) One step closer to building production-ready, scalable backend systems.💪 #BuildInPublic

• 
  Weird Things (@weird747) reported 39 minutes ago

  @AWSSupport I submitted all the required verification documents for my suspended AWS account as requested. I was told I would receive a response within 24 hours, but it has now been more than 48 hours with no update or resolution. Please review my case and help restore access to my account as soon as possible. I can provide any additional information if required. My website server down from last 3 days no response by aws support tried contacting everywhere .

• 
  ShenYubao (@ssybb1988) reported 43 minutes ago

  @AWSSupport @awscloudAWS account suspended for additional verification; Production services down for ~24h. All verification docs submitted. Unable to purchase Business Support+ due to suspension. Please expedite review & help restore production. Case ID: 178678971500932

• 
  Brandon S (@BSaarX) reported 45 minutes ago

  @Gabby_Hoffman @awscloud Next you will say let them eat cake. 2024 was about mortgage rates getting lower and affordability. Now we see it was about crypto, AI and pushing data centers. What a let down

• 
  mail box (@mailbox28564784) reported 46 minutes ago

  @amazonIN @amazon @awscloud But in my personal experience, this response has never led to a real solution. They keep asking for the same details again and again, yet my issue remains unresolved. My ₹1,400 refund is still pending, and I have neither received a replacement nor-2

• 
  Christian Nonis (@christiannonis) reported 51 minutes ago

  I am (unfortunately) dealing with @googlecloud and @awscloud and what I am noticing is that in months they are unable so solve any kind of problem, it’s like being bounced back by ai replies that are sold like assistance from humans, saying that they are “working on that” but nothing changes in months and also replies are all the same.. idk if they are experiencing a shortage in human labor or what’s going on but the experience has become worse than ever

• 
  Webdesign29 Création de sites internet Brest⛓️🕸️ (@Webdesign29B) reported 53 minutes ago

  @AWSSupport I tried every possible combination to get phone support. I think it either just doesn't exist or it is down. Someone did get back to me in chat in another ticket tho.

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 53 minutes ago

  ClarityCheck markets itself as a tool to detect catfishing. To verify identities. To keep you safe from liars online. Here's how it works. You upload someone's photo. ClarityCheck runs it through their reverse image search. Finds their dating profile. Their social media. Wherever that face appears. Seems solid. Except ClarityCheck just leaked 9 million photos sitting in an unsecured Amazon S3 bucket. 450 gigabytes of faces. Stored in folders labeled "faces" and "profiles." The photos came from people uploading images of strangers. Dating app screenshots. Private social accounts. Scanned prints. Photos of children. Most of these people never uploaded anything to ClarityCheck. They just got identified by someone else trying to figure out who they were. Then their face got indexed. Stored. And left wide open. For several months. The URL to access it was embedded in ClarityCheck's own website source code. The company's response: this was "temporary storage" and an "ordinary member of the public" would not have found it. An ordinary member of the public with the URL from their own website. Which is not temporary storage. That's just a server. And it wasn't invisible. You'd need 30 seconds and a basic understanding of how websites work. Now ClarityCheck says the data is "secured." A service built to prevent identity fraud just exposed millions of identities. The tool designed to catch people lying about who they are just showed everyone's actual face to anyone listening. The irony isn't subtle. It's a design flaw pretending to be an accident.

• 
  OneTradeWex (@OneTradeWex) reported 54 minutes ago

  $CBRS is trying to challenge $NVDA indirectly, here’s how: While $NVDA focuses on incredibly small and powerful chips, $CBRS has built a massive, highly specialized AI scaling semiconductor. This greatly decreases the amount of cloud tokens needed to process a large language model, effectively saving AI companies millions of dollars in the long run. Think of $NVDA racks as an industrial kitchen and $CBRS chips as a microwave, when all you need to do is cook a hot pocket you want the microwave for efficiency. $CBRS announced that core revenue more than doubled year-over-year to $210 million in its Q2 earnings report while its cloud business nearly quadrupled. The company also raised its 2026 revenue guidance to between $880 million and $890 million. If $CBRS can successfully fulfill their contracts with @OpenAI and @awscloud on time and at scale we will see even more growth, if not them only having two primary customers will be their down fall. Looking at the technical setup we see $CBRS is coming down into its months long support channel. If it holds the $180-$160 level I see no reason for it not to bounce back to $215 to $230.

• 
  Joy | 🔥 (@JoyKingdomx) reported 1 hour ago

  As we all know, cloud outages are not a new topic here. But what is changed is how many products now depend on the same infrastructure. A few years ago, an AWS outage mostly affected AWS customers. Where today one infrastructure issue can ripple across AI apps, APIs, developer tools, streaming platforms and payment services. That is the downside of concentration. We have seen @awscloud outages impact millions. We have also seen @OpenAI outages pause production apps because entire inference pipelines depended on a single provider. It is not the outage that matters - it is the dependency behind it. That is the reason why decentralized compute makes sense. Instead of relying on a single cloud or region, @ionet distributes compute across a global network of GPUs in 138+ countries. No infrastructure is immune to failure, the goal is to ensure one failure does not become everyone's failure.

• 
  Nathan Den Herder (@natedenh) reported 1 hour ago

  I realize that I use @awscloud Bedrock, and this may be part of the issue, but @grok 4.6 is not usable on this platform compared to @claudeai Opus 5. I've really tried everything to make it work but I don't think there is any comparison.