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 (71%)
- Sign in (14%)
- Errors (14%)
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 | 2 days ago |
 Township of Evan
|
Website Down | 17 days ago |
|
New York City
|
Website Down | 20 days ago |
 Ciudad Jardín
|
Website Down | 1 month 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:
-
Bob Tong (@bob80924) reported@Cloudflare @awscloud genuinely curious how tax/vat treatment works when your buyer is an anonymous agent wallet with no jurisdiction attached to it, feels like the accounting problem is way behind the payment rail problem right now
-
Harun R. (@harundotdev) reported2. 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.
-
mail box (@mailbox28564784) reported@amazonIN @amazon @awscloud I am extremely disappointed with Amazon's customer service. Despite returning the product, I have neither received my ₹1,400 refund nor a replacement. Repeated follow-ups and social media complaints have not resolved my issue.l
-
ShenYubao (@ssybb1988) reported@AWSSupport @awscloud AWS 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
-
Andrii Bidochko 🦉 (@andriibidochko) reportedThe 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:
-
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.
-
GamerUP (@GamerUPGaming) reported@TheRavenHelm man... are you detective seeds right? this is a new profile name ? whatever.. the "digital only direction" was announced more than 3 weeks ago.. not last week.. PSN servers are hosted by Amazon AWS, and amazon AWS had some disruptions today, they already solved the issue.
-
Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported@ivanburazin Why are you still using windows server ? It’s less than 10 minutes to fire up a @awscloud ECS cluster running free Linux
-
Nachman Mostofsky ✡︎🇺🇸 (@Mostofsky) reported@awscloud I signed up w/ new account to get @AWS_Gov. Got usual error. Created ticket. At about 3pm. Just got my phone call. At 11:30. AT NIGHT! To then get a message while on hold that there was an error, that a tech was assigned to case & would call me back. C'mon!
-
Joy | 🔥 (@JoyKingdomx) reportedAs 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.
-
Okko Ojala @okko@mastodon.social (@okko) reported@edwarddonner @awscloud @AWSSupport Combine a bug like that and spending caps, and the services would have been taken down and caused major losses of services worldwide.
-
Milan Jovanović (@mjovanovictech) reported@mrwcjoughin @awscloud @Azure I doubt this is a compute issue, looks like a bottleneck from past choices coming to bite you
-
Prof. D. Kumar (@DrDKumar_NRI) reported@AmazonHelp @amazonIN @awscloud Amazon pay UPI is blocked and can not verify device while other UPIs r working on porting the number. Been 03 days and the issue is still not resolved. LOOK INTO TICKET # V2289236874 and resolve at its earliest. Already cleared data, reboot!
-
IDrabs (@drabs_i) reported@PlayStation @awscloud Wtf you playing at fix the outage.
-
matyas.dev (@DevMatyas28516) reported@AWSSupport Still nothing happened after a week, after I sent your X account our issues numbers.
-
Ayush Awasthi (@Ayush_awa) reported@AWSSupport Its the third day today. The only mail I received from aws was all about “We are getting someone to investigate this” Since then I havent received any update. My only issue is that these things are time sensitive and you cant just take days after days with no real status updates
-
TeeBeeCTO (@TeeBeeCTO) reportedSetting up a new AWS account @awscloud … and get non stop errors on set up. Looks like their vibe coding dystopia worked… were all going to die because SkyNet will have error pages that end up giving us all death by error page. Amazing work… @JeffBezos !!
-
Prateek Gupta (@p_valuee) reported@AWSSupport My entire production is down since 3 days, I believe this is a P1 and should be treated like one @AWSSupport. Please help me with an ETA
-
Synapse Brief (@Synapse_Brief) reported@yugacohler @awscloud @CoinbaseDev The post frames this as a new capability, but Amazon already gave agents the ability to make purchases in December 2025. The Coinbase integration is the expansion, not the invention. The real bottleneck was never payment rails. It's authentication and authorization at scale. How does an agent prove it's authorized to spend, and how do you prevent a single compromised agent from draining a wallet? Coinbase's infrastructure solves the custody and settlement problem. AWS solves the identity and access management layer. The combination is what makes this production-ready. The "AI agents will outnumber humans" framing is hype. The real driver is that agents need to pay for API calls, data feeds, and compute resources autonomously. That's a practical requirement, not a sci-fi scenario. Stripe being involved is the quiet signal here. They handle the merchant side of the equation. Agents paying for things requires both the payer and the payee infrastructure. The managed aspect matters more than the payments themselves. AWS handles the compliance, KYC, and fraud detection layers that would otherwise be a nightmare to build. That's the real value proposition.
-
🦋Kieran🦋 💻 (@sir_divs_alot) reported@AWSSupport Thanks for your response and I've been keeping track for any updates very closely but the problem is these cases are either unassigned and if they are, no one is following up. I'm at the point of just giving up entirely cuz it's pointless waiting endlessly.
-
BOB-DO-THEM (@osangesua) reportedThis is a blatant lie intended to mislead the electorate. The glitch synchronisation in the BVAS is the reason he won't effect the upgrade because if an upgrade is carried on the BVAS, the entire calibration of glitches will disappear and the fear that @awscloud may have disabled or blocked the application that allows them to manipulate the BVAS is the reason for this unprovoked lies
-
Ivan Toma (@FounderRAVERK) reported@awscloud @Google @Microsoft The water problem is only going to get bigger. We already have technology that can help data centers produce their own cooling water from the sea. Let’s solve this together.
-
Yuyun Francis (@FrancisYuyun) reported@AWSSupport case ID (178590975600210) "account activation blocked 2+ weeks by Error 880104, case escalated internally Aug 5, no update since."
-
GettingMyGlitchOff (@GettingMyGlitch) reported@AWSSupport Again there is a mass wave of suspensions like in May, I'm assuming in error as I've been on this platform for over 10 years and this seems to be happening more frequently. Emails from mturk-noreply havent worked in a long time so any updates on this situation?
-
Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported@AWSSupport @AWSSupport @awscloud small business now facing issues with clients. Have provided all details and past 2hrs downtime on production server. Case 178699777500302 with Bill B. Also case 178555512600788, open since Aug 4, no response.
-
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.
-
J Bret Edwards (@jbecompslns) reporteddid @AWSSupport lay off all the accounts and billing people or are they all just swamped from all those insane billing estimate cases from last week? I don't remember the wait times being this bad when I was still working at AWS a few years ago. It's kind of surreal being on the other side of the fence, knowing exactly what needs to be done to resolve the issue, but then having to wait to get someone to actually look at the case. I think they laid off too many people. This is going to come back to bite them in the medium to long term.
-
Kartik Jain (@kartikjain0101) reported@awscloud you guy has lost your mind. payment got missing so team told me they will raising the request. account got hold, we have 250K unused credits, and now they are not initiation the account. wtf. our whole production is down.
-
Edward Donner (@edwarddonner) reported@okko @awscloud @AWSSupport That's why it's opt in. Netflix would likely not opt in and be fine with the risk. You could join them if you wish. I would prefer to face an outage if AWS has another billing disaster than have unbounded exposure.
-
Maciej Wilczyński (@wilczynski24) reported@opsolutehq @awscloud Otherwise, I believe it's not fully viable for full-range products. Example of Lovable: they have hundreds of potential use cases. That's where they are on credit-based systems rather than outcome-based systems, because you can't narrow down the overall cafeteria of use cases.