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 (80%)
- Sign in (10%)
- Errors (10%)
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 | 7 days ago |
|
New York City
|
Website Down | 10 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:
-
Keith Townsend (@CTOAdvisor) reportedI spent over $120 in @awscloud so far this month. Most of it has been on GPU instances and Xeon 6. This is the most I've spent since I've had a long-running VM as a web app server a few years ago.
-
Joy | 🔥 (@JoyKingdomx) reportedAs we all know, cloud outages are not a new topic here. But what is changed is how many products now depend on the same infrastructure. A few years ago, an AWS outage mostly affected AWS customers. Where today one infrastructure issue can ripple across AI apps, APIs, developer tools, streaming platforms and payment services. That is the downside of concentration. We have seen @awscloud outages impact millions. We have also seen @OpenAI outages pause production apps because entire inference pipelines depended on a single provider. It is not the outage that matters - it is the dependency behind it. That is the reason why decentralized compute makes sense. Instead of relying on a single cloud or region, @ionet distributes compute across a global network of GPUs in 138+ countries. No infrastructure is immune to failure, the goal is to ensure one failure does not become everyone's failure.
-
CaptainAmericaTex (@CaptAmericaTx) reported@LayoffAI During the last 12 months Amazon AWS had outages directly caused by initiatives from the AI group (with associated revenue impact). No surprise they are down sizing the snake oil sales men group.
-
JJ Ferman (@jjferman) reported@awscloud the fix: if bill > 1 quadrillion: we have a problem...
-
Adam Peterson (@_adam_here_) reportedis @AWSSupport down?
-
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.
-
Indrani Som (@indrani_som2004) reported@AWSSupport please look into this issue
-
Meo Meo (@CastleEL88) reported@awscloud Focus on AI features instead of server maintenance. .
-
paige s. (@PaigeSully88) reported@BenENewton @awscloud This isn’t human error. This is failed automation
-
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.
-
Matthew (@OneShotCaller) reported@CalebChamberla6 It’s an AWS billing error (see @awscloud)
-
Donna Paulsen (@donnapaulparody) reported@VeryCoolGuy6 @awscloud Check the issues that happened in last 6 months and diagnosis/cause of the issue.
-
🔥 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.
-
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
-
Jack Stone (@c0XhHxvylL) reported@AWSSupport be honest, how much of this problem was due to ai and/or vibecoding
-
* (@BunnnyRAM18) reported@amazonIN @awscloud The same issue happened twice for these product
-
Mario Giampieri (@mario_giampieri) reported@AWSSupport Another update- I received a canned response explaining to me what sign in credentials are and sending me a link to open a new account. Eleven months of this.
-
TeeBeeCTO (@TeeBeeCTO) reportedSetting up a new AWS account @awscloud … and get non stop errors on set up. Looks like their vibe coding dystopia worked… were all going to die because SkyNet will have error pages that end up giving us all death by error page. Amazing work… @JeffBezos !!
-
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 your 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.
-
Sai Manikanta ☕ (@rebuiltWithSai) reportedDay 19 of #JobSwitchUntilPlaced 🚀 Today's progress: ✅ Started a new Microservices project by building the User Service ✅ Solved 2 DSA problems ✅ Learned about Blob Storage (Amazon S3) One step closer to building production-ready, scalable backend systems.💪 #BuildInPublic
-
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
-
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.
-
Ing. Mario Varón M.Sc (@ma_varon_col) reported@AWSSupport BTW, a follow up email to everyone alerting of your ****** bug would be awesome. That's the least you can do ... Had to take down everything I have in production right now and I'm not certain enough of your competence to resume it once again...
-
RickDavis404 (@RickDavis404) reported@awscloud I left an EKS cluster running while waiting for my Fable 5 limit to reset...only been a few days, but Opus says my aws bill was pretty accurate, just a small rounding error, still over 950 trillion dollars 🤑
-
metis (@metis00001) reportedI can't understand why AWS has not been able to resolve my issue of payment method. Whatever credit card I put, they are not able to verify it and they keep asking me to call the card issuer. It's not card issuer issue! @awscloud
-
Mike Webb (@themikebwebb) reported@awscloud You should be the first cloud provider to issue a billing usage reset.
-
JamilOmar ( 💉💉💉🦠 💉 💉💉) (@jamilomar) reported@chuanq @awscloud same issue !!!
-
Ohm Patel (@Techieohm) reported“Facing some problems with @awscloud on our new product. This is the 2nd time this has happened.”
-
S (@cloudsurf3) reported@awscloud Take down that other tone-deaf tweet, pure mockery of your customers
-
M (@mdw864) reported@googlecloud @GoogleCloudTech do you accommodate customers with disabilities? In case we have problems and need to speak to you? I think I may have to switch to you because @awscloud has not provided accommodations for people with disabilities.