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 (80%)
- Errors (20%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Website Down | 13 hours ago |
|
|
Errors | 12 days ago |
|
|
Website Down | 27 days ago |
|
|
Website Down | 30 days ago |
|
|
Website Down | 2 months ago |
|
|
Sign in | 3 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:
-
Adel Bucetta (@adelbucetta) reported@tushaarmehtaa @OpenAIDevs @awscloud back to school is just a Band-Aid on a larger issue: how do we make building with ai accessible for the next 50 million people, not just 50?
-
Matt Lea (@schematical) reported@PhilipAnderse @awscloud @amazon What's the problem? I know a thing or two about AWS.
-
lak-alak (@baricadelane) reported@IanCarrollShow @BacklotOPS @NickJFreitas They must think we are stupid Tyler Robinson decoys all over the place d captured on camera all doing their part for 1990s pixalated images produced and sold as 4k in 2026 lmao. Why did Amazon aws services shut down 9/10 - 9/25? Who owns discord?
-
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
-
Siya (@reze_xqc) reported@AWSSupport Case 178653274100402 opened 3 days ago, no response. Can't sign in to AWS Builder ID, email locked to unknown sign-in method, blocking access to AWS Academy courses. Need help.
-
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!
-
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
-
Graham Christensen (@grhmc) reported@apparentorder @QuinnyPig @awscloud I'm sure they'll fix it after they're done at the discotheque
-
Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported@meaningoflights @jpschroeder @awscloud what issue do you have with that?
-
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.
-
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??
-
GIrls In Technology! (@francescaViking) reported@awscloud @amazonmturk are shuttering services barely months after announcing maintenance mode, giving barely a month now and leaving requesters and workers in the lurch. Amazon demonstrates again why it's terrible for businesses and users.
-
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.
-
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?)
-
niknak (@niknak) reported@duckdb @ducklabs_com @awscloud Congrats on the check fellas but this is terrible news
-
ゆーー𓂀🦊京のそちこち(暑いので液化した🫠) (@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.
-
Adel Bucetta (@adelbucetta) reported@Deeen_Codes @awscloud @devpost the real unlock here isn't just solving the hackathon prompt but figuring out what problems to automate first
-
WPBeginner (@wpbeginner) reportedYou have spent months building your WordPress site. What happens the day it suddenly goes offline? 😱 It happens all the time. We have heard several scary stories. A plugin conflict, a bad update, or a security breach can wipe out your complete website without any warning. The scary part is that most site owners assume their host has them fully covered, right up until they actually need to restore. We have tested countless backup tools on our own projects, so we put together the exact methods we trust to keep a site safe. Here is what you will learn: ✅ Pick the Right Method: Compare backup plugins, host backups, and manual cPanel or FTP so you know which fits your skill level. ✅ Back Up the Full Site: Save your database, themes, plugins, and uploads together so you can restore everything, not just your posts. ✅ Automate It With @DuplicatorWP: Schedule daily or weekly backups and send them straight to the cloud so you never have to remember. ✅ Store Copies Off Your Server: Keep backups in Google Drive, Dropbox, or Amazon S3 so one server crash never takes your site and its backup at once. ✅ Restore in Minutes: Use a disaster recovery link to bring your site back even when it is completely broken. Ready to protect all that hard work before disaster strikes? Read our complete step-by-step guide from the link in the comments 👇 (Link is in the thread below)
-
Ü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
-
Vera ¤⩊¤ (@VeraSimila) reported@awscloud L+ Ratio Fix Twitch please, nobody wants AI hype beast corpo speak
-
Arian van Putten (@ProgrammerDude) reported@QuinnyPig @awscloud Are they gonna fix logging me out and then redirecting to the root console login? Are they gonna fix having links shareable and login to the right account? **** is such a **** show idk why I even cope
-
Dan Lynch (@danlynch) reported@QuinnyPig @awscloud I need to sign in with LEGO 😎
-
Weaver Labs (@Weaver_Labs) reported@amazon @awscloud @nvidia AI infrastructure is becoming a full-stack problem. GPUs are only one piece now, with networking, compute and data infrastructure all needing to scale together.
-
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.
-
Arian van Putten (@ProgrammerDude) reported@QuinnyPig @awscloud Not randomly redirecting to root console login page if I logged in with IAM identity center
-
TechThought.org (@TechThought_org) reportedAn era ends for human data annotation. @awscloud is shutting down Mechanical Turk after 21 years as LLMs take over micro-tasks, per @techradar. What happens to training baselines when synthetic data completely replaces human feedback? #AI #Automation #AIeconomy techradar .com/pro/aws-is-shutting-down-mechanical-turk-which-let-humans-beat-ai-at-certain-work-tasks
-
Mohammed Nafees (@mnafees) reportedyo @awscloud seems like a broken cert chain from your side
-
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:
-
Sumedh More (@DroidBoyJr) reportedHey @awscloud @AWSSupport im trying Bedrock with root user and getting NOT_AUTHORISED error with 400. Tried support and the ai assistant couldn't find anything. Tried raising ticket, it asked me to upgrade support plan. Plan upgrade failing with error. Going nowhere #SOS
-
Jonny Castles (@jonny_castles) reportedNot seeing much on here, but seems like a massive outage across platforms? Looks like all AWS linked? @awscloud