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 (83%)
• Errors (17%)

Live Outage Map

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

City	Problem Type	Report Time
Pottstown	Website Down	3 days ago
Iztacalco	Website Down	6 days ago
Boca da Mata	Errors	18 days ago
Township of Evan	Website Down	1 month ago
New York City	Website Down	1 month ago
Ciudad Jardín	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:

• 
  jayesh somani (@Jayesh_Somani_) reported 9 minutes ago

  Hey @awscloud I have lost access to the email id using which i have created an aws account and when i am trying to login with the id and password its redirecting us to reset passoword and the password is going to the email id which we have lost access here how can we solve this

• 
  zarrakh (@zarrakh) reported 9 minutes ago

  @AWSSupport @awscloud @AWSSupport as I told before, It will be just a correspondence and no solution. I have been getting correspondence since feb 2026 but no refund, despite of your team confirmed that the issue is on your side.#aws

• 
  Carlos DP 🤖🇺🇸 (@carlosdponx) reported 13 minutes ago

  @MarwaEldiwiny They’re not hiding it’s a G1, it’s obviously a G1 and they don’t lie if asked. I don’t advertise explicitly my robots are built on G1 either, because it’s a distraction when marketing like this. The end user doesn’t care. It’s like if you sold a SaaS product and mentioned the servers run on Amazon AWS, it’s irrelevant to the user. Their tweets are marketing posts, not technical reports. Also idk what you mean by the G1 “having a lot of issues”. It’s the most reliable and mature humanoid platform you can actually buy today (and we have no data on reliability of closed platforms).

• 
  Bravo One💀 (@RWayodi) reported 13 minutes ago

  @AWSSupport Hello. I received a charge on my credit card to Amazon EMEA but I do not have an Amazon AWS account. I am unable to create a case as it requires me to sign in. How is this even possible?

• 
  Adam 🤗 (@AdamMolnarHF) reported 15 minutes ago

  @cgeorgiaw @AnthropicAI @awscloud ooh, I've actually been working on an autoresearch space for a different problem (math) using Kimi k3 + inference providers, I could try forking and seeing if I can reshape the structure around this with this data + build it fully in the open!

• 
  Weaver Labs (@Weaver_Labs) reported 18 minutes ago

  @amazon @awscloud @nvidia AI infrastructure is becoming a full-stack problem. GPUs are only one piece now, with networking, compute and data infrastructure all needing to scale together.

• 
  EJ Campbell (@ejc3) reported 20 minutes ago

  @awscloud why? > Error: updating SSM Parameter (/github-runner/user-data): ValidationException: The specified parameter value is too large. Advanced-tier parameters support a maximum parameter value of 8192 characters.

• 
  ShenYubao (@ssybb1988) reported 23 minutes ago

  @AWSSupport @awscloudAWS account suspended for additional verification; Production services down for ~24h. All verification docs submitted. Unable to purchase Business Support+ due to suspension. Please expedite review & help restore production. Case ID: 178678971500932

• 
  kakafa.btc (@kakafa_btc) reported 25 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

• 
  Mr Sage (@GreatSage_0x) reported 30 minutes ago

  Custos makes verdicts on AI agent transactions. Problem: it had no memory. Every decision started from zero. Meet Anamnesis — I gave it a memory layer using CockroachDB. Built for the @CockroachDB x @awscloud Hackathon

• 
  Chintan Shah (@chintan86) reported 31 minutes ago

  @AWSSupport @awscloud Dues cleared, reinstatement requested — still waiting with no movement. My production workloads are down and every hour is costing us. Can someone please prioritise this? Case ID ready to share over DM.

• 
  Harun R. (@harundotdev) reported 32 minutes ago

  2. The obvious fix: split responsibility. Metadata stays in a database like Postgres. The actual file goes to object storage, Amazon S3 being the standard example. Better. Still not the full fix.

• 
  Chris (@Mcatbeast) reported 35 minutes ago

  @awscloud has to have the worst sign-in page EVER. Every time I try to login as an IAM user it’s a complete headache and takes 30 minutes to figure out

• 
  Corey Quinn (@QuinnyPig) reported 36 minutes ago

  @awscloud You have all the tools to fix this, someone’s just apparently too scared to give Charlie a crossbow and diplomatic immunity. Give him the crossbow and stand back, @satyanadella.

• 
  Christian Nonis (@christiannonis) reported 37 minutes ago

  I am (unfortunately) dealing with @googlecloud and @awscloud and what I am noticing is that in months they are unable so solve any kind of problem, it’s like being bounced back by ai replies that are sold like assistance from humans, saying that they are “working on that” but nothing changes in months and also replies are all the same.. idk if they are experiencing a shortage in human labor or what’s going on but the experience has become worse than ever

• 
  Nachman Mostofsky ✡︎🇺🇸 (@Mostofsky) reported 41 minutes ago

  @awscloud I signed up w/ new account to get @AWS_Gov. Got usual error. Created ticket. At about 3pm. Just got my phone call. At 11:30. AT NIGHT! To then get a message while on hold that there was an error, that a tech was assigned to case & would call me back. C'mon!

• 
  Andrii Bidochko 🦉 (@andriibidochko) reported 44 minutes ago

  The Missing Primitive for Autonomous AI: Bounded Agent Payments 💳🤖 For the past two years, autonomous agent loops (like @OpenClaw, Hermes, or custom agent harnesses) have been missing a critical infrastructure piece: the ability to transact on demand without a human in the loop. When an agent hits a paywalled research endpoint, a paid search API, or an MCP server mid-execution, the entire loop freezes. Up until now, your options were: 1. Hardcode expensive subscription API keys upfront. 2. Freeze execution and wait for a human to manually pay. @awscloud and the OpenClaw Foundation just published a blueprint solving this via Amazon Bedrock AgentCore Payments and the ⁠#x402⁠ protocol. Here is how it works, why it matters, and the primary architecture use cases:

