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 (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	4 days ago
New York City	Website Down	6 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:

• 
  Sai Manikanta ☕ (@rebuiltWithSai) reported 24 seconds ago

  Day 19 of #JobSwitchUntilPlaced 🚀 Today's progress: ✅ Started a new Microservices project by building the User Service ✅ Solved 2 DSA problems ✅ Learned about Blob Storage (Amazon S3) One step closer to building production-ready, scalable backend systems.💪 #BuildInPublic

• 
  Adam Peterson (@_adam_here_) reported 37 seconds ago

  @AWSSupport Even the AWS health page was down. Total AWS system downtime for 12-13 minutes. AWS appears back now.

• 
  Matthew (@OneShotCaller) reported 1 minute ago

  @CalebChamberla6 It’s an AWS billing error (see @awscloud)

• 
  Toastie (@hightoastie) reported 2 minutes ago

  @marcelocantos @awscloud How would forfieting a chess tournament fix the problem though?

• 
  Certified AI Dev (@MisterPrashant) reported 2 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 their 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.

• 
  Corey Quinn (@QuinnyPig) reported 4 minutes ago

  Kinda funny that nobody's even making observations like this about @awscloud, if you want to go a level deeper down the irrelevance well.

• 
  Matt Teixeira (@matt_teeixeira) reported 9 minutes ago

  @priyansh_ptl18 @awscloud @AWSSupport Error I'm sure?

• 
  𝘋𝘳. 𝙈𝙞𝙘𝙝𝙖𝙚𝙡 𝙅. 𝙋𝙚𝙩͛𝙚𝙧𝙨𝙤𝙣 (@WeatherArchive) reported 13 minutes ago

  Somehow, GOES19 going down wasn’t the craziest thing to happen this week. Happy bankruptcy day to those who celebrate (I.e., have an @awscloud account)

• 
  Nil (@slowalgorithm) reported 13 minutes ago

  @awscloud The LEAST you can do is to give some compensation. This mistake caused operational issues for several companies across the globe.

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

  @jeffdafo @ivanburazin @awscloud Even aspnetcore can run on Linux now - there is no excuse to have (and pay through the nose) for Windows server licenses)

• 
  Sudeep (@sudee1285) reported 15 minutes ago

  I need assistance to access existing APN account...it's getting error.. please help me. @awscloud

• 
  Guilherme Lage (@ItsEasypop) reported 17 minutes ago

  Another OG goes down. I remember people calling Storj the next Amazon S3 back in 2018

• 
  Santhosh (@santhoshv) reported 18 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

• 
  Indrani Som (@indrani_som2004) reported 24 minutes ago

  @AWSSupport please look into this issue

• 
  Alvaro Villalba (@alvarovillalbap) reported 24 minutes ago

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

• 
  S (@cloudsurf3) reported 25 minutes ago

  @awscloud Take down that other tone-deaf tweet, pure mockery of your customers

• 
  PositiveVibes (@KPTheFighter) reported 26 minutes ago

  @awscloud @AWS You guys almost gave me heart attack today morning. When saw the email from you with billing about $192 million, I got shaken up, frozen. Logged into dashboard , and saw same amount. Imagine what would have been the state of mind. This is not done!! Mistakes do happen, being in tech industry, I do understand that. But once you recognised that mistake, you did not have courtesy to send an email to all users asking not to Panic. That is not acceptable. Before one could reach to support page, his soul would leave the body. Immediately you should have put a banner on dashboard reporting about the potential issue and could have sent a next communication to users informing them. You didn’t do anything of that sort and left users in panicked state. This is so unprofessional. Really disappointed!!! You would have been responsible if anything tragic happened to me today just because of your negligence. A communication asking users to ignore the faulty email was due. You didn’t do that. Shameful!! #awsbilling #aws

• 
  AntDracula (@ant_dracula) reported 26 minutes ago

  @kankerhoerrrrrr @marcelocantos @awscloud And you had no response for "what's the alternative to shutting down services, just pay the bill?" Maybe you really are an AI bot instead of a retard.

• 
  Shobhit Shrivastava (@shri_shobhit) reported 27 minutes ago

  @adamr_1776 I left Amazon AWS around 2019. From what I recall it was something like issues dot Amazon dot com

• 
  M (@mdw864) reported 37 minutes ago

  @AWSSupport Five months of broken links & blocked support channels is unacceptable. You have more cut off core business services because you have refused to provide a person with disabilities a way to tell you that you are over billing me. Escalate to a senior rep to fix this before 9am cst

• 
  metis (@metis00001) reported 39 minutes ago

  I can't understand why AWS has not been able to resolve my issue of payment method. Whatever credit card I put, they are not able to verify it and they keep asking me to call the card issuer. It's not card issuer issue! @awscloud

• 
  kakafa.btc (@kakafa_btc) reported 40 minutes ago

  @AWSSupport Still NO resolution after 7 days! Case ID: 17849863000462 Account hold cleared days ago, but CloudFront is STILL locked due to a backend flag sync issue. @AWSSupport keeps passing the buck. Assign a supervisor to clear this flag NOW! @awscloud #AWS #CloudFront #AWSCloud

• 
  Fikri Firdaus (@fikrfird) reported 42 minutes ago

  @awscloud This really isn’t something to joke about. A false billing alert at this scale can cause genuine panic and even serious health consequences. Some users may have rotated credentials, shut down workloads, or deleted services because they feared their accounts had been compromised.

• 
  Mario Giampieri (@mario_giampieri) reported 42 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.

• 
  Mike Webb (@themikebwebb) reported 47 minutes ago

  @awscloud You should be the first cloud provider to issue a billing usage reset.

• 
  devastatindave.eth (@NftCelestials) reported 47 minutes ago

  @awscloud totally avoidable error caused by reliance on unskilled h1b scabs ya'll will learn eventually

• 
  Abhijit Tripathy (@AbhijitTripat13) reported 55 minutes ago

  @awscloud @awscloud still no response. You guys are so slow

• 
  mark seery (@140ismymax) reported 58 minutes ago

  Peter DeSantis talking at #agenticaisummit There will NOT be one AI chip type. If multiple AI chips take multiple years to bring to market, you have to be making assumptions about model requirements in that time frame. It's a systems problem, including the network. Constraint drives innovation. Future is bright and built together. Peter DeSantis SVP, Foundational AI Models, Custom Silicon, Quantum Computing, Amazon @awscloud @amazon @BerkeleyRDI #AI

• 
  Anjishnu Ganguly (@Anjishnu46) reported 59 minutes ago

  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.

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

  @awscloud Your AI sucks and costs more than humans. This sure is not a human error