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 | 4 days ago |
 Township of Evan
|
Website Down | 19 days ago |
|
New York City
|
Website Down | 21 days ago |
 Ciudad Jardín
|
Website Down | 2 months 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:
-
Guilherme Lage (@ItsEasypop) reportedAnother OG goes down. I remember people calling Storj the next Amazon S3 back in 2018
-
billy (@Billy17979063) reported@fortniteleaksmy It’s up for some down for some @awscloud ******* decides to shut down not just PlayStation but other platforms too
-
Har (@duckboy1909) reported@awscloud fix your Alexa servers and fix your Bluetooth on app and devices! #alexadown #alexa #amazon
-
Mohammed Nafees (@mnafees) reportedyo @awscloud seems like a broken cert chain from your side
-
Ondřej Flídr (@snipercze) reportedHello @AWSSupport, is there any problem with EBS subsystem in us-east-2 (Ohio region)? Cannot resize volume (ending with internal error, same for console and CloudFormation), new volume is created but stuck in "Attaching" to the EC2. Thanks for check
-
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)
-
SwarmOne.ai (@swarmoneai) reportedOpenAI just unveiled Jalapeño - their first custom inference chip with Broadcom. "Substantially better performance per watt." Interesting. But a chip doesn't fix a misconfigured serving stack. Custom silicon with default batching, naive routing, and untuned KV-cache management is still burning money. SwarmOptimizer doesn't care what chip you run. It tunes the deployment layer - batching, caching, routing, concurrency - where most of the waste actually lives. The silicon is one layer. The optimization is another. Now on @awscloud
-
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?)
-
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.
-
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.
-
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
-
mail box (@mailbox28564784) reported@amazonIN @amazon @awscloud But in my personal experience, this response has never led to a real solution. They keep asking for the same details again and again, yet my issue remains unresolved. My ₹1,400 refund is still pending, and I have neither received a replacement nor-2
-
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.
-
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
-
M (@mdw864) reported@AWSSupport Five months of broken links & blocked support channels is unacceptable. You have more cut off core business services because you have refused to provide a person with disabilities a way to tell you that you are over billing me. Escalate to a senior rep to fix this before 9am cst
-
Eszter Morvay (@eszter_morvay) reported@AWSSupport Also - apologies for the DM issues, i just changed my settings, so DMs should work now
-
Yuyun Francis (@FrancisYuyun) reported@AWSSupport case ID (178590975600210) "account activation blocked 2+ weeks by Error 880104, case escalated internally Aug 5, no update since."
-
matyas.dev (@DevMatyas28516) reported@AWSSupport Still nothing happened after a week, after I sent your X account our issues numbers.
-
Jim Osman (@EdgeCGroup) reported@awscloud Real innovation starts with people solving real problems.
-
Prateek Gupta (@p_valuee) reportedAWS suspended my account for billing. I have zero due invoices and zero past-due invoices. Their own Amazon Q agent confirmed it in writing. P1 case 178635853400575, day 3, production still down. @AWSSupport what is the actual reason?
-
Abdulkadir | Cybersecurity (@cyber_razz) reportedClarityCheck markets itself as a tool to detect catfishing. To verify identities. To keep you safe from liars online. Here's how it works. You upload someone's photo. ClarityCheck runs it through their reverse image search. Finds their dating profile. Their social media. Wherever that face appears. Seems solid. Except ClarityCheck just leaked 9 million photos sitting in an unsecured Amazon S3 bucket. 450 gigabytes of faces. Stored in folders labeled "faces" and "profiles." The photos came from people uploading images of strangers. Dating app screenshots. Private social accounts. Scanned prints. Photos of children. Most of these people never uploaded anything to ClarityCheck. They just got identified by someone else trying to figure out who they were. Then their face got indexed. Stored. And left wide open. For several months. The URL to access it was embedded in ClarityCheck's own website source code. The company's response: this was "temporary storage" and an "ordinary member of the public" would not have found it. An ordinary member of the public with the URL from their own website. Which is not temporary storage. That's just a server. And it wasn't invisible. You'd need 30 seconds and a basic understanding of how websites work. Now ClarityCheck says the data is "secured." A service built to prevent identity fraud just exposed millions of identities. The tool designed to catch people lying about who they are just showed everyone's actual face to anyone listening. The irony isn't subtle. It's a design flaw pretending to be an accident.
-
Chintan Shah (@chintan86) reported@AWSSupport @awscloud Dues cleared, reinstatement requested — still waiting with no movement. My production workloads are down and every hour is costing us. Can someone please prioritise this? Case ID ready to share over DM.
-
Ü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
-
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 happening more frequently. Emails from mturk-noreply havent worked in a long time so any updates on this situation?
-
krrawn (@krrawn) reportedI was wondering why @awscloud support was slow the other day
-
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.
-
sof ࿔˚⋆ (@sophia_ray_17) reported@awscloud until the cloud has a power outage and i can't get into my car
-
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.
-
Ayush Awasthi (@Ayush_awa) reported@AWSSupport Its the third day today. The only mail I received from aws was all about “We are getting someone to investigate this” Since then I havent received any update. My only issue is that these things are time sensitive and you cant just take days after days with no real status updates
-
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.