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 (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 |
|---|---|---|
|
|
Sign in | 2 days ago |
|
|
Website Down | 6 days ago |
|
|
Website Down | 10 days ago |
|
|
Errors | 21 days ago |
|
|
Website Down | 1 month ago |
|
|
Website Down | 1 month 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:
-
Siddartha DevOps (@SiddarthaDevops) reported@AWSSupport link is not working
-
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!
-
Wogan (@WoganMay) reported@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."
-
Chris (@Mcatbeast) reported@AWSSupport Apologies for the earlier frustration. Turns out it was an issue from our end! My user was accidentally deleted.
-
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.
-
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
-
PolyPup (@PolyPup) reportedI think I have a problem. - 3 @ChatGPT subscriptions - 2 @AnthropicAI subscriptions - $8,200 @awscloud bill coming this month I have so many protocols built, ready for deployment. Really cool innovative, revenue generating projects but I'm hesitant to launch on anything. Maybe someday.
-
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
-
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.
-
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.
-
Arick Goomanovsky (@g00manoid) reported@awscloud It's worse than technical debt in one way - sprawl compounds through the connections, not just the count. Ten agents with no shared context or ownership isn't ten problems, it's every pair of them. The fix is a connective layer that makes them a network instead of scattered debt.
-
Hannan (@truehannan) reported@AWSSupport Why AWS console is not opening? Its soo much slow even my internet and everything is fine. I used VPN too but nothing worked
-
Zenwatts πΊπΈ (@BullCall101) reported@awscloud Not my problem. Maybe sell a yacht or two and fix it yourself.
-
Samrat Singh (Sam) (@isamrats) reported@KahlonGurshaan @Rushike32313211 Yes its down , but no official confirmation posted by @awscloud yet
-
Krishna.Ki.Shor (KK) (@kkbava) reported@AmazonHelp You are still giving me work!π‘ Why not look inwards and check if order was indeed delivered? And tell the software geeks and nerds that there is a problem with conflicting messages? Learn from failures guys! That's what I learnt from @awscloud
-
Jaimin Vaghani (@jaiminvaghani) reported@AWSSupport 5+ days, Case 178738643800497. Production down, customers impacted. Same scripted answer daily: no ETA, no updates, just "check back in a couple of hours." This needs real escalation. Please have someone with authority look at this.
-
π΅πππ£ππ πΏππππ β‘οΈ (@FaizelPatel143) reportedβAI will solve real problems, for the continent.β #AWSSummit2026 @awscloud
-
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.
-
niknak (@niknak) reported@duckdb @ducklabs_com @awscloud Congrats on the check fellas but this is terrible news
-
Arian van Putten (@ProgrammerDude) reported@QuinnyPig @awscloud Are they gonna fix people needing to know what region their orgs IAM identity center is deployed in order to set up cli login? (How the heck would an employee know this??)
-
Adam π€ (@AdamMolnarHF) reported@cgeorgiaw @AnthropicAI @awscloud ooh, I've actually been working on an autoresearch space for a different problem (math) using Kimi k3 + inference providers, I could try forking and seeing if I can reshape the structure around this with this data + build it fully in the open!
-
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.
-
Jared Cassidy (@depach) reported@grhmc @QuinnyPig @awscloud Not fixed on mine I login every day π₯² did you have to set anything?
-
Nandkishor (@devops_nk) reportedInfosys DevOps Engineer L2 Round (Offline) My friend got these questions in the L2 interview: 1. What does the top command show in Linux, and what does load average represent? 2. What is the difference between Amazon S3 and EBS? 3. What is Amazon EC2, and can we use a custom OS/image with an EC2 instance? 4. What is the difference between self-managed PostgreSQL and Amazon RDS for PostgreSQL? 5. What are Primary Keys and Foreign Keys, and why are they used? 6. Can S3 data be automatically deleted based on a policy? How do S3 Lifecycle Policies work? 7. How would you install Nginx or Apache on Ubuntu? 8. What is sudo, and why do we use it in Linux? 9. What is the difference between Prometheus and Grafana? 10. How does Prometheus collect/scrape metrics? 11. How do you manage Docker images, containers, and running processes from the CLI? 12. Where is a Bearer Token normally passed in an HTTP request? 13. Do you use any third-party monitoring tools in your production environment? If yes, which one? 14. How would you design a standardized Jenkins pipeline for multiple teams? 15. How would you create reusable Jenkins templates and shared libraries? 16. How would you troubleshoot an intermittently failing Jenkins pipeline? 17. How would you integrate Maven into a CI/CD pipeline? 18. How would you manage builds involving Node.js, Python, or Go? 19. How would you troubleshoot a failed production deployment from Jenkins? 20. How would you investigate a Kubernetes workload with high CPU or memory usage? 21. How would you use cloud monitoring and logs to isolate an infrastructure issue? Save this if you're preparing for a DevOps Engineer interview.
-
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:
-
Kailash Tulsi Gajra (@kailashgajara) reportedIs @awscloud down right now? #AWSDownAgain #AwsDown
-
Γmit Kaan Usta (@umitkaanusta) reported@AWSSupport I keep getting errors across the AWS Console where components or resource lists fail to load, showing messages like βAn error occurred calling the API: describeAddresses.β Reloading sometimes fixes it temporarily. can you help? It's mostly on EC2 related stuff. us-east-1
-
Brandon S (@BSaarX) reported@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
-
absk (@abskwdkr) reportedMy ec2 ssh logs in too slow and lags @AWSSupport
-
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 !!!!!!