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 (82%)
- Sign in (9%)
- Errors (9%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Township of Evan
|
Website Down | 5 days ago |
|
New York City
|
Website Down | 7 days ago |
 Ciudad Jardín
|
Website Down | 1 month ago |
 Kyiv
|
Sign in | 2 months ago |
 Chennai
|
Website Down | 2 months ago |
|
Point Pleasant Beach
|
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:
-
🔥 PHOENIXX🔥 (@AIPulse0) reportedAMAZON AWS PAYS $127K/MO FOR CLOUD COMPUTING. SERGEY BOUGHT CHEAP SERVER RACK + CLAUDE AI. MAKES $318K Pause at 0:11 — rack with 40+ servers. Every indicator glows green. This is local computing. Zero latency. Zero cloud bills. Sergey, 35, Ukraine. Was AWS architect, $7,200/month. Understands: companies pay Amazon millions, but they can do same calculations locally. Bought used server rack for $4,800. Installed Claude AI for local processing. 78 companies pay $4,077/month each instead of $12K on AWS. Amazon offered $4,200,000. Sergey said: "You profit from dependency. I profit from freedom." Why — in video.
-
Silksteele (@silksteele) reported@adamKDean @awscloud Pshhhh! That's a rounding error against your consulting fees and contract work. I'm surprised you even noticed.
-
golden gate bridge (@_ggbridge) reported@litteralyme0 this happens to me everytime Amazon AWS has an outage
-
Certified AI Dev (@MisterPrashant) reportedThis solution to this problem is AI traffic monetization. If you are an owner of a platform that provides some valuable data, you can put the data behind a paywall for the AI traffic by charging the bot fraction of a penny for using their content. x402 Payment Required protocol tells the bot that the content requires payment and the bot settles the transaction quickly on a stable coin at which point the content becomes accessible. This way,people running their search bots does not require subscription to 10 different services and can easily access data from anywhere at a very minimal cost and the owners of the sites also win as the traffic count to their paywalled site will generate income. This is not a concept. The framework to build this is already available in @awscloud today.
-
Steven Coburn (@pcgamer11) reported@PlayStation We can't play the open beta rn because PSN IS DOWN. Yes, it uses/runs on @awscloud but you could at least ACKNOWLEDGE the issue!!!
-
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
-
Har (@duckboy1909) reported@awscloud fix your Alexa servers and fix your Bluetooth on app and devices! #alexadown #alexa #amazon
-
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.
-
M (@mdw864) reported@AWSSupport Either that or ask me to login, which I keep telling you I cannot login. It has nothing to do with 2FA. That is not the issue.
-
Fikri Firdaus (@fikrfird) reported@awscloud This really isn’t something to joke about. A false billing alert at this scale can cause genuine panic and even serious health consequences. Some users may have rotated credentials, shut down workloads, or deleted services because they feared their accounts had been compromised.
-
PositiveVibes (@KPTheFighter) reported@AWSSupport @AWS @awscloud I still did not receive any email communication which I was expecting as soon as you guys noticed the issue. Today I almost lost my life due to panic. My hands were shaking as I was told. I still can’t believe I went through this. First email - insane actual bill about Dashboard shows the same amount After panic attack, I see a note on your support page, but what would one go to your support page ? Shouldn’t it be on your billing console page ? Again, my issue is not about your mistake, it’s about how you handled the situation. And you didn’t do anything!! Not even one email to the users!! Sad and shocked at the same time!! I can’t forget what I went through today morning. 😞
-
barney (@Southclaws) reported@jonny_castles @awscloud I am seeing this too, ECR and S3 in eu-west-1, lots of "service unavailable" errors
-
Nil (@slowalgorithm) reported@awscloud The LEAST you can do is to give some compensation. This mistake caused operational issues for several companies across the globe.
-
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.
-
Aaryan Bansal (@NotUnHackable) reported@awscloud that issue was happening since yesterday dude. why tf did it take so much time?
-
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
-
M (@mdw864) reported@AWSSupport Tells me to login when I keep telling you I cannot login because I don’t have the capability to do so.
-
kyun anon (Gobhi ka fool ) (@anondis1122) reported@AWSSupport @ashu_sharma17 Yeah. Why tf not send an email.. that there is an issue. I have a medical condition. It put my life in danger
-
mail box (@mailbox28564784) reported@amazonIN @amazon @awscloud I am extremely disappointed with Amazon's customer service. Despite returning the product, I have neither received my ₹1,400 refund nor a replacement. Repeated follow-ups and social media complaints have not resolved my issue.l
-
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?
-
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?
-
David G (@MohandesDavid) reported@thewebbie @awscloud Rounding error, obviously....
-
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.
-
Adam Peterson (@_adam_here_) reportedis @AWSSupport down?
-
Ajith (@iamarulajith) reported@F1 @awscloud Actually surprised to see the good start by Max. I thought he would bog down again but not this time.
-
Edward Donner (@edwarddonner) reported@darkosubotica @awscloud @AWSSupport Thanks Darko. I'm keen to be involved. I'm aware there are challenges. A billing bug shouldn't cause a global outage or delete backups. I believe these are solvable. I don't want the possibility of financial ruin from a mistake or hack. Will DM.
-
Shaaaaaaaaan (@AryavartKSamrat) reported@Sahilvyas29 @JeffBezos @AWSSupport Its a amazon glitch man. Read about it.
-
* (@BunnnyRAM18) reported@amazonIN @awscloud The same issue happened twice for these product
-
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
-
AntDracula (@ant_dracula) reported@kankerhoerrrrrr @marcelocantos @awscloud And you had no response for "what's the alternative to shutting down services, just pay the bill?" Maybe you really are an AI bot instead of a retard.