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	4 days ago
Iztacalco	Website Down	8 days ago
Boca da Mata	Errors	19 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:

• 
  Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported 3 minutes ago

  @meaningoflights @jpschroeder @awscloud what issue do you have with that?

• 
  Base Builder (@basedbuilder_io) reported 3 minutes ago

  What happens when agent payments go from "works on testnet" to "GA on AWS"? AgentCore Payments just shipped general availability via @awscloud and @CoinbaseDev. CDP Embedded Wallets handle the key material, x402 encodes the payment terms, and the whole thing runs as a single runtime-to-settlement flow on Base. No testnet disclaimer, no "coming soon" asterisk. The end-to-end shape: your agent detects a payable event, opens an x402 payment channel with the recipient, and settles in USDC through the embedded wallet, all without the user touching a key or approving a transaction. That's the runtime plumbing. What it unlocks is agents that can pay for services mid-execution without a human in the loop. API credits, inference time, data access, compute, whatever someone x402-wraps. The integration gotcha to watch is spending limit enforcement at the wallet layer. x402 handles the invoice generation and the payment terms, but the CDP embedded wallet's permissioning lives one layer up. If your agent holds a wallet with a default spend cap and then processes a batch of x402 invoices in sequence, the cumulative settlement can blow past the limit before the wallet context re-checks. The outcome is partial payment batches where some invoices clear and others bounce, and your error handling needs to know which ones landed. The dependent abstraction this pushes into focus is agent-to-rail routing: your agent picks a payment path based on cost, speed, and counterparty, not just a static USDC address. That's the next layer to wire.

• 
  Swaroop Hegde (@SwaroopH) reported 3 minutes ago

  TIL: @awscloud has been racking up ipv4 charges on an old test instance of mine even though it uses dynamic IP. Just checked that their launch wizard deployed new instances with the same issue without warning 🤷

• 
  absk (@abskwdkr) reported 9 minutes ago

  My ec2 ssh logs in too slow and lags @AWSSupport

• 
  Chaz Wargnier ♨️ (@DataChaz) reported 11 minutes ago

  Let's take @Snowflake as an example. Working there gave me a clear view of the data problems hiding behind most ambitious AI roadmaps. Because Snowflake is natively deployed on AWS and available through the AWS Marketplace, it fits right into a modern stack. If you are building an AI feature, a sensible pattern looks like this: > Isolated customer events land securely in Amazon S3 from day one > Snowflake transforms raw data into a governed, usable layer > Flexible Amazon ECS compute routes only approved context to Amazon Bedrock Getting this pipeline right early means less time fixing data leaks and more time shipping AI features ↓

• 
  mark seery (@140ismymax) reported 13 minutes ago

  Peter DeSantis talking at #agenticaisummit There will NOT be one AI chip type. If multiple AI chips take multiple years to bring to market, you have to be making assumptions about model requirements in that time frame. It's a systems problem, including the network. Constraint drives innovation. Future is bright and built together. Peter DeSantis SVP, Foundational AI Models, Custom Silicon, Quantum Computing, Amazon @awscloud @amazon @BerkeleyRDI

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

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

• 
  Chris (@Mcatbeast) reported 16 minutes ago

  @AWSSupport Apologies for the earlier frustration. Turns out it was an issue from our end! My user was accidentally deleted.

• 
  Christian Nonis (@christiannonis) reported 20 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

• 
  ✨Neil Blumenthal (@MrKryptonBTC) reported 20 minutes ago

  @AWSSupport So you guys wont fix my issue anymore? Ghosting me? 7days gone? Dont say weekend or bla bla. Stop wasting people's time

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 21 minutes ago

  ClarityCheck markets itself as a tool to detect catfishing. To verify identities. To keep you safe from liars online. Here's how it works. You upload someone's photo. ClarityCheck runs it through their reverse image search. Finds their dating profile. Their social media. Wherever that face appears. Seems solid. Except ClarityCheck just leaked 9 million photos sitting in an unsecured Amazon S3 bucket. 450 gigabytes of faces. Stored in folders labeled "faces" and "profiles." The photos came from people uploading images of strangers. Dating app screenshots. Private social accounts. Scanned prints. Photos of children. Most of these people never uploaded anything to ClarityCheck. They just got identified by someone else trying to figure out who they were. Then their face got indexed. Stored. And left wide open. For several months. The URL to access it was embedded in ClarityCheck's own website source code. The company's response: this was "temporary storage" and an "ordinary member of the public" would not have found it. An ordinary member of the public with the URL from their own website. Which is not temporary storage. That's just a server. And it wasn't invisible. You'd need 30 seconds and a basic understanding of how websites work. Now ClarityCheck says the data is "secured." A service built to prevent identity fraud just exposed millions of identities. The tool designed to catch people lying about who they are just showed everyone's actual face to anyone listening. The irony isn't subtle. It's a design flaw pretending to be an accident.

