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 (53%)
• Errors (30%)
• Sign in (17%)

Live Outage Map

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

City	Problem Type	Report Time
Kyiv	Sign in	12 days ago
Chennai	Website Down	15 days ago
Point Pleasant Beach	Website Down	19 days ago
Little Rock	Errors	23 days ago
Atlanta	Website Down	23 days ago
Clearwater	Website Down	24 days 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:

• 
  LAuk23 (@Pearl23X) reported 1 minute ago

  @WNBA @awscloud Your AI is broken. Back to the drawing board.

• 
  TechBrosTechBro (@WE2SeriousConvo) reported 5 minutes ago

  @JeffBezos We need to give everyone in the world 1VCPU for free for life from amazon aws. That will solve all world problems. People can rent them out or host their websites and or business ideas. Call me Jef..

• 
  Intelfactor AI (@IntelFactorAI) reported 10 minutes ago

  @awscloud More AI-Agents doesn’t make your revenue grow faster. It might actually slow you down.

• 
  AntDracula (@ant_dracula) reported 11 minutes ago

  @leeman24 @GyuMusang56418 @awscloud They don’t need sloppers. They need people with deep knowledge of their products, not slop cannons taking down entire regions. They laid those people off and now it’s an outage every other week, with worse support.

• 
  Anna Singh (@anna_fanatic) reported 13 minutes ago

  @amazon @awscloud And shamelessly your team instead of rectifying have blocked my account. They didn’t bother to sort a small issue from your end the so called technical glitch just sent auto generated emails and blocked my email and twitter

• 
  Ahmed Fouad (@ahmedfouaddev) reported 18 minutes ago

  @awscloud Yeah, because it takes much more time to debug and find issues later...

• 
  Eduard Lugo (@eduardlh) reported 19 minutes ago

  @AWSSupport @AWS 🚨 URGENT: Account 8366-7457-5282 suspended due to unauthorized 3rd party access. We CANNOT access console to complete required remediation steps. Support case 177899971400371 open 48hrs+ with no resolution. Deadline June 16. Business fully down.

• 
  Astro Kanu (@AstroKanu) reported 19 minutes ago

  @aws @AWSSupport I’ve already used this link raised tickets explained the ongoing issue the only reply I got was pls log in- day 5 of my live project down- all payments made at my end- I’m serous if this isn’t resolved I’ll ask my clients to start contacting u for refunds #aws

• 
  peepee2u (@peepee2her) reported 22 minutes ago

  @AWSSupport Are there some ongoing outage on AWS route53? saw many 503 error from API response cross accounts and regions.

• 
  Ross 🛩️ (@airline_king) reported 23 minutes ago

  Likely this **** is staged… But I had @amazon send me a crusty Apple Magic Keyboard that they demanded to get back even though they would dispose of it/saw pictures (wasn’t even the one I ordered with Touch ID) , and made me waste 6+ hours on the phone being angry with customer service (which I am not proud of). The scumbag who took an Xacto knife to the seal, replaced it, and sealed it up for return likely got away with it. Days later, they had the audacity to threaten me via email after over the whole experience. That was the day I decided to start winding down Amazon purchases and tel myself to never use @awscloud for anything if that’s how they want to act. Just amazing how they deal with this. Cc @AmazonHelp my memory is deep after that experience and I will hold a grudge over this.

• 
  If Beli (@beli_if) reported 25 minutes ago

  @awscloud Until your services are not working for 4 hours, right ?

• 
  Preetham Kyanam ☣︎ (@pkyanam) reported 27 minutes ago

  @QuinnyPig @AWSSupport I’m having issues with Mantle. I tried accessing GPT-5.5 through it and it says my account doesn’t have access. Same issue with Opus 4.7 and 4.8. 4.6 works fine.

• 
  Ross 🛩️ (@airline_king) reported 29 minutes ago

  Likely this **** is staged… But I had @amazon send me a crusty Apple Magic Keyboard that they demanded to get back (wasn’t even the one I ordered with Touch ID) , and made me waste 6+ hours on the phone being angry with customer service (which I am not proud of). The scumbag who took an exacto knife to the seal, replaced it, and sealed it up for return likely got away with it. Days later, they had the audacity to threaten me via email after over the whole experience. That was the day I decided to start winding down Amazon purchases and tel myself to never use @awscloud for anything if that’s how they want to act. Just amazing how they deal with this. Cc @AmazonHelp my memory is deep after that experience.

• 
  Cornfields1 (@CornFieldsOne) reported 29 minutes ago

  @IAGovernor @awscloud @Cognizant This is extremely disappointing, selling out hard working IOWANS for Indians. Terrible. DOJ needs to step in

• 
  Ventilateur sous couverture (@HugeVentilateur) reported 30 minutes ago

  @_JX14_ @irshit0 @awscloud This does not work as you expect. First ai is dumb, it can't remember things other months let alone years, second, it hallucinate, there is no fix for that yet. It also write convoluted code that "may" not work. Data leaks will exploded in the coming years...

• 
  angelmilkcry (@alina_aalx) reported 32 minutes ago

  @awscloud Maybe it’s your inability to adapt. You are used to development being a slow and manual process…that's how you sell more of your services

• 
  wokler (@wokler_) reported 37 minutes ago

  @awscloud It only took your servers doing down 3x as often to figure it out. good job.

