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 (71%)
• Sign in (14%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Boca da Mata	Errors	3 days ago
Township of Evan	Website Down	18 days ago
New York City	Website Down	21 days ago
Ciudad Jardín	Website Down	2 months ago
Kyiv	Sign in	3 months ago
Chennai	Website Down	3 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:

• 
  Dan Lynch (@danlynch) reported 13 seconds ago

  @QuinnyPig @awscloud I need to sign in with LEGO 😎

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

• 
  𝙵𝚊𝚒𝚣𝚎𝚕 𝙿𝚊𝚝𝚎𝚕 ⚡️ (@FaizelPatel143) reported 4 minutes ago

  “AI will solve real problems, for the continent.” #AWSSummit2026 @awscloud

• 
  Harun R. (@harundotdev) reported 10 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.

• 
  Aramis Official (@AramisToken) reported 12 minutes ago

  @NoaSanderskyo7 @F1 @awscloud He was slow af, actually

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

• 
  Kartik Jain (@kartikjain0101) reported 13 minutes ago

  @awscloud you guy has lost your mind. payment got missing so team told me they will raising the request. account got hold, we have 250K unused credits, and now they are not initiation the account. wtf. our whole production is down.

• 
  Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported 15 minutes ago

  @AWSSupport Live production server is down. Case 178699777500302 (Account Reinstatement) filed with a callback requested — call failed to initiate. Earlier case 178699433100264 still unassigned. Need urgent help, can someone DM me?

• 
  Brian Porter (@kbporter) reported 15 minutes ago

  @amazon @awscloud @AmazonHelp why do I have to continually contact you on social media for issues with your service? Why is your customer service online “help” so bad? $5 credits for delayed orders for a service we pay for is horrible!

• 
  Adam Peterson (@_adam_here_) reported 16 minutes ago

  is @AWSSupport down?

• 
  Arian van Putten (@ProgrammerDude) reported 17 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?

• 
  Sam (@samraysap) reported 18 minutes ago

  @awscloud @Ankushk73325131 Not surprised that H1-B Amazon is highlighting a Non-American. And they wonder why a multi trillion dollar company is having errors like charging quadrillions of dollars to their users. Hire American

• 
  Felipe Rojas (@FipeRojas) reported 18 minutes ago

  @AWSSupport as root admin of a management account in Chile, your system failed to issue our statutory VAT invoice despite our tax settings were configurated according to your mails and RUT verified since june 2. Already 4 open cases without answer. ID 178524912400362

• 
  Adam Peterson (@_adam_here_) reported 20 minutes ago

  @AWSSupport Even the AWS health page was down. Total AWS system downtime for 12-13 minutes. AWS appears back now.

• 
  Anjishnu Ganguly (@Anjishnu46) reported 23 minutes ago

  @AWSSupport @awscloud, please don't reply again just to say this was shared internally. Assign someone who can actually look at the account, explain what's blocking it, and fix it.

• 
  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

• 
  Anjishnu Ganguly (@Anjishnu46) reported 23 minutes ago

  Hey @AWSSupport, Our Case 178452910500907 is still not resolved, and we've been left waiting without any meaningful update. Because of this, we're also unable to apply for AWS Activate, which is directly impacting our business operations and slowing down our workflow. This delay is becoming unacceptable. Please look into this urgently and help resolve it as soon as possible.

• 
  GamerUP (@GamerUPGaming) reported 29 minutes ago

  @TheRavenHelm man... are you detective seeds right? this is a new profile name ? whatever.. the "digital only direction" was announced more than 3 weeks ago.. not last week.. PSN servers are hosted by Amazon AWS, and amazon AWS had some disruptions today, they already solved the issue.

• 
  TeeBeeCTO (@TeeBeeCTO) reported 31 minutes ago

  Setting up a new AWS account @awscloud … and get non stop errors on set up. Looks like their vibe coding dystopia worked… were all going to die because SkyNet will have error pages that end up giving us all death by error page. Amazing work… @JeffBezos !!

• 
  ErinE (@WhoaNowNelly) reported 33 minutes ago

  @DRiceHockey @WNBA @awscloud Same applies to all their stats. Their PRA is gonna go down too. That's the nature of injuries. Makes it harder for the individual, but does not increase the difficulty of the actual shot itself.

• 
  Adel Bucetta (@adelbucetta) reported 36 minutes ago

  @Deeen_Codes @awscloud @devpost the real unlock here isn't just solving the hackathon prompt but figuring out what problems to automate first

• 
  mark seery (@140ismymax) reported 38 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

• 
  The Trading Guy (@thetradingguy_) reported 42 minutes ago

  @AWSSupport , got no replies on this upon follow up message. Please look into it. Why is it so tough to resolve an issue?

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

  @Cloudflare @awscloud Fix human verification

• 
  Maurizio Santamicone (@santamm) reported 44 minutes ago

  @awscloud And while you fix it, you can credit us for those amounts.

• 
  Base Builder (@basedbuilder_io) reported 52 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.

• 
  sof ࿔˚⋆ (@sophia_ray_17) reported 55 minutes ago

  @awscloud until the cloud has a power outage and i can't get into my car

• 
  Clem ent (@clement___10) reported 57 minutes ago

  Self hosting your email server is something that Is very tricky and I still can't grasp till today. The craziest part is not the setup but managing the email server reputation. I rather pay @Cloudflare or @awscloud.

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

• 
  ❤️‍🔥ViBe GuY_PrinCe😉 (@777PrinceFreaky) reported 60 minutes ago

  Amazon has very poor service in Warranty and Claim Procedure To Customer fix this for me soon @amazonIN @awscloud @AmazonHelp