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 (46%)
• Errors (35%)
• Sign in (19%)

Live Outage Map

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

City	Problem Type	Report Time
Kyiv	Sign in	18 days ago
Chennai	Website Down	21 days ago
Point Pleasant Beach	Website Down	26 days ago
Little Rock	Errors	29 days ago
Atlanta	Website Down	29 days ago
Clearwater	Website Down	1 month 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:

• 
  Mike | 🏀 Sports Ninja (@Major_Mike) reported 5 minutes ago

  @WNBA @awscloud Your gravity board is broken

• 
  Ventilateur sous couverture (@HugeVentilateur) reported 6 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...

• 
  If Beli (@beli_if) reported 7 minutes ago

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

• 
  Astro Kanu (@AstroKanu) reported 7 minutes ago

  @Suraj_Lande_ @awscloud is running a scam in India- payments taken but services not given at multiple levels! It’s time to raise this issue ! We as paying clients cannot be treated this way ! #awsscam

• 
  Rohan Jeruel (@JeruelSingh) reported 9 minutes ago

  @AWSSupport @AWS Our AWS account has been suspended for 48+ hours. Production SaaS platform serving enterprise clients is down. Support case open but UNASSIGNED. We need a human at AWS Trust & Safety or Account Reinstatement to look at this TODAY. #AWS #AWSSupport

• 
  Kash (@misterrpink1) reported 14 minutes ago

  @AWSSupport My Athena + Glue was failing my status check. Are you sure this wasn’t down a few hours ago?

• 
  Simon (@Simonnnnnnnfox) reported 20 minutes ago

  @mcbc @WNBA @awscloud Are you mentally slow? I haven’t “gone from” anything lol 1. It doesn’t use an equation (not math) 2. I said Diggins is an OUTLIER (never said she’s not a PG) (1/10) 3. Yes, google as in the WNBA. If you google “how is gravity stat tracked” google will take u to the W page

• 
  Matthew Garrison (@GlowieRag) reported 22 minutes ago

  @AWSSupport I have a 7 day old unassigned support ticket for a billing refund, and my auto pay declined due to suspected fraud because the cost was so much higher than normal. This is pretty urgent, id like to fix this and pay you! Case id 177973340000997

• 
  Radu ⳩ XiXi ☦️ ☸️ ☯️ ⚡️ ⭐️⭐️ (@LizardWizardBTC) reported 23 minutes ago

  @BrenBuilds @awscloud The main problem Big Tech companies face is how to not break millions of customers. They already have distribution pipelines and getting an MVP out fast has never been a problem for them. That’s a startup problem, not an Amazon problem.

• 
  Rickkk (@rickzzzzr) reported 25 minutes ago

  @BrenBuilds @awscloud i agree with more people creating more MVP's the economic pie is increasing but the problem was never about writing software i mean anyone can learn that in like 1 month but humans usually don't think out of box and has this sheep like mimicking nature so it's futile

• 
  1828 (@DEVELOPER1828) reported 26 minutes ago

  @AWSSupport my cognito users can sign up but require verification after sign up. if they close the verification page they are unable to sign in with the credentials they set. resetting password doesn’t work either, every code that gets sent to reset password is “invalid”.

• 
  leapfrog (@leapfrogcl) reported 30 minutes ago

  AWS Amazon is down. 😱🤯 @AWSSupport

• 
  Eduard Lugo (@eduardlh) reported 31 minutes ago

  @AWSSupport Hi @AWSSupport, 🚨URGENT: Is there anything else I can do to expedite this process? A phone number I can call, or an email address? My business has been down for 48 hours. Please advise.

• 
  Duke of Idanre Kingdom (@Alexander474335) reported 41 minutes ago

  @AWSSupport I went to the issue section and I already have my issue reported in the past. I didnt want to duplicated issue.

• 
  June Kwan - Bali (@junekwan6688) reported 42 minutes ago

  @awscloud @OpenAI If I choose 2 different kinds of AI (Chinese & American) in 1 device, will you 2 fight and not supporting each other or maybe try to fail each other down???

