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 | 1 day ago |
 Township of Evan
|
Website Down | 16 days ago |
|
New York City
|
Website Down | 18 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:
-
Corey Quinn (@QuinnyPig) reportedKinda funny that nobody's even making observations like this about @awscloud, if you want to go a level deeper down the irrelevance well.
-
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.
-
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)
-
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
-
Abhijit Tripathy (@AbhijitTripat13) reported@awscloud @awscloud still no response. You guys are so slow
-
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 !!!!!!
-
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. @AWSSupport
-
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.
-
Jacklyn Taylor (@Ronindrake2) reported@awscloud hey, got a simple question When your moderation refuses to post a review of a book, can you do everyone a favor and instead of saying "one of these things" Say "here is the specific part that violates our guidelines. Pls fix it" It would be, so much more helpful
-
Sudeep (@sudee1285) reportedI need assistance to access existing APN account...it's getting error.. please help me. @awscloud
-
mark seery (@140ismymax) reportedPeter DeSantis talking at #agenticaisummit There will NOT be one AI chip type. If multiple AI chips take multiple years to bring to market, you have to be making assumptions about model requirements in that time frame. It's a systems problem, including the network. Constraint drives innovation. Future is bright and built together. Peter DeSantis SVP, Foundational AI Models, Custom Silicon, Quantum Computing, Amazon @awscloud @amazon @BerkeleyRDI
-
Ignacio Cassinelli (@igncass) reported@awscloud What a terrible response
-
barney (@Southclaws) reported@jonny_castles @awscloud I am seeing this too, ECR and S3 in eu-west-1, lots of "service unavailable" errors
-
metis (@metis00001) reported@AWSSupport Looks like it has been resolved. But it definitely took like 5 days to resolve a payment configuration issue! Thanks for reaching out.
-
Ü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
-
DeeDee Armstrong (@deedeeafton) reported@t1097s @larunachalam @awscloud Tyler, are you an AWS actual customer, or just someone who thinks real people should “chill out” when a vendor causes actual business trouble and then jokes about it?
-
Robert Culver (@senorculver) reported@awscloud Wow, that’s it, no explanation? No, and for your trouble, and extra work and panic, a free month of service or anything. Just our bad, see you next month?
-
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
-
banhchung (@banhchugxanh) reported@POTATOCHEAPGAM1 @trythreews @awscloud i'm so down for cloud gaming, but 5gb internet feels like a stretch
-
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.
-
🦋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.
-
billy (@Billy17979063) reported@fortniteleaksmy It’s up for some down for some @awscloud ******* decides to shut down not just PlayStation but other platforms too
-
Nil (@slowalgorithm) reported@awscloud How are you planning to compensate all your customers who panicked and started deleting resources since the email was legit and there was not a second email notifying of the issue. Your support bot itself claimed the expenses were legit.
-
✨Neil Blumenthal (@MrKryptonBTC) reported@AWSSupport So you guys wont fix my issue anymore? Ghosting me? 7days gone? Dont say weekend or bla bla. Stop wasting people's time
-
Maurizio Santamicone (@santamm) reported@awscloud And while you fix it, you can credit us for those amounts.
-
DeeDee Armstrong (@deedeeafton) reported@Gozieuk @awscloud You felt they were transparent? I got the anomaly detection email from AWS last night. Dashboard had an outrageous $$ number. Spun up devs to find out problem. And- then AWS posted a joke here on X, and still no email as a follow up to their first one. Doesn’t seem transparent
-
Shobhit Shrivastava (@shri_shobhit) reported@adamr_1776 I left Amazon AWS around 2019. From what I recall it was something like issues dot Amazon dot com
-
Mr Sage (@GreatSage_0x) reportedCustos makes verdicts on AI agent transactions. Problem: it had no memory. Every decision started from zero. Meet Anamnesis — I gave it a memory layer using CockroachDB. Built for the @CockroachDB x @awscloud Hackathon
-
Siddartha DevOps (@SiddarthaDevops) reported@AWSSupport link is not working
-
Carlos DP 🤖🇺🇸 (@carlosdponx) reported@MarwaEldiwiny They’re not hiding it’s a G1, it’s obviously a G1 and they don’t lie if asked. I don’t advertise explicitly my robots are built on G1 either, because it’s a distraction when marketing like this. The end user doesn’t care. It’s like if you sold a SaaS product and mentioned the servers run on Amazon AWS, it’s irrelevant to the user. Their tweets are marketing posts, not technical reports. Also idk what you mean by the G1 “having a lot of issues”. It’s the most reliable and mature humanoid platform you can actually buy today (and we have no data on reliability of closed platforms).