1. Home
  2. Companies
  3. Amazon Web Services
Amazon Web Services

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.

  • 78% Website Down (78%)
  • 11% Sign in (11%)
  • 11% Errors (11%)

Live Outage Map

The most recent Amazon Web Services outage reports came from the following cities:

CityProblem TypeReport Time
Township of Evan Website Down 13 days ago
New York City Website Down 15 days ago
Ciudad Jardín Website Down 1 month ago
Kyiv Sign in 3 months ago
Chennai Website Down 3 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:

  • MrKryptonBTC
    ✨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

  • omnishredder_
    Omni (@omnishredder_) reported

    @AmazonUK @Twitch @awscloud sort yo ****, I'm getting tired of ironically the last two days unable to watch twitch without lag or buffering at random with no explanation, it's almost like the ******* AI training is the problem that nobody wanted! How about ******* remove it!

  • JoyKingdomx
    Joy | 🔥 (@JoyKingdomx) reported

    As 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.

  • mrwcjoughin
    Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported

    @meaningoflights @jpschroeder @awscloud what issue do you have with that?

  • dvtoever
    Daniël (@dvtoever) reported

    @marcelocantos @awscloud Totally agree. I my took hours for the stress to leave my body. I tought i was hacked and my services were abused. They didnt bother to take down the billing page temporarily with a warning or sent a follow up mail pointing out this bug.I am going to close down my account as well

  • ant_dracula
    AntDracula (@ant_dracula) reported

    @ngriffin_uk @perezcarreno @awscloud You never built anything of consequence, ever. This could have set off circuit breakers where people would automatically shut down and nuke services when a bill gets out of control because AWS themselves doesn’t have a spend cap. Lower your tone.

  • MisterPrashant
    Certified AI Dev (@MisterPrashant) reported

    This 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.

  • clement___10
    Clem ent (@clement___10) reported

    Self hosting your email server is something that Is very tricky and I still can't grasp till today. The craziest part is not the setup but managing the email server reputation. I rather pay @Cloudflare or @awscloud.

  • Anjishnu46
    Anjishnu Ganguly (@Anjishnu46) reported

    @AWSSupport @awscloud, please don't reply again just to say this was shared internally. Assign someone who can actually look at the account, explain what's blocking it, and fix it.

  • GettingMyGlitch
    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?

  • wilczynski24
    Maciej Wilczyński (@wilczynski24) reported

    @opsolutehq @awscloud Otherwise, I believe it's not fully viable for full-range products. Example of Lovable: they have hundreds of potential use cases. That's where they are on credit-based systems rather than outcome-based systems, because you can't narrow down the overall cafeteria of use cases.

  • drabs_i
    IDrabs (@drabs_i) reported

    @PlayStation @awscloud Wtf you playing at fix the outage.

  • DrDKumar_NRI
    Prof. D. Kumar (@DrDKumar_NRI) reported

    @AmazonHelp @amazonIN @awscloud Amazon pay UPI is blocked and can not verify device while other UPIs r working on porting the number. Been 03 days and the issue is still not resolved. LOOK INTO TICKET # V2289236874 and resolve at its earliest. Already cleared data, reboot!

  • jdonovan42
    jd42 (@jdonovan42) reported

    @DarioCpx Pls recalculate considering the massive clouds the AI revs sit on. Each $1 in AI attaches $1.5-2.5X attached cloud biz and your down to 30-45% of revs. Then as open wgt models gain apply the 100% revenue retention vs. 60% on frontier and look at EBITDA % from frontier is 10-15% max. But nice try ;) No doubt Anthropic and OpenAI both stimulate demand for Amazon AWS. It creates 2x the cloud biz than it does the direct AI biz. So why not count the full picture of things vs just the #'s that fit one narrative.

  • mailbox28564784
    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

  • payal_codes
    Payal (@payal_codes) reported

    Day 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.

  • BunnnyRAM18
    * (@BunnnyRAM18) reported

    @amazonIN @awscloud The same issue happened twice for these product

  • Anjishnu46
    Anjishnu Ganguly (@Anjishnu46) reported

    Hey @AWSSupport, Our Case 178452910500907 is still not resolved, and we've been left waiting without any meaningful update. Because of this, we're also unable to apply for AWS Activate, which is directly impacting our business operations and slowing down our workflow. This delay is becoming unacceptable. Please look into this urgently and help resolve it as soon as possible.

  • okko
    Okko Ojala @okko@mastodon.social (@okko) reported

    @edwarddonner @awscloud @AWSSupport Combine a bug like that and spending caps, and the services would have been taken down and caused major losses of services worldwide.

  • jbecompslns
    J Bret Edwards (@jbecompslns) reported

    did @AWSSupport lay off all the accounts and billing people or are they all just swamped from all those insane billing estimate cases from last week? I don't remember the wait times being this bad when I was still working at AWS a few years ago. It's kind of surreal being on the other side of the fence, knowing exactly what needs to be done to resolve the issue, but then having to wait to get someone to actually look at the case. I think they laid off too many people. This is going to come back to bite them in the medium to long term.

  • GettingMyGlitch
    GettingMyGlitchOff (@GettingMyGlitch) reported

    @AWSSupport Yeah its just getting automated responses to everyone saying "Your account will not be re-opened. We regret that we have not been able to address your concerns to your satisfaction." so can you send the mturk team a message to review the error since its more then just me its

  • mon73x
    Mon (@mon73x) reported

    @asimrazax @AWSSupport I have the same problem. Did you fix it?

  • iproductAI
    Priyanshu (@iproductAI) reported

    Here’s the cleaned-up version with fixed grammar, same hard tone, and no em dashes: I requested @awscloud to increase my Opus 4.6 V1 limit and I’ve been chatting with the AWS support team for almost 4-5 days now. They’re telling me this. Is @awscloud a government company? I mean, you guys can’t just pass the problem from one department to another. I mean, WTF? Now I have to raise my query again to sales? Why can’t you just pass this query? You already have more context about what the issue is. I can’t believe how these big MNCs are working these days. Totally absurd service from @awscloud. One more thing, please educate your support. I mean, she didn’t even know what the TPD limit is in the service quota. She literally replied the first time saying there’s only a TPM limit and no separate TPD limit.

  • jbodl
    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?

  • doktorgphd
    Gabriel (@doktorgphd) reported

    @awscloud wow really??? i had to search x for the reason?? not even an email?? I saw the email sent yesterday about the cost alert and I spend the last hour trying to work out what is going on because it looks very legit and I only find out it was an error on x! Just had to send an email!!

  • ant_dracula
    AntDracula (@ant_dracula) reported

    @BohemiaTech @awscloud Google just randomly shuts down services for no clear reason. That’s why they’re not trusted

  • p_valuee
    Prateek Gupta (@p_valuee) reported

    AWS 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?

  • slowalgorithm
    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.

  • isamrats
    Samrat Singh (Sam) (@isamrats) reported

    @KahlonGurshaan @Rushike32313211 Yes its down , but no official confirmation posted by @awscloud yet

  • Dhanush_Nehru
    Dhanush N (@Dhanush_Nehru) reported

    Opened a support portal ticket on AWS. For a week, I heard nothing. contacted @AWSSupport by direct message and the issue was resolved in a matter of days. Their team still responds to thousands of queries every day. That's how genuine support appears. Thank you AWS!