Amazon Web Services status: access issues and outage reports

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.

Most Reported Problems

The following are the most recent problems reported by Amazon Web Services users through our website.

• Website Down (67%)
• Sign in (17%)
• Errors (17%)

Live Outage Map

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

City	Problem Type	Report Time
Ciudad Jardín	Website Down	19 days ago
Kyiv	Sign in	2 months ago
Chennai	Website Down	2 months ago
Point Pleasant Beach	Website Down	2 months ago
Little Rock	Errors	2 months ago
Atlanta	Website Down	2 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:

• 
  Ryan Varghese Mathew (@RyanVarghese14) reported 1 minute ago

  Hi @awscloud @AWS I am currently facing issues from regarding certain payments. And despite incessantly reaching out on the support team and the email, I have been charged and there has been no formal support extended. I know you guys can do better than this.

• 
  M (@mdw864) reported 6 minutes ago

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

• 
  Santhosh (@santhoshv) reported 7 minutes ago

  @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

• 
  Erin (@erinEncoded) reported 12 minutes ago

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

• 
  chetan soni (@chetansoni_it) reported 22 minutes ago

  @AWSSupport Same type of issue, occurred in my account as well

• 
  Param (@Param_eth) reported 24 minutes ago

  The downfall of Storj Labs (bankruptcy): - launches Storj in 2014 to build a decentralised alternative to cloud storage - promises a blockchain based competitor to Amazon S3. - attracts thousands of node operators across the world - raises around $35 million in funding - secures roughly $30 million through its 2017 token sale - spends years building its decentralised storage network - the DePIN business model proves difficult to scale profitably 2021: - $STORJ reaches its all time high 2022–2025: - the token enters a prolonged decline - node operators report declining rewards and operational issues - Storj begins selling non-core assets and right sizing operations October 2025: - Inveniam Capital Partners acquires Storj Labs - the acquisition is expected to strengthen the company's future - financial pressures remain unresolved July 2026: - Storj Labs files for Chapter 11 bankruptcy protection - the company says legacy liabilities can no longer be outgrown - assets and liabilities are estimated between $1 million and $10 million > operations > customer services > the storage network continue running - Inveniam backs the restructuring process - Storj proposes a plan that could give STORJ token holders equity in the reorganised company - $STORJ falls another 14–15% after the bankruptcy announcement - the token is down roughly 99% from its 2021 all time high

• 
  DeeDee Armstrong (@deedeeafton) reported 25 minutes ago

  @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

• 
  Pratikkumar​ Mohite (@DotSlashMohite) reported 29 minutes ago

  Spent this week breaking down @awscloud Regions and Availability Zones what they are, why they matter, how they work, where your app actually runs, and when to go multi-Region. Thread 🧵

• 
  Vaibhav Khatri (@vaibhavkhatrii) reported 29 minutes ago

  @AWSSupport Believe me when I saw this, I had to check my BP. No issue is more than someone’s life.

• 
  Ignacio Cassinelli (@igncass) reported 29 minutes ago

  @awscloud What a terrible response

• 
  Md Jaoyad (@JaoyadCode) reported 29 minutes ago

  @awscloud you should fix it otherwise people will become sick after watching the bill!

• 
  Drate Berry (@drateberry) reported 31 minutes ago

  Is anyone else experiencing issues with the @awscloud Billing system? I’m trying to add a new card and both the physical and virtual versions are throwing a verification issue. Bank is saying they don’t see anything on their end. Waiting to hear back from AWS Support.

• 
  M (@mdw864) reported 33 minutes ago

  @awscloud can you PLEASE answer me? You’ve just turned off my Business because you will not help me. I need you to stop charging me. Do not tell me to login because I do not know the email address that was used to open the account. All I know is my bank account is being charged

• 
  Certified AI Dev (@MisterPrashant) reported 33 minutes ago

  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.

• 
  Matthew Feinberg (@thewebbie) reported 33 minutes ago

  @infoscav @awscloud 28 Billion! AWS has acknowledged there is a problem with the billing console.

• 
  Damon (@agaphto) reported 34 minutes ago

  @sorower01 @awscloud Also just got a $3m bill. There's an AWS issue going on

• 
  Mario Giampieri (@mario_giampieri) reported 35 minutes ago

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

• 
  Maurizio Santamicone (@santamm) reported 35 minutes ago

  @awscloud And while you fix it, you can credit us for those amounts.

• 
  paige s. (@PaigeSully88) reported 39 minutes ago

  @BenENewton @awscloud This isn’t human error. This is failed automation

• 
  Zyreon (@Zyreon_trading) reported 40 minutes ago

  @awscloud When i wake up i saw:there is another AWS Bug/Service Down. Lol cannot give up time of 24 hours/7 days/infinity uptime..

• 
  Indrani Som (@indrani_som2004) reported 42 minutes ago

  @Anjishnu46 @AWSSupport @AWSSupport look into this issue

• 
  Edward Donner (@edwarddonner) reported 42 minutes ago

  @darkosubotica @awscloud @AWSSupport Thanks Darko. I'm keen to be involved. I'm aware there are challenges. A billing bug shouldn't cause a global outage or delete backups. I believe these are solvable. I don't want the possibility of financial ruin from a mistake or hack. Will DM.

• 
  Amine Zack 🇩🇿 (@AmineZacks) reported 46 minutes ago

  @awscloud Bro fix your servers

• 
  Alex Hooper (@AlexHooper78640) reported 47 minutes ago

  @AWSSupport our entire system is returning 500s - what’s the eta on a fix for this?

• 
  Gerzson (@Gerzsononline) reported 49 minutes ago

  @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

• 
  GettingMyGlitchOff (@GettingMyGlitch) reported 50 minutes ago

  @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

• 
  Head4Liberty (@Head4Liberty) reported 52 minutes ago

  @thewebbie @awscloud Especially cool that the rest of the month he’s projected to recoup ~$800MM. He needs to up his usage like crazy the rest of the month! (Not to mention many other errors and inconsistencies in that snapshot.)

• 
  * (@BunnnyRAM18) reported 54 minutes ago

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

• 
  Ashmit Dutta (@ashmit105) reported 56 minutes ago

  @awscloud keeps charging me $60 a month. I can’t login to my account due to a deprecated email. Making support tickets goes nowhere. Anyone got advice on what to do?

• 
  Aaryan Bansal (@NotUnHackable) reported 59 minutes ago

  @awscloud that issue was happening since yesterday dude. why tf did it take so much time?