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 (50%)
• Errors (33%)
• 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	30 days ago
Chennai	Website Down	1 month ago
Point Pleasant Beach	Website Down	1 month ago
Little Rock	Errors	1 month ago
Atlanta	Website Down	1 month 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:

• 
  Tanner Scadden (@TannerSDev) reported 6 minutes ago

  @awscloud please help us asap your team suspended our account at the same time we got an email saying we have two weeks to address a problem with our root account. Cloudflare is down for us, and EC2 won't provision new instances. Our app is down. We serve hospitals. Please

• 
  Tiffa (@TiffaJessi) reported 7 minutes ago

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

• 
  ahmed (@ENGA999) reported 7 minutes ago

  @VodafoneGroup @awscloud @VodafoneBiz When does customer service in Egypt actually help customers? The app is terrible when it comes to roaming services. Every time I travel abroad, I struggle to activate or manage any service, and there are no real solutions. The only thing that works perfectly is charging customers

• 
  Astra (@0xAstra) reported 13 minutes ago

  @awscloud AWS is honestly a massive disappointment. You sign up, then discover basic customer support is locked behind a paid plan. Isn’t support supposed to be the most basic part of a cloud service? I didn’t pay for premium support, so a simple SES email permission request has been ignored for three days. I genuinely don’t understand how this is the world’s No.1 cloud provider. This experience is terrible.

• 
  🇺🇸 End H1B F1 OPT TN E3 O1 L1 I1 H4 all NIV 🇺🇸 (@slmimorgan) reported 16 minutes ago

  @IAGovernor @awscloud @Cognizant You need to stop down you treasonous monster. You are elected to serve we the American people. Not Cognizant or Indians. Shame on you.

• 
  Garratt Campton 🍄 (@gcampton) reported 16 minutes ago

  @AndrewChamb @awscloud It actually wasn’t able to do that, it could create new repos and PRs but not analyse and fix your own code. It would get downgraded. Sounds like you never used it.

• 
  ProAmPete (@ProAmPete1) reported 20 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.

• 
  Amit Khera (@ai_amitkhera) reported 25 minutes ago

  @MatthewBerman They need not to fix other system vulnerabilities. They have to fix their system from its own. Now its clear that Amazon @awscloud is not secure as pretend to be. Now a clear risk is there when you are hositng your data in the system.

• 
  Sir Edward VonTinklebum (@EdwardTinklebum) reported 27 minutes ago

  @IAGovernor @awscloud @Cognizant I hope those same employees charge you double when you have to hire them back to fix the vibe-coded slop you just bought.

• 
  Prithvi Jadwani | AI SEO | GEO | REDDIT SEO | GMB (@Prithvi_Jadwani) reported 27 minutes ago

  @aselipsky @awscloud 15 years is a long time to spot the same bottleneck. What's the fix for hyperscalables now, then?

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

• 
  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

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

  @Chiraq100x @Anthropic @awscloud I mean I can check this after every prompt but that doesn’t help that I’ve already been billed for the tokens and have to pay to fix it if I want it to be correct.

• 
  Ann O'Leary 🙄🤬 (@Panda6) reported 33 minutes ago

  @goodreads Hi - honest question - why is your site so very slow to load?? Can’t you get some @awscloud juice behind it??

• 
  Matt Adams (@mattflashuk) reported 36 minutes ago

  @AWSSupport 40 days for a billing issue. Can you look into this please.

• 
  Ani (@nomad_on_run) reported 42 minutes ago

  @awscloud my ticket is open for more than 24hrs and nobody is yet assigned. I understand there is no SLA for basic support, but need assistance as i’m getting quota error even for a basic machine setup with 2 vCPUs

• 
  Rickkk (@rickzzzzr) reported 42 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

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

• 
  Alex 🇨🇦 (@leeman24) reported 47 minutes ago

  @ant_dracula @GyuMusang56418 @awscloud I will agree on support falling off for their neglected services. Any time I interact with Textract/Comprehend support, they take 1+ hrs to join the chat and my issue is always a bug they got to reach out to the product team for. I also agree senior engineers will be good at AI.

• 
  Andrew Rodriguez (@andrewvr303) reported 48 minutes ago

  @Polymarket Glad I just got $10K in credits from @awscloud, hope it's made available on there quickly (still having issues getting Opus 4.8 to work, seems to be gated for whatever reason)

• 
  Piyush (@iPiyushKashyap) reported 49 minutes ago

  @awscloud Interesting take from the same company that built Kiro. Either AI-generated code is useful enough to invest millions in, or it slows teams down. Pick a lane.

• 
  Joyfulwood (@JoyfulWood) reported 49 minutes ago

  $GXAI 1.47 Dip SL under 1.39 Ran big on news this morning, brought down to support at 1.45. Trying for a second run. PT 1.75/1.89/2/2.15/2.3+ Gaxos Secures Additional Funding from Amazon AWS to Accelerate AI Sales Platform Development

• 
  Randall Hunt (@ranman) reported 50 minutes ago

  @pkyanam @QuinnyPig @AWSSupport Your account is probably flagged for fraud risk - any billing issues in the past? That's what seems to happen when people can't access the models automagically

• 
  praveen A (@praveen_hacker) reported 51 minutes ago

  @AWSSupport @AWSSupport Hello AWSSupport, The issue has not yet been resolved. Could you please assist in resolving it as soon as possible?

• 
  Jeff (@CensoredJeff) reported 52 minutes ago

  @IAGovernor @awscloud @Cognizant this is just one problem with women in positions of power. you’ll sell the country out and think you’re doing a good thing. repeal the 19th.

• 
  Bryce Crawford 🐱 (@bryce_meow) reported 54 minutes ago

  Have @awscloud service problem Contact AWS support "This response was generated using generative AI. You may need to verify responses." * Hallucinates * * Obvious mathematical error * Peak comedy

• 
  Matthew Garrison (@GlowieRag) reported 58 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

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

• 
  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

• 
  David Perlov (@DavidPerlov) reported 1 hour ago

  @awscloud The company selling the compute says slow down. Noted.