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 (67%)
- Errors (22%)
- Sign in (11%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Errors | 3 hours ago |
|
|
Website Down | 15 days ago |
|
|
Website Down | 17 days ago |
|
|
Website Down | 1 month ago |
|
|
Sign in | 3 months ago |
|
|
Website Down | 3 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:
-
Anjishnu Ganguly (@Anjishnu46) reportedHey @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.
-
Alvaro Villalba (@alvarovillalbap) reported@philipkung @awscloud @amazon Technical support has being helpful historically for me (with smaller problems than yours) But it did cost us a lot of $$$ for something I feel should be included Did they charge for your technical support?
-
Himanshu Singh (@hsnice16) reportedBeen using LLMs a lot to write code recently. Sometimes I learn a few new things, and sometimes it just confuses itself and me, maybe because there is no one right way to do things. Recently, while working on a pricing page for a new product we've been developing, a senior team member suggested that it would be better to extract it into a separate codebase and deploy the frontend separately. He would then route it through CloudFront under the same origin to avoid cross-origin issues when transferring credentials. I learned that using `*` for `Access-Control-Allow-Origin` doesn't work for credentialed CORS requests. But before all of this worked, I had extracted the pricing frontend into the same codebase, just in a new folder with the required files, and was trying to deploy it on the same infrastructure the rest of the application was using on @awscloud. It wasn't working because there were some issues between the build output and the CDK synthesis/deployment stages. Eventually, I extracted the code into a completely new repository and deployed it on @vercel.
-
Luke Skywalker (@LSF4Life1981) reported@RinoTheBouncer Just like you can't be bothered to Google anything PSN issue was @awscloud which doesn't say anything either
-
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
-
V0LYX (@0xV0LYX) reported@awscloud clear communication like this builds trust fast the fix matters but the transparency matters more
-
Prateek Gupta (@p_valuee) reported@AWSSupport My entire production is down since 3 days, I believe this is a P1 and should be treated like one @AWSSupport. Please help me with an ETA
-
JoeFromSJersey (@JoeFromSJersey) reported@AWSSupport Good morning folks, I appreciate the help getting things working for me yesterday as I was able to use Kiro! I'm not unable to upgrade from free tier though and get an error that says unable to upgrade. I've a case for that too and was hoping you could also get eyes on that.
-
Kartik Jain (@kartikjain0101) reported@awscloud you guy has lost your mind. payment got missing so team told me they will raising the request. account got hold, we have 250K unused credits, and now they are not initiation the account. wtf. our whole production is down.
-
Dhanush N (@Dhanush_Nehru) reportedOpened 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!
-
Mahadev Vyavahare (@mahadevkv) reported@SarvamAI should learn from American companies on how to and what to document on internet Documentation and visibility is broken compared on sarvam website. Learn from @OpenAI and @awscloud
-
Shobhit Shrivastava (@shri_shobhit) reported@adamr_1776 I left Amazon AWS around 2019. From what I recall it was something like issues dot Amazon dot com
-
Yuyun Francis (@FrancisYuyun) reported@AWSSupport case ID (178590975600210) "account activation blocked 2+ weeks by Error 880104, case escalated internally Aug 5, no update since."
-
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!!
-
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.
-
S (@cloudsurf3) reported@awscloud Take down that other tone-deaf tweet, pure mockery of your customers
-
J Bret Edwards (@jbecompslns) reporteddid @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.
-
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.
-
Maurizio Santamicone (@santamm) reported@awscloud And while you fix it, you can credit us for those amounts.
-
zarrakh (@zarrakh) reported@AWSSupport @awscloud @AWSSupport as I told before, It will be just a correspondence and no solution. I have been getting correspondence since feb 2026 but no refund, despite of your team confirmed that the issue is on your side.#aws
-
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
-
Felipe Rojas (@FipeRojas) reported@AWSSupport as root admin of a management account in Chile, your system failed to issue our statutory VAT invoice despite our tax settings were configurated according to your mails and RUT verified since june 2. Already 4 open cases without answer. ID 178524912400362
-
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.”
-
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).
-
Ivan Toma (@FounderRAVERK) reported@awscloud @Google @Microsoft The water problem is only going to get bigger. We already have technology that can help data centers produce their own cooling water from the sea. Let’s solve this together.
-
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.
-
DeeDee Armstrong (@deedeeafton) reported@t1097s @larunachalam @awscloud Tyler, are you an AWS actual customer, or just someone who thinks real people should “chill out” when a vendor causes actual business trouble and then jokes about it?
-
Samrat Singh (Sam) (@isamrats) reported@KahlonGurshaan @Rushike32313211 Yes its down , but no official confirmation posted by @awscloud yet
-
Kailash Tulsi Gajra (@kailashgajara) reportedIs @awscloud down right now? #AWSDownAgain #AwsDown
-
BOB-DO-THEM (@osangesua) reportedThis is a blatant lie intended to mislead the electorate. The glitch synchronisation in the BVAS is the reason he won't effect the upgrade because if an upgrade is carried on the BVAS, the entire calibration of glitches will disappear and the fear that @awscloud may have disabled or blocked the application that allows them to manipulate the BVAS is the reason for this unprovoked lies