• 
  AntDracula (@ant_dracula) reported 42 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.

• 
  Teri Radichel #cybersecurity #pentesting (@TeriRadichel) reported 45 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 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.

• 
  Shawn Jots (@shawnjots) reported 45 minutes ago

  @awscloud been trying to create an account over 36 hours ago but I realized your sign up process is broken. Getting this error: response: { "message": "Failed to start DIVA SMS PIN verification".... Can you help?

• 
  VarmıGol (@VarmiGol) reported 47 minutes ago

  @AWSSupport Hi @AWSSupport, thanks for prior help. Sent a DM about urgent Kiro issue still no human reply after days. Could you check and escalate please?

• 
  Ameya (@lambatameya) reported 47 minutes ago

  @awscloud That's true for all software. More software can slow you down.

• 
  ProAmPete (@ProAmPete1) reported 48 minutes ago

  @AWSSupport @DiegooUA_ I am having the exact same issue, except support has inexplicably left my tickets in unassigned status for 3 months. I verified my identity and they in turn suspended and threatened to delete my account, and never even gave me the call I requested MULTIPLE times.

• 
  Laurent Cligny (@lcligny) reported 48 minutes ago

  @awscloud Skill issue ?

• 
  Arroiss (@arroiss12) reported 49 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

• 
  Hot_Tamales (@tama96420497) reported 51 minutes ago

  @IAGovernor @awscloud @Cognizant Terrible optics. Read the room.

• 
  Crypto Pulse (@x1cryptopulse) reported 53 minutes ago

  @awscloud @OpenAI Context retention across multi-step agent workflows is where the real scaling issues show up. 🤖

• 
  Tiffa (@TiffaJessi) reported 55 minutes ago

  Yo @awscloud u guys should totally idk maybe fix servers with @PlayApex because they’re TERRIBLE!!!!!!

• 
  Ronald van Loon (@Ronald_vanLoon) reported 55 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

• 
  Skunky (@skunky) reported 1 hour ago

  @Marc269681 @awscloud These lying morons are covering for their mismanagement and poor decision making by blaming a toolset. It's like blaming photoshop for the fact that your are a terrible photographer.

• 
  Ordo Amoris ⛪️ 👩‍❤️‍👨👶👧🇺🇸🌎 (@OrdoAmorisVerus) reported 1 hour ago

  @IAGovernor @awscloud @Cognizant This is a really bad decision. Indians only hire other Indians. You’ve put 200 Iowans out of work and given those jobs to H1b holders. Bad, bad move. Fix it.

• 
  Charu (@Charu_Sethi) reported 1 hour ago

  This week the same problem showed up in two places that don't talk to each other: Coinbase wrapping AI trading agents in an SEC-registered advisory, and x402 charging AI agents per request at the AWS edge. Both are solving authorisation-within-limits. Neither is interoperable with the other. Step back and the pattern is clear. Agentic settlement is becoming table stakes. x402 now runs through AWS CloudFront and WAF, settling USDC on Base and Solana via EIP-3009 in around 200ms, with 169M-plus cumulative payments. Mastercard's Agent Pay for Machines handles multi-rail M2M settlement. Coinbase is putting agent execution inside a registered wrapper. The rails are getting solved. What is not getting solved is the layer above them: a portable, revocable spending mandate that binds an agent's authorisation to a verifiable human or corporate entity and travels across rails. ERC-8004 gives agents identity and reputation, not spending authority. The agent-authorisation drafts (ERC-8118, 8184, 8150) are all single-principal or payment-channel scoped, and none has advanced. An agent authorised inside Coinbase's advisory and an agent paying through x402 at the AWS edge are governed by completely separate, non-portable models. That's the gap. The structural question worth testing: do the platforms each standardise their own proprietary mandate model, leaving on-chain rails competing inside someone else's walled authorisation garden, or does a neutral cross-rail mandate primitive finally emerge? Whoever ships the portable mandate owns the layer everyone else has to build against. @coinbase @awscloud @Mastercard #AgenticPayments #x402