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 (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 |
|---|---|---|
|
|
Website Down | 3 days ago |
|
|
Website Down | 6 days ago |
|
|
Website Down | 1 month ago |
|
|
Sign in | 2 months ago |
|
|
Website Down | 2 months ago |
|
|
Website Down | 2 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:
-
Ben Newton ベン (@BenENewton) reported@awscloud Somewhere there's an IT guy lying on the ground next to his desk after opening the page with this error on it.
-
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.
-
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. 😞
-
devastatindave.eth (@NftCelestials) reported@awscloud totally avoidable error caused by reliance on unskilled h1b scabs ya'll will learn eventually
-
Naren Bao 包娜仁 | Physical AI Agents (@NarenBao) reported@awscloud please fix your Cost Explorer bug asap!
-
GiveHateAChance (@HelpingHate) reported@awscloud It's cute how the ***** indians who caused all of this are never at fault and how you dismiss what a huge error this was with an emoji.
-
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.
-
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
-
🔥 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.
-
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!!!
-
Koray Yersel (@korayyersel) reported@AWSSupport My balance went down to zero. Time to the delete the aws account.
-
₽ⱤΞΞ₮Ⱨ△M ₭Ɏ△И△M (@pkyanam) reported@yellow_fellowz @awscloud @emm3122 AWS replied to me saying they’re aware of this issue
-
Abdul Rauf (@armujahid) reported@miserer3_mei @AWSSupport It's a known issue that they are already checking
-
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 happen more frequently. Emails from mturk-noreply havent worked in a long time,any updates on this situation @amazonmturk
-
golden gate bridge (@_ggbridge) reported@litteralyme0 this happens to me everytime Amazon AWS has an outage
-
Jeff B. Vockrodt (@JeffBVockrodt) reported@AWSSupport You should send follow up emails alerting all your customers to this issue. I woke up to a $719 million billing estimate which although absurd conjures a potential nightmare of getting it worked out
-
Jan Jezek (@jbodl) reported@awscloud First you sent alerts that the account was over budget by 6-figure numbers. When the user logged in, the billing console confirmed the same. No banner there was an issue, no followup email, nothing. Just wannabe funny jokes on X. Seriously, AWS?
-
Gerzson (@Gerzsononline) reported@slap__tjips @awscloud Gosh ai haters are so ******* dumb they just assume and blame it on ai for a funny error that didn’t result in any wrong
-
Aaron Spiel 📣 (@SpielAaron) reported@AWSSupport It's not estimated. To quote the horrific emails you're sending people: "The month actual cost associated with this...". And yes, maybe it's easier to laugh and realise it's an error when you're potentially being billed $1,000,000,000. But when it's $80K, it feels scarily real.
-
Corey Quinn (@QuinnyPig) reportedI want to hear the inside story of the largest @awscloud project. Not bill run, nor S3. I’m talking about what it took to fix all the hardcoded “jeff@“ userID stuff when @ajassy rose. Not kidding: it woulda been orders of magnitude easier for him to change his name to “Jeff.”
-
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
-
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.
-
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.
-
barney (@Southclaws) reported@jonny_castles @awscloud I am seeing this too, ECR and S3 in eu-west-1, lots of "service unavailable" errors
-
Meo Meo (@CastleEL88) reported@awscloud Focus on AI features instead of server maintenance. .
-
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).
-
Gabe Fletcher (@gabefletcher) reported@marcelocantos @awscloud bro... touch some ******* grass. OF COURSE IT WAS AN ERROR. WHO REALLY THINKS THEY LOOK AT THEIR AWS BILL FOR A TRILLION DOLLARS AND SAYS "OH THATS DEFINITELY REAL" stop. go **** off to some VPS's or some ****.
-
Aramis Official (@AramisToken) reported@NoaSanderskyo7 @F1 @awscloud He was slow af, actually
-
Shaaaaaaaaan (@AryavartKSamrat) reported@Sahilvyas29 @JeffBezos @AWSSupport Its a amazon glitch man. Read about it.
-
Adam Peterson (@_adam_here_) reported@AWSSupport Even the AWS health page was down. Total AWS system downtime for 12-13 minutes. AWS appears back now.