• 
  esyx (@esyx0) reported 40 minutes ago

  Today i got email from AWS that they can't approve my request for **** SES no explanation at all, only generic "During our evaluation, we identified some concerns that prevent us from approving your request. Due to security reasons, we are unable to provide specific details about our assessment criteria." has anyone had to deal with this? All i wanna use the SES for is transactional mails like verification, reset, notifications about your account etc @awscloud @AWSSupport Can you please help? At least tell me what's wrong so i can fix it, i genuinely have no idea

• 
  Buttface (@buttface_9000) reported 43 minutes ago

  @sult @awscloud I mean, what are you trying to say? That they should double down on that or learn from their mistakes?

• 
  Abomination (@Abomination81) reported 44 minutes ago

  @paulonoldin Ahh there is a huge problem. get an amazon aws in ireland, its like 5-10 a month usd. It will massively improve it

• 
  Tofu (@tofujson) reported 45 minutes ago

  @AWSSupport No, it's a problem you need to solve, you know there is, you've already received feedback and reports.

• 
  Teri Radichel #cybersecurity #pentesting (@TeriRadichel) reported 46 minutes ago

  I’m using @anthropic opus 4.8. With @awscloud Kiro. I have rules in my README that say only use Bash. But it ignored my instructions and said sorry I used Python after using a lot of tokens to do something I didn’t want it to do. I feel like I should get those tokens refunded: this is the kind of thing that unexpectedly wastes money and time and tokens unnecessarily. I can’t make the instructions any clearer. Stuff like that is so annoying. But I’m still writing code way faster. The problem is I got a $20 plan and used it up in a few hours. I tried switching back to 4.6 but seemed like the same results for code written. It’s like everything got more expensive after the new model showed up. Or maybe I really was just making that big of a change. I had to just up the subscription to $40. I’ve already spent a bunch of money on other subscriptions and got incorrectly billed $200 in tokens I couldn’t use this month (working on getting that refunded). So you can do the math. $40 per day x 31 = $1240. But people are using multiple agents. I could spin up an army of agents to write code for me if it didn’t cost so much. Who is going to win this game? As a single developer I’m seeking ways to reduce token usage (or whatever the billing metric is) and mistakes by agents like this one feel so unfair. It clearly was not what I asked for. Whether I fix it or the agent notices its mistake after the fact and fixes it without telling me it’s still going to cost the same. Bottom line is that I can produce a lot but it also costs me a lot and so far I haven’t found a way around that besides writing deterministic code I can then use instead of AI. I have to get the thing built I want to make me money before I spend it all on AI tokens. But right now the agent is making mistakes and getting stuck on things I’m doing that I guess are unique and the agent hasn’t seen too much before. It writes code and can’t figure out what it did wrong, AWS shared networking with VPC endpoints and organizations delegated admins and such I’m getting around that (without giving up full access to my cloud account) by creating verification queries and code but then the agent doesn’t follow the existing file structure and uses the wrong language without at least asking…*sigh* Also it seems like the verification code is burning tokens like a wildfire out of control. Not sure how this is going to work out. I hope there’s not some issue like someone else siphoning off tokens behind the scenes or some other weird problem like the previous nerf issue.

• 
  Munawwar Firoz (@munawwarfiroz) reported 47 minutes ago

  @AWSSupport I don't care anymore. These issues were reported years ago by others but never fixed.

• 
  akash (@akashtattva) reported 47 minutes ago

  i wonder whether anyone has ever mapped amazon AWS server costs to specific product feature improvements. because this kind of accounting framework being applied ai spend seems intuitively wrong to me.

• 
  L'éclaireur (@apex_leclaireur) reported 50 minutes ago

  @luckychappy_ Only in your head, reality is they had a 6 year contract with a server provider and then switched to amazon aws servers. So your claims are bs. I studied computers and you dont understand anything. All battle royal games use 20hz servers that dont fail but your connection does

• 
  primate portfolio (@AgastyaSinha7) reported 50 minutes ago

  @BullTheoryio This is such a bullshit argument. Yes there are 3 customers but does he realize they are just gateways for AI access? Amazon AWS, Google GCP and Microsoft Azure buy the GPUs and install them in their data centers. Then these data centers are made available to small and bug enterprises via Cloud services? The alternative would be every individual and company buys their own servers and racks and build software on top for provisioning/security/resource allocation. This is slow and lot of overhead. But the demand is so strong that companies will go down this route if the cloud providers cannot service their needs and are not eating up every GPU Nvidia is making. Also, Nvidia is expanding the field. Enter project Stargate, Oracle, Neoclouds, consumer friendly GPUs.. Like wtf is this concentration argument. The cutting edge GPUs are not a direct consumer device

• 
  Arroiss (@arroiss12) reported 52 minutes ago

  @felipestscosta @AWSSupport I'm having the same problem and AWS isn't giving me a proper response. I'm losing a lot of money because my services stopped without prior notice. @AWSSupport

• 
  Ronald van Loon (@Ronald_vanLoon) reported 53 minutes ago

  Most AI pilots do not fail because the model is weak. They fail because the enterprise underneath it was never built for production AI. → Data volume → Latency → Deployment cycles → Legacy dependencies → Technical debt This is the infrastructure problem nobody is talking about. Sponsored by @awscloud. #AWSpartner

• 
  Astro Kanu (@AstroKanu) reported 56 minutes ago

  @awscloud @AWSSupport if u don’t resolve this on urgent basis I’m going to start telling my clients who have paid for my services- which are down because of you to start writing to u to claim a refund - you cannot disrupt a live project and be so causal about this #aws #awsscam

• 
  Tarun Singh (@JodhaTarun60774) reported 60 minutes ago

  @AWSSupport Still not working...