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 (29%)
• Sign in (18%)

Live Outage Map

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

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

• 
  🇿🇦CN - Cracking News🇵🇹 (@walter_mashala) reported 29 seconds ago

  @awscloud @luis_usaa It’s good but will only server those who could afford using them, the world has more poor people than rich the people therefore it will work for the few.🤔

• 
  Alex 🇨🇦 (@leeman24) reported 3 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.

• 
  Wagecuck Liberator (@WagecuckR) reported 3 minutes ago

  @chainlink @amazon @awscloud Slow news day

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

• 
  Astra (@0xAstra) reported 6 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.

• 
  Hershal Rao (@Hershal0_0) reported 8 minutes ago

  @awscloud finally, i can keep my embarrassing "fix later" comments strictly internal.

• 
  Radu ⳩ XiXi ☦️ ☸️ ☯️ ⚡️ ⭐️⭐️ (@LizardWizardBTC) reported 9 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.

• 
  Alexa Web3 (e/acc) (@alexabelonix) reported 11 minutes ago

  @aiven_io @serenavc @awscloud this is why more outreach doesn’t always fix it 🤝 let's be mutuals!

• 
  Eduard Lugo (@eduardlh) reported 14 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.

• 
  oraclee.btc 🧠 (@oraclee_xyz) reported 15 minutes ago

  @awscloud @OpenAI but can it fix ****

• 
  Wildo Tango (@xx01010xxc) reported 19 minutes ago

  @awscloud please add disconnect for aws-mcp, I've spent 6hrs. to re-login with new aws account with in project scope, instead of global. @ClaudeDevs

• 
  Tamara Baxter (@baxter_tam80462) reported 19 minutes ago

  @awscloud @OpenAI Wannabe student. Social media guru. Food scholar. Problem solver. Internet maven. Amateur beer ninja. Hipster-friendly music fanatic. uGzJ8E

• 
  Sridhar Katakam (@srikat) reported 21 minutes ago

  @AWSSupport 39 hours since my email reply and still waiting. There's not a single human reply so far regarding the billing issue.

• 
  DIWhyCoder - ⌨️ 🇺🇸 (@diwhycoder) reported 23 minutes ago

  @awscloud AWS running out of server space confirmed.

• 
  Bryce Crawford 🐱 (@bryce_meow) reported 25 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

• 
  Vivek Varia (@vivekvvaria) reported 25 minutes ago

  Not able to login, I am planning to register for AWS Certified Cloud Practitioner. @awscloud

• 
  Rudra Narayan Mohapatra (@rnmohapatra46) reported 26 minutes ago

  @awscloud Hi, I took the AWS Certified Solutions Architect – Associate exam about 3–4 weeks ago, but my digital badge is still not showing up on Credly. Could you please help me resolve this issue? Thanks in advance.

• 
  Hershal Rao (@Hershal0_0) reported 29 minutes ago

  @awscloud anything to avoid hugging a server rack in a cold data center ever again

• 
  AI Inc (@AiTesty5) reported 30 minutes ago

  @awscloud Normal people call this „skill issue“… come one AWS, you’re selling us this crap and then talk bad about it?

• 
  School Reading List (@SchoolReading) reported 31 minutes ago

  @Cloudflare @CloudflareHelp @awscloud We've also referred to the same issue in Case #02165422

• 
  RationalJames2776 (@RationalJames76) reported 38 minutes ago

  @IAGovernor @awscloud @Cognizant Your systems will be spaghettified and will need 10x the staff to support and fix. Source: seen it irl

• 
  Shawn Jots (@shawnjots) reported 38 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?

• 
  ThriveCart (@ThriveCart) reported 42 minutes ago

  @CivilEngAcad @TheWAHWoman Hello, Amazon AWS has triggered an unscheduled update, likely mitigating a wider issue on their end. This is impacting some carts. We expect AWS to resolve very shortly. We will provide an update when it does.

• 
  Kingdom of ElviSpeare (@ElviSpeareTV) reported 44 minutes ago

  All down: DoorDash. Spotify. GoDaddy. Verizon. Uber Eats. Amazon AWS. Did someone cut the under water wires half way around the world? Possibly others.

• 
  Amit Khera (@ai_amitkhera) reported 45 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.

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

• 
  Charu (@Charu_Sethi) reported 49 minutes 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

• 
  Ahmed Fouad (@ahmedfouaddev) reported 50 minutes ago

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

• 
  Jay (@jaycansea) reported 51 minutes ago

  @awscloud It slows everything down and is a disaster so far.

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