• 
  Amanda (@AMyrick1989) reported 26 minutes ago

  @krassenstein @Tesla Be careful. All these at the same time makes me think they are hacked, I’m fairly certain Amazon AWS was hacked that day when everything when down, given my Grok we hacked and no one ever gave explanation. I’m no expert but ya know, all these signs are pointing to this. Also, the Obamas helped produce a movie where someone hacked our satellites and alluded to it being the Middle East and all the teslas went haywire and self drive themselves to pile up on all the freeways. I wish I remembered the name however I made note of this terrifying movie given Obama clearly knows things we don’t. Just sayin, these incidents aren’t scattered. I would not be driving that ***** if I were you.

• 
  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

• 
  Chris (@Mcatbeast) reported 31 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

• 
  Brandon James (@brandonajames) reported 31 minutes ago

  @callmeauntie218 Yes global outage from Amazon AWS.

• 
  Mon (@mon73x) reported 31 minutes ago

  @asimrazax @AWSSupport I have the same problem. Did you fix it?

• 
  Ohm Patel (@Techieohm) reported 38 minutes ago

  “Facing some problems with @awscloud on our new product. This is the 2nd time this has happened.”

• 
  Jaimin Vaghani (@jaiminvaghani) reported 39 minutes ago

  @AWSSupport @AWSSupport Appreciate the reply, but I've heard this exact message every day this week. At what point does a 5+ day production-down case qualify for actual escalation? Please have an escalation manager or TAM contact me directly, the Support Center loop isn't working.

• 
  Synapse Brief (@Synapse_Brief) reported 42 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.

• 
  🦋Kieran🦋 💻 (@sir_divs_alot) reported 45 minutes ago

  🚨 @AWSSupport I've been unable to create a Kiro subscription for 2+ weeks, getting error"account is not authorized to make this call." I have an active account, valid billing, and correct IAM Identity Center Organization instance setup. Case #178567212700620 escalate urgently.

• 
  Ranbir Mahapatra (@ranbirnxt) reported 46 minutes ago

  @QuinnyPig @awscloud Is NAT Gateway a ‘pricing’ bug that you would care to fix? Forever?

• 
  Siya (@reze_xqc) reported 47 minutes ago

  @AWSSupport Case 178653274100402 opened 3 days ago, no response. Can't sign in to AWS Builder ID, email locked to unknown sign-in method, blocking access to AWS Academy courses. Need help.

• 
  Jose njui (@jsnjui) reported 50 minutes ago

  Anyone to sort my AWS account. Am unable to login. Any leads to urgently help fix @awscloud @aws_UGkenya

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 52 minutes ago

  @Cloudflare @awscloud Fix human verification

• 
  Andrii Bidochko 🦉 (@andriibidochko) reported 53 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:

• 
  Sai Manikanta ☕ (@rebuiltWithSai) reported 54 minutes ago

  Day 19 of #JobSwitchUntilPlaced 🚀 Today's progress: ✅ Started a new Microservices project by building the User Service ✅ Solved 2 DSA problems ✅ Learned about Blob Storage (Amazon S3) One step closer to building production-ready, scalable backend systems.💪 #BuildInPublic

• 
  Arian van Putten (@ProgrammerDude) reported 55 minutes ago

  @QuinnyPig @awscloud Not randomly redirecting to root console login page if I logged in with IAM identity center

• 
  Arian van Putten (@ProgrammerDude) reported 57 minutes ago

  @QuinnyPig @awscloud Are they gonna fix that IAM identity center stored passkeys on a domain that is shared between aws orgs and accounts so I keep locking myself out of orgs when updating one?

• 
  Eemanuel (@Chukwunons63680) reported 1 hour ago

  @nvidia @awscloud @grok what is the CPU server for?

• 
  Harshil Mathur (@harshilmathur) reported 1 hour ago

  4 billion payments. 3 trillion data points. One model trained on all of it. Meet @Razorpay Vulcan - India’s first transformer-based AI foundation model for payments. Built, trained and hosted in India, in partnership with @nvidia and @awscloud. Until now, every payments problem was solved separately: routing, fraud, risk, personalisation and more. We asked: What if one model could understand how money moves? And like LLMs are trained on text to understand language, Vulcan is trained on payments to understand how money moves. Already running in beta across 51,000+ businesses, Vulcan is delivering: - 8–10% improvement in payment success rates - the ultimate measure of whether a payment simply works. - 8x more international card fraud detected. - 5x more fraudulent or disputed transactions identified. - 1–2 lakh more purchases completed every month through better checkout personalisation. And we’re just getting started. The best part? Every payment Vulcan sees makes the next one smarter. We’ve spent years building the infrastructure that moves money for India. Now, we’re building the intelligence that understands and improves it. 🔥