Amazon Web Services status: access issues and outage reports
Some problems detected
Users are reporting problems related to: website down, sign in and errors.
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.
August 10: Problems at Amazon Web Services
Amazon Web Services is having issues since 09:50 PM IST. Are you also affected? 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 |
|---|---|---|
 Township of Evan
|
Website Down | 5 days ago |
|
New York City
|
Website Down | 8 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:
-
AntDracula (@ant_dracula) reported@kankerhoerrrrrr @marcelocantos @awscloud "skill issue" is a term only unironically used by losers and AI bots. I can take a guess at which one you are.
-
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. 😞
-
That Other Hecate (@HecateKeys) reported@OwenGregorian 1) Forgets how DNS works. AWS goes down for days. 2) Forgets how arithmetic & metering works. Trillion-dollar bills for scant usage. @awscloud Regretting all those mass layoffs of your veteran engineers yet?
-
Indrani Som (@indrani_som2004) reported@AWSSupport please look into this issue
-
Ironluca (@Ironlucaaa) reportedHeyo again @AWSSupport, thanks for fixing the issue! My bill is only $503 now. That's much better, it's okay now!
-
Aaryan Bansal (@NotUnHackable) reported@awscloud that issue was happening since yesterday dude. why tf did it take so much time?
-
The Trading Guy (@thetradingguy_) reported@AWSSupport , got no replies on this upon follow up message. Please look into it. Why is it so tough to resolve an issue?
-
billy (@Billy17979063) reported@fortniteleaksmy It’s up for some down for some @awscloud ******* decides to shut down not just PlayStation but other platforms too
-
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.
-
D (@D8118199174282) reported@awscloud No, you still haven’t compensated users for the cost bug error
-
Koray Yersel (@korayyersel) reported@AWSSupport My balance went down to zero. Time to the delete the aws account.
-
DeeDee Armstrong (@deedeeafton) reported@Gozieuk @awscloud You felt they were transparent? I got the anomaly detection email from AWS last night. Dashboard had an outrageous $$ number. Spun up devs to find out problem. And- then AWS posted a joke here on X, and still no email as a follow up to their first one. Doesn’t seem transparent
-
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.
-
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
-
(au)stin (@stin_reece) reported@awscloud $50,000,000,000 says this was a vibe code error
-
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.
-
Abhijit Tripathy (@AbhijitTripat13) reported@awscloud @awscloud still no response. You guys are so slow
-
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
-
Santhosh (@santhoshv) reported@PinokioSystem @AWSSupport But again health dashboard says forcast, but usage itself showing.. how come this is not explained correctly. Another point is it's the billing and money not any service down, so billing page itself could have add some alert
-
Matthew (@OneShotCaller) reported@ZZiata15569 @awscloud I have billing and budget alerts set up with AWS already. Main problem with a lot of tools I’ve used is too much noise in the alerts vs AWS option. Still, I think every AWS customer gets at least 1 surprise lol… part of initiation (onboarding?)
-
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.
-
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
-
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.
-
Jack Stone (@c0XhHxvylL) reported@stoprocent @AWSSupport when you owe aws 10k that's your problem when its 1 trillion it's their problem
-
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.
-
Nicholas Griffin (@ngriffin_uk) reported@deedeeafton @awscloud you should have enhanced your calm and raised a support issue instead.
-
Kish_lloyd (@kish_lloyd) reported@AWSSupport Why does this feel like a stage for subscriptions hikes on other hosting providers. Previously human error was deemed the highest risk for error but if humans made AI 🤔
-
Erin (@erinEncoded) reported@awscloud This is tone deaf. It wasn’t funny. It was upsetting. It reduced my trust in your systems, testing, and ability to roll back critical errors. I didn’t laugh. Why are you?
-
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
-
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