Amazon Web Services

Is Amazon Web Services down?

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.

Amazon Web Services Outage Chart 01/29/2026 17:45

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.

  1. Website Down (47%)

    Website Down (47%)

  2. Errors (41%)

    Errors (41%)

  3. Sign in (12%)

    Sign in (12%)

Live Outage Map

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

Loading map, please wait...
City Problem Type Report Time
United KingdomBirmingham Errors
United StatesNew York City Website Down
United StatesSan Jose Errors
United StatesSan Jose Errors
ColombiaCali Website Down
FranceSandillon Website Down
Map 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:

  • CTOAdvisor Keith Townsend (@CTOAdvisor) reported

    Anyone out there actively talking to their @AWScloud account team about Outposts Server?

  • coates Sean Coates (@coates) reported

    Honest question: is there a security reason for not saying which bucket here, @awscloud team? “…NoSuchBucket: An error occurred (NoSuchBucket) when calling the PutObject operation: The specified bucket does not exist” I can dig, but it sure would be helpful to see it inline.

  • DKinkler Bruh Moment Connoisseur (@DKinkler) reported

    @awscloud Remember when AWS went down like last week

  • vennemp Matthew Venne (@vennemp) reported

    @marekq @QuinnyPig @awscloud My point (though terse) was without these issues the CSPs wouldn’t be motivated to improve their architecture and design. They had a single point of failure that disrupted a huge portion of the internet. Now we all know it and the ball is on their court

  • aasheikh Asad Sheikh (@aasheikh) reported

    Problem: @awscloud is always having an outrage. Solution: @googlecloud and its multi cloud strategy #Anthos platform

  • coates Sean Coates (@coates) reported

    Honest question: is there a security reason for not specifying the bucket here, @awscloud team? “…NoSuchBucket: An error occurred (NoSuchBucket) when calling the PutObject operation: The specified bucket does not exist” I can dig, but it sure would be helpful to see it inline.

  • ZiggyTheHamster Keith Gable 🌻 (@ZiggyTheHamster) reported

    @simonggillett @QuinnyPig @awscloud I don’t think that they don’t know how to technical write, but rather that they’re not comfortable naming systems or architectural patterns, so it gets edited down to something that sounds less competent.

  • hypermikem HyperMikey (@hypermikem) reported

    @pmac92681135 @NextGenStats @awscloud A screen pass can go down as the longest completion if it goes for more yards. This was 63 yards IN THE AIR on a dime. There's a difference.

  • TonyOnTheTweetr Tony on the Tweetbox (@TonyOnTheTweetr) reported

    @QuinnyPig @awscloud In doing so most stuff recovered before we could even tell why it had broken. So here’s a partial description containing what little we do know for sure and a promise we’re going to theorize real hard about what we didn’t actually capture’

  • skydodiya Aakash Dodiya (@skydodiya) reported

    Hey @awscloud, please fix SQS console search. It's very hard to search queue by name. Give it a try so you will understand.

  • OLayer8 OSILayer8 (@OLayer8) reported

    @QuinnyPig @awscloud Move the cloud they say, it's resilient. It doesn't go down. Then it goes down. And they don't know how to fix it.

  • ryan_sb Ryan "Non-Fundable Token" Scott Brown (@ryan_sb) reported

    @g_bonfiglio @QuinnyPig @awscloud Because for example in the 2017 S3, 2021 Kinesis, and this latest availability event outage reports, there is a section mentioning dependency on internal AWS networks/services. If that's all about to change that is great news, but hard to see as a customer to know 2/2

  • Kahnighticus Bryan K (@Kahnighticus) reported

    @mmceach476 I didn’t realize the AWS outage was still a thing… terrible look @awscloud

  • Si_ShaunRyan shaun ryan (@Si_ShaunRyan) reported

    @ItaiYaffe @awscloud lol... at least it wasn't a person this time that accidentally shut it down a name server. It was a computer that accidentally started everything up.

  • MiggsSD1964 Michael L. (@MiggsSD1964) reported

    @BuffaloBills @awscloud Only tells half of the story. They are getting dominated by the run. As a result, the passing stats are down.

  • SIGSEGV23 SIGSEGV (@SIGSEGV23) reported

    @ashishlogmaster @QuinnyPig @awscloud It’s not a single region service. I had no problems with SSO at all during the incident. It worked like a charm in the EU regions.

  • AaronBoothUK Aaron Booth (he/him) (@AaronBoothUK) reported

    @poiThePoi @QuinnyPig @awscloud Yeah not biased advice at all. Most people's risk profiles do not require multi region. The risk of having aws issues compared to the likelihood of breakages and issues due to your own poor implementation or losing skills in the workforce.

  • kenhorn Terrahorn (@kenhorn) reported

    @fintanr @awscloud My takeaway is that apps/clusters should support a stable mode, where you avoid autoscaling if infra has issues - azure had similar impact. Minimising control plane dependence has some value, at times.

  • strategistmag Chris Middleton (@strategistmag) reported

    What happens if a human uses @Amazon / @awscloud EC2 to attempt to log on to a domain you own as admin, using your name - not my login btw - and you report it, with IP address, date, time etc? I can answer that: nothing. They have refused to give me any info without a court order

  • ashishlogmaster Ashish “Logmaster” (@ashishlogmaster) reported

    @QuinnyPig @awscloud Will be interesting how they will “improve” AWS SSO. We were SOL as we could not login at all! It’s a single region service and does not support “dual” instances (2 diff regions) by AWS org.

  • gpapilion Geoffrey Papilion (@gpapilion) reported

    @QuinnyPig @awscloud Its really hard in large scale infra. Facebook’s badge system breaking is a good example during the routing outage. Auth, routing, and naming are often global things so when touching them, it requires lots of thought. Then since they are so foundational you can break everything

  • fapo39 fapo (@fapo39) reported

    on a side note amazon AWS tokyo is terrible, I had to downscale to 360p to even be able to listen to the stream...

  • ngissahgeorge12 George Ngissah :-) (@ngissahgeorge12) reported

    @Nana_Awuku24 @awscloud They took a good amount of the internet down for days.

  • Si_ShaunRyan shaun ryan (@Si_ShaunRyan) reported

    @ItaiYaffe @awscloud lol... at least it wasn't a person this time that accidentally shut down a name server with terminal cmd. It was a computer that accidentally started everything up.

  • annaspies Anna Spysz 💉💉💉 (@annaspies) reported

    @mitabaxi @awscloud I'm kidding :) My #1 goal at AWS is to not cause a wide-scale outage that gets written about in the news

  • JK_Dynamic_D wingdingking (@JK_Dynamic_D) reported

    @QuinnyPig @awscloud Us-east-1 has been a SPOF that people just don't want to admit is there sense the beginning. Scores of things just stop when it has issues.

  • Friar_Fest Manny Munchado (@Friar_Fest) reported

    @NextGenStats @GManzano24 @awscloud “Check down king” I heard

  • wrd83 Alex (@wrd83) reported

    @QuinnyPig @awscloud Does it matter what the fine grained failure models are? Whats important is that your design can mitigate failures such that you don't go down with them..

  • aggarwal_aviral Aviral Aggarwal (@aggarwal_aviral) reported

    @AWSSupport Hi, I made an account November 2020 for learning purposes , but now I am unable to sign in as I have lost my MFA information and unable to change password as I have no longer access to that e-mail , I have sent you all the details in DM, please terminate my account...

  • g_bonfiglio Giorgio Bonfiglio (@g_bonfiglio) reported

    @ryan_sb @QuinnyPig @awscloud Although the current SHD can scale in terms of traffic, it doesn't scale in terms of content and mechanism - but things are about to change. Another issue which leads to what's externally perceived as "posting delays" is AWS only communicates when certain about things.