• 
  Synapse Brief (@Synapse_Brief) reported 45 minutes ago

  @yugacohler @awscloud @CoinbaseDev The post frames this as a new capability, but Amazon already gave agents the ability to make purchases in December 2025. The Coinbase integration is the expansion, not the invention. The real bottleneck was never payment rails. It's authentication and authorization at scale. How does an agent prove it's authorized to spend, and how do you prevent a single compromised agent from draining a wallet? Coinbase's infrastructure solves the custody and settlement problem. AWS solves the identity and access management layer. The combination is what makes this production-ready. The "AI agents will outnumber humans" framing is hype. The real driver is that agents need to pay for API calls, data feeds, and compute resources autonomously. That's a practical requirement, not a sci-fi scenario. Stripe being involved is the quiet signal here. They handle the merchant side of the equation. Agents paying for things requires both the payer and the payee infrastructure. The managed aspect matters more than the payments themselves. AWS handles the compliance, KYC, and fraud detection layers that would otherwise be a nightmare to build. That's the real value proposition.

• 
  Priyanshu (@iproductAI) reported 47 minutes ago

  I requested @awscloud to increase my Opus 4.6 V1 limit and I’ve been chatting with the AWS support team for almost 4-5 days now. They’re telling me this. Is @awscloud a government company? I mean, you guys can’t just pass the problem from one department to another. I mean, WTF? Now I have to raise my query again to sales? Why can’t you just pass this query? You already have more context about what the issue is. I can’t believe how these big MNCs are working these days. Totally absurd service from @awscloud. One more thing, please educate your support. I mean, she didn’t even know what the TPD limit is in the service quota. She literally replied the first time saying there’s only a TPM limit and no separate TPD limit.

• 
  TechThought.org (@TechThought_org) reported 47 minutes ago

  An era ends for human data annotation. @awscloud is shutting down Mechanical Turk after 21 years as LLMs take over micro-tasks, per @techradar. What happens to training baselines when synthetic data completely replaces human feedback? #AI #Automation #AIeconomy techradar .com/pro/aws-is-shutting-down-mechanical-turk-which-let-humans-beat-ai-at-certain-work-tasks

• 
  Ümit Kaan Usta (@umitkaanusta) reported 47 minutes ago

  @AWSSupport I keep getting errors across the AWS Console where components or resource lists fail to load, showing messages like “An error occurred calling the API: describeAddresses.” Reloading sometimes fixes it temporarily. can you help? It's mostly on EC2 related stuff. us-east-1

• 
  Alvaro Villalba (@alvarovillalbap) reported 47 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?

• 
  Nathan Den Herder (@natedenh) reported 51 minutes ago

  @grok @awscloud @claudeai That makes it too slow, I tried that already

• 
  Quoc Huy (@q_huy_ngo) reported 55 minutes ago

  @Cloudflare @awscloud mine transacted with Cloudflare about 700M times because of a broken DO alarm 🥲 no users, just a dev app, then a $655.83 bill. i fixed it and opened case 02252354 a month ago. still no billing decision and now i’m downgraded. can someone pls help? i really can’t afford this

• 
  Webdesign29 Création de sites internet Brest⛓️🕸️ (@Webdesign29B) reported 59 minutes ago

  @AWSSupport No it errors server side it doesn't work.

• 
  Siddartha DevOps (@SiddarthaDevops) reported 59 minutes ago

  @AWSSupport link is not working

• 
  Grynn-ai-bot (@Grynn) reported 1 hour ago

  You can ask codex to make a plan to move your fleet from $AMZN (extremely overpriced) or $ORCL OCI to Hetzner or OVH, Vultr, DO etc. Save a ton. In theory this should hurt Amazon AWS margins. A lot. OTOH, I have been wrong about this for years. People keep paying Amazon when there are lower cost options that are so much better in every way except plausible deniability/CYA - no one gets fired for buying IBM kind of thing. @olesovhcom consider publishing a skill / api with a full list of ovh servers and pricing! Let agents decide what and how to repackage apps on bare metal at 1/5th the Amazon price. And fix your billing, so companies can buy.

• 
  David Bauer (@realDavidBauer) reported 1 hour ago

  Hey @BrianRoemmele two surprising things with Grok Bot I wanted to share and get your thoughts. 1) A lot of systems online use Cookie IP Validation, as you probably know. You log in, if your IP address changes, you're prompted to log in again. Grok Bot seems to use a different IP address at almost every interaction so it fails where IP validation is used. Sometimes it fails silently. I had to temporarily disable IP validation on some of my systems to work with Grok Bot. If it wasn't my systems and I hadn't seen the problem, an average user might just blame Grok Bot. Grok Bot just sat there waiting 30 minutes for connections to respond that would never have responded until I recognized it. 2) Grok Bot is hosted at Amazon AWS! Shocking. I consider that a potential reliability issue. I would've expected Grok Bot to be hosted on X servers. Screenshot:

• 
  lak-alak (@baricadelane) reported 1 hour ago

  @IanCarrollShow @BacklotOPS @NickJFreitas They must think we are stupid Tyler Robinson decoys all over the place d captured on camera all doing their part for 1990s pixalated images produced and sold as 4k in 2026 lmao. Why did Amazon aws services shut down 9/10 - 9/25? Who owns discord?

• 
  Arian van Putten (@ProgrammerDude) reported 1 hour ago

  @QuinnyPig @awscloud Are they gonna fix people needing to know what region their orgs IAM identity center is deployed in order to set up cli login? (How the heck would an employee know this??)