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 | 16 days ago |
|
New York City
|
Website Down | 19 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:
-
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 happen more frequently. Emails from mturk-noreply havent worked in a long time,any updates on this situation @amazonmturk
-
Eszter Morvay (@eszter_morvay) reported@AWSSupport Also - apologies for the DM issues, i just changed my settings, so DMs should work now
-
Ashmit Dutta (@ashmit105) reported@awscloud keeps charging me $60 a month. I can’t login to my account due to a deprecated email. Making support tickets goes nowhere. Anyone got advice on what to do?
-
ゆーー𓂀🦊京のそちこち(暑いので液化した🫠) (@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.
-
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.
-
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
-
Siya (@reze_xqc) reported@AWSSupport @AWSSupport @awscloud Case 178653274100402, 4 days old. Got a copy-paste "noted for awareness" reply, no actual fix. Still locked out of AWS Builder ID, still can't access AWS Academy courses. This is blocking coursework. Fix it.
-
Ashutosh Dubey (@_virusbug_) reported@AWSSupport I’ve already emailed the AWS Receivables team but haven’t received a reply yet, it’s been 3 days now. The support engineer only advised me to contact them about this issue.
-
GettingMyGlitchOff (@GettingMyGlitch) reported@AWSSupport Yeah its just getting automated responses to everyone saying "Your account will not be re-opened. We regret that we have not been able to address your concerns to your satisfaction." so can you send the mturk team a message to review the error since its more then just me its
-
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)
-
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
-
Pixi Dust (@Bethco2257) reported@FmrRepMTG @amazon @awscloud walk into any Amazon office building at Seattle HQ and South Lake Union Amazon Seattle offices and instantly you can see with your own eyes… nearly 80% of staff are HB1 visa holders!!!! So yes, we have a big problem.
-
Ritesh Roushan (@devXritesh) reportedA good architecture starts by separating document storage, signing, identity verification, and notifications into independent services. 1. API Gateway All requests (upload, sign, download, share) pass through the API Gateway. It handles authentication, rate limiting, request validation, and routing. 2. Document Service Contracts are uploaded directly to object storage (Amazon S3/GCS/Azure Blob). Metadata such as owner, participants, document status, and version history is stored in PostgreSQL. Large files never pass through application servers. 3. Identity Verification Service Before signing, users verify their identity using email OTP, SMS OTP, OAuth, or KYC providers depending on compliance requirements. A verified identity token is issued before allowing signatures. 4. Signing Service Each signature request creates an immutable signing event. Documents are locked while applying a signature to prevent conflicts when multiple users sign simultaneously. Optimistic locking or version numbers help resolve concurrent updates. 5. Audit Log Service Every action upload, view, download, sign, reject, revoke is published to Kafka. Events are stored in an append-only audit database with timestamps, signer identity, IP address, and device information, creating a tamper-resistant audit trail. 6. Notification Service Kafka events trigger email, SMS, and push notifications asynchronously so users are notified instantly without slowing down API responses. 7. Security • Encrypt files at rest (AES-256) • TLS for data in transit • Short-lived signed URLs for downloads • RBAC for document access • Hash every signed document (SHA-256) to detect tampering • Store digital certificates securely using a KMS/HSM 8. Scalability Deploy services independently behind load balancers. Use Redis for caching document metadata and sessions. Object storage handles millions of documents, while Kafka decouples services and absorbs traffic spikes. Read replicas improve download performance, and multi-region replication ensures disaster recovery. This architecture provides secure storage, concurrent signing, legal compliance, high availability, and scales to millions of contracts worldwide.
-
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.
-
Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported@Cloudflare @awscloud Fix human verification
-
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.
-
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.
-
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
-
zarrakh (@zarrakh) reported@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
-
Harshil Mathur (@harshilmathur) reported4 billion payments. 3 trillion data points. One model trained on all of it. Meet @Razorpay Vulcan - India’s first transformer-based AI foundation model for payments. Built, trained and hosted in India, in partnership with @nvidia and @awscloud. Until now, every payments problem was solved separately: routing, fraud, risk, personalisation and more. We asked: What if one model could understand how money moves? And like LLMs are trained on text to understand language, Vulcan is trained on payments to understand how money moves. Already running in beta across 51,000+ businesses, Vulcan is delivering: - 8–10% improvement in payment success rates - the ultimate measure of whether a payment simply works. - 8x more international card fraud detected. - 5x more fraudulent or disputed transactions identified. - 1–2 lakh more purchases completed every month through better checkout personalisation. And we’re just getting started. The best part? Every payment Vulcan sees makes the next one smarter. We’ve spent years building the infrastructure that moves money for India. Now, we’re building the intelligence that understands and improves it. 🔥
-
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?)
-
masaki (@silenthill_x) reported@AWSSupport Could someone please take a look at my support case? I opened a case 6 days ago because my RDS Reserved Instance is showing "Payment failed", but the case is still unassigned. The automated AWS Support response confirmed that my account is in good standing, my payment method is valid, and my invoices are fully paid. It also indicated that this appears to be a reservation processing issue rather than a payment issue. I've tried both Phone and Chat but haven't been able to reach an associate. Could you please help me get this case assigned? I can provide the Case ID via DM.
-
Payal (@payal_codes) reportedDay 1 : "How to Scale an App to 10 Million Users on AWS" If I have to design a system for 10 million users, I won't build everything on Day 1 because it will add unnecessary complexity and cost. I'll start simple with one application server and one database. As traffic grows, if the server starts reaching its CPU, memory, or storage limits, I'll first scale vertically by moving to a bigger instance. Once that is not enough, I'll separate the backend and database so both can scale independently. To avoid a single point of failure, I'll deploy the application across multiple Availability Zones and put a Load Balancer in front so if one server or AZ goes down, traffic is automatically routed to healthy servers. As the number of users keeps increasing, I'll make my application stateless by storing sessions in Redis. This allows me to add multiple application servers behind the Load Balancer and scale horizontally. If my database starts getting overloaded with reads, I'll use Redis to cache frequently accessed data and add read replicas to distribute read traffic. For static assets like images, CSS, and JavaScript, I'll store them in Amazon S3 and serve them through CloudFront so requests don't keep hitting my application servers. If traffic suddenly spikes during sales or events, I'll enable Auto Scaling with CloudWatch metrics so AWS automatically adds or removes servers based on demand. As the application becomes larger, I'll split the monolith into microservices. This allows each service, like authentication, payments, or notifications, to scale independently instead of scaling the entire application. If the database becomes the bottleneck, especially for write operations, I'll use sharding or federation depending on the data and business requirements. Finally, when users are spread across the world, I'll deploy the application in multiple AWS Regions to reduce latency and improve availability. My approach is always the same: find the bottleneck, solve that bottleneck, and only introduce more complexity when the current architecture can no longer handle the traffic.
-
Hagop Chemedikian (@hagop17) reported@AWSSupport Account blocked — "not recognized as a valid account." Console login works, all resource creation fails. 10+ year old account, dormant for years, just resumed for a personal project. Three cases open, no response. Can someone look?
-
ShenYubao (@ssybb1988) reported@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
-
🦋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.
-
CaptainAmericaTex (@CaptAmericaTx) reported@LayoffAI During the last 12 months Amazon AWS had outages directly caused by initiatives from the AI group (with associated revenue impact). No surprise they are down sizing the snake oil sales men group.
-
AntDracula (@ant_dracula) reported@BohemiaTech @awscloud Google just randomly shuts down services for no clear reason. That’s why they’re not trusted
-
Rohit Dhawan (@rohitdhawan26) reported@AWSSupport @awscloud I send a DM on 17th july with same issue but no one responded to that.
-
Mon (@mon73x) reported@asimrazax @AWSSupport I have the same problem. Did you fix it?