Amazon Web Services status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
Full Outage Map
Amazon Web Services (AWS) offers a suite of cloud-computing services that make up an on-demand computing platform. They include Amazon Elastic Compute Cloud, also known as "EC2", and Amazon Simple Storage Service, also known as "S3".
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.
At the moment, we haven't detected any problems at Amazon Web Services. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Amazon Web Services users through our website.
- Website Down (60%)
- Sign in (20%)
- Errors (20%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Boca da Mata
|
Errors | 10 days ago |
 Township of Evan
|
Website Down | 25 days ago |
|
New York City
|
Website Down | 28 days ago |
 Ciudad Jardín
|
Website Down | 2 months ago |
 Kyiv
|
Sign in | 3 months ago |
 Chennai
|
Website Down | 3 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:
-
Jacklyn Taylor (@Ronindrake2) reported@awscloud @AmazonHelp @amazon Yo, can any of yall explain why a review that gets flagged for "community guidelines" refuses to tell you what the issue is? Like yall's bot goes "it violates rules!" But cant tell me what part? It obviously had to note what the issue was...
-
Dhananjay (@DhananjayKhark2) reported@AWSSupport Case open since Aug 13 — 15 days, no fix! AWS Glue blocked with AccessDeniedException (account-level) in ap-south-1. NOT an IAM issue. Needs backend account verification sync. Case: 178661799100381 Please escalate! 🙏 #AWS #AWSGlue @awscloud @AWSCloudIndia
-
✨Neil Blumenthal (@MrKryptonBTC) reported@AWSSupport So you guys wont fix my issue anymore? Ghosting me? 7days gone? Dont say weekend or bla bla. Stop wasting people's time
-
jd42 (@jdonovan42) reported@DarioCpx Pls recalculate considering the massive clouds the AI revs sit on. Each $1 in AI attaches $1.5-2.5X attached cloud biz and your down to 30-45% of revs. Then as open wgt models gain apply the 100% revenue retention vs. 60% on frontier and look at EBITDA % from frontier is 10-15% max. But nice try ;) No doubt Anthropic and OpenAI both stimulate demand for Amazon AWS. It creates 2x the cloud biz than it does the direct AI biz. So why not count the full picture of things vs just the #'s that fit one narrative.
-
Yuliyan Tsvetkov (@yuli_tsvetkov) reported@per_arneng @awscloud That's the control plane handshake, not Terraform being slow. Don't put cluster create on the incident path. Keep a warm spare per env.
-
Sai Manikanta ☕ (@rebuiltWithSai) reportedDay 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
-
Harikrishna KP (@harikp2002) reported@AWSSupport Two days into migrating to AWS and both new accounts I created are locked out of every single service. S3, EC2, Lambda, DynamoDB, all of it. The accounts show as ACTIVE. Support confirmed it needs a manual fix from an internal team, then went quiet for 28 hours. Three open cases, one phone call, still completely blocked. Sitting on AWS credits I literally cannot spend. Do better please!
-
M (@mdw864) reported@AWSSupport Either that or ask me to login, which I keep telling you I cannot login. It has nothing to do with 2FA. That is not the issue.
-
jayesh somani (@Jayesh_Somani_) reportedHey @awscloud I have lost access to the email id using which i have created an aws account and when i am trying to login with the id and password its redirecting us to reset passoword and the password is going to the email id which we have lost access here how can we solve this
-
The Trading Guy (@thetradingguy_) reported@AWSSupport I need resolution on this asap as I am having problem deploying my services. I am using alternative services which are costing a lot. So please resolve this and verify my account for cloudfront Case ID: 178582104300071
-
niknak (@niknak) reported@duckdb @ducklabs_com @awscloud Congrats on the check fellas but this is terrible news
-
Jim Osman (@EdgeCGroup) reported@awscloud Real innovation starts with people solving real problems.
-
Aqib Ansari (@Aqib_Ansari_) reported@AWSSupport Hey @AWSSupport any update on this? 8 Aug 2026: Issue opened 13 Aug 2026: Issue escalated to specialized team 18 Aug 2026: Still being investigated. Its 21 Aug 2026 now still no resolution or substantive update. Nearly 2 weeks for a service-access issue is frustrating experience
-
banhchung (@banhchugxanh) reported@POTATOCHEAPGAM1 @trythreews @awscloud i'm so down for cloud gaming, but 5gb internet feels like a stretch
-
The Trading Guy (@thetradingguy_) reported@AWSSupport , got no replies on this upon follow up message. Please look into it. Why is it so tough to resolve an issue?
-
Arian van Putten (@ProgrammerDude) reported@QuinnyPig @awscloud Not randomly redirecting to root console login page if I logged in with IAM identity center
-
Dan Lynch (@danlynch) reported@QuinnyPig @awscloud I need to sign in with LEGO 😎
-
Babak (@bbkhbb) reported@ajassy @AWSSupport what happened to customer obsession? I would like to invite you to review the interactions on AWS support case #178605390000779. There's no better way to put this, it's a sad joke. Reps don't appear to be incentivized to solve the problem nor to do the reading
-
Ikenna Iheanaetu (@Ikenna_dev) reported@awscloud Runtime request flow User → HTTPS → ALB → ECS Fargate → Container The ALB handles HTTPS using ACM and routes traffic to the ECS service. The service runs multiple tasks across Availability Zones, giving the application redundancy instead of relying on one server.
-
Yuyun Francis (@FrancisYuyun) reported@AWSSupport case ID (178590975600210) "account activation blocked 2+ weeks by Error 880104, case escalated internally Aug 5, no update since."
-
Jose njui (@jsnjui) reportedAnyone to sort my AWS account. Am unable to login. Any leads to urgently help fix @awscloud @aws_UGkenya
-
Corey Quinn (@QuinnyPig) reportedI want to hear the inside story of the largest @awscloud project. Not bill run, nor S3. I’m talking about what it took to fix all the hardcoded “jeff@“ userID stuff when @ajassy rose. Not kidding: it woulda been orders of magnitude easier for him to change his name to “Jeff.”
-
mark seery (@140ismymax) reportedPeter 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 #AI
-
Vinit Upadhyay (@vinitcodes) reported@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.
-
Piragash Velummylum (@piragash) reportedAt @awscloud we call this undifferentiated heavy lifting. @Cometml Opik does the hard work, so you can focus on the customer problems.
-
mail box (@mailbox28564784) reported@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
-
Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported@meaningoflights @jpschroeder @awscloud what issue do you have with that?
-
Christian Nonis (@christiannonis) reportedI 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
-
Somers (@jake__somers) reportedAWS keeps charging me 1000x what it should be for inference I try to use the new "generally available" Grok 4.6 Prompt caching doesn't work at all I spend $1.9 worth of inference testing caching I see my AWS bill is now $3400 This was an issue months ago as well. @AWSSupport
-
Base Builder (@basedbuilder_io) reportedWhat happens when agent payments go from "works on testnet" to "GA on AWS"? AgentCore Payments just shipped general availability via @awscloud and @CoinbaseDev. CDP Embedded Wallets handle the key material, x402 encodes the payment terms, and the whole thing runs as a single runtime-to-settlement flow on Base. No testnet disclaimer, no "coming soon" asterisk. The end-to-end shape: your agent detects a payable event, opens an x402 payment channel with the recipient, and settles in USDC through the embedded wallet, all without the user touching a key or approving a transaction. That's the runtime plumbing. What it unlocks is agents that can pay for services mid-execution without a human in the loop. API credits, inference time, data access, compute, whatever someone x402-wraps. The integration gotcha to watch is spending limit enforcement at the wallet layer. x402 handles the invoice generation and the payment terms, but the CDP embedded wallet's permissioning lives one layer up. If your agent holds a wallet with a default spend cap and then processes a batch of x402 invoices in sequence, the cumulative settlement can blow past the limit before the wallet context re-checks. The outcome is partial payment batches where some invoices clear and others bounce, and your error handling needs to know which ones landed. The dependent abstraction this pushes into focus is agent-to-rail routing: your agent picks a payment path based on cost, speed, and counterparty, not just a static USDC address. That's the next layer to wire.