Amazon Web Services status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
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 (83%)
- Errors (17%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Website Down | 2 hours ago |
|
|
Website Down | 3 days ago |
|
|
Errors | 15 days ago |
|
|
Website Down | 29 days ago |
|
|
Website Down | 1 month ago |
|
|
Website Down | 2 months ago |
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:
-
Keith (@happy_keith) reported@amazon @awscloud @AmazonUK What does it take to get you to respond to a serious problem DO NOT tell me to go to customers services AI as it is incapable of responding to the issue This is a complete farce !!!!!!
-
Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported@jeffdafo @ivanburazin @awscloud Even aspnetcore can run on Linux now - there is no excuse to have (and pay through the nose) for Windows server licenses)
-
Stephen “The Yellow Dart” Schutt (@schuttsm) reported@QuinnyPig @awscloud I get charged $0.55 every month. Fix that
-
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
-
Gopal Goti (@gopal_goti) reported@AWSSupport @AWSSupport Thank you for the update, but 'high volume' cannot justify a support case sitting completely 'Unassigned' for over 4 days for a basic account verification issue. This is not a complex technical issue. it is a backend system error on the AWS verification form.
-
Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported@AWSSupport Live production server is down. Case 178699777500302 (Account Reinstatement) filed with a callback requested — call failed to initiate. Earlier case 178699433100264 still unassigned. Need urgent help, can someone DM me?
-
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:
-
Yuyun Francis (@FrancisYuyun) reported@AWSSupport case ID (178590975600210) "account activation blocked 2+ weeks by Error 880104, case escalated internally Aug 5, no update since."
-
Jaimin Vaghani (@jaiminvaghani) reported@AWSSupport @AWSSupport Day 7.Production still down, Case still unresolved. Yesterday you said it was "forwarded internally for review" that's the third different phrasing for the same non-answer. I'm not asking for updates anymore. I'm asking: who owns this case, and when will it be fixed?
-
mubs (@xmubsx) reported@AWSSupport MFA team is in-house team or outsourced. This is not acceptable. It has been 3 months. In June '26 this issue started. If the MFA device or app is out of sync. How is it my problem. This is aws issue. How can you guys ignore a genuine issue like this. All articles are useless.
-
EJ Campbell (@ejc3) reported@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.
-
zarrakh (@zarrakh) reported@AWSSupport @awscloud @AWSSupport as I told before, It will be just a correspondence and no solution. I have been getting correspondence since feb 2026 but no refund, despite of your team confirmed that the issue is on your side.#aws
-
Quoc Huy (@q_huy_ngo) reported@Cloudflare @awscloud mine transacted with Cloudflare about 700M times because of a broken DO alarm 🥲 no users, just a dev app, then a $655.83 bill. i fixed it and opened case 02252354 a month ago. still no billing decision and now i’m downgraded. can someone pls help? i really can’t afford this
-
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.
-
jayesh somani (@Jayesh_Somani_) reportedIt's Sunday 11:30 AM. Production is down. Users can't login. My phone won't stop buzzing. Every tool I tried to use to fix it — blocked. AWS had quietly quarantined our only admin IAM user. Here's how I restored production in 2 hours without AWS Support @awscloud 🧵
-
Art Vandelay (@john15489) reported@amazon @awscloud @nvidia I need an actual customer service phone number so I can actually speak to a ******* rep regarding 4 orders now. Your email help system is broken.
-
Webdesign29 Création de sites internet Brest⛓️🕸️ (@Webdesign29B) reported@AWSSupport There is no way to get a call back I have tried many different ways. And it always show's this issue
-
Arian van Putten (@ProgrammerDude) reported@QuinnyPig @awscloud Are they gonna fix not being able to have to accounts logged in in two different tabs?
-
Corey Quinn (@QuinnyPig) reported@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.
-
Drama Memes (@drama_meme) reported@cgeorgiaw @AnthropicAI @awscloud Someone tell me why this is a hard problem and you can’t just do $ diff normal.genome sick.genome ? I am guessing it’s a statistical thing, but, if it were random then how would you figure out what’s different??
-
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...
-
Onkar Deshpande (@i_am_onkar) reported@bilal_akh @awscloud what were potential issues? account compromised? keys exposed? last time this happened for me was when some keys got leaked and someone emptied my startup credits -this was 8years ago tho
-
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
-
Brian Porter (@kbporter) reported@amazon @awscloud @AmazonHelp why do I have to continually contact you on social media for issues with your service? Why is your customer service online “help” so bad? $5 credits for delayed orders for a service we pay for is horrible!
-
ゆーー𓂀🦊京のそちこち(暑いので液化した🫠) (@Hikari_644) reported@ishanxtwt Simply DNS server problem never take down an entire website. Except, like amazon AWS, are using domain and dynamic name resolve to working correctly between multiple servers and services.
-
Himanshu Singh (@hsnice16) reportedBeen 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.
-
MrWho (@Mrwho23) reported@AWSSupport I create a case for your support and till now waiting for the reply My whole system and company is waiting for your support, but you are so slow
-
Webdesign29 Création de sites internet Brest⛓️🕸️ (@Webdesign29B) reported@AWSSupport No it errors server side it doesn't work.
-
Matthew (@OneShotCaller) reported@ZZiata15569 @awscloud I have billing and budget alerts set up with AWS already. Main problem with a lot of tools I’ve used is too much noise in the alerts vs AWS option. Still, I think every AWS customer gets at least 1 surprise lol… part of initiation (onboarding?)
-
Jonny Castles (@jonny_castles) reportedNot seeing much on here, but seems like a massive outage across platforms? Looks like all AWS linked? @awscloud