Amazon Web Services 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:

• 
  Joy | 🔥 (@JoyKingdomx) reported 6 minutes ago

  As we all know, cloud outages are not a new topic here. But what is changed is how many products now depend on the same infrastructure. A few years ago, an AWS outage mostly affected AWS customers. Where today one infrastructure issue can ripple across AI apps, APIs, developer tools, streaming platforms and payment services. That is the downside of concentration. We have seen @awscloud outages impact millions. We have also seen @OpenAI outages pause production apps because entire inference pipelines depended on a single provider. It is not the outage that matters - it is the dependency behind it. That is the reason why decentralized compute makes sense. Instead of relying on a single cloud or region, @ionet distributes compute across a global network of GPUs in 138+ countries. No infrastructure is immune to failure, the goal is to ensure one failure does not become everyone's failure.

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

• 
  jd42 (@jdonovan42) reported 12 minutes ago

  @DarioCpx Pls recalculate considering the massive clouds the AI revs sit on. Each $1 in AI attaches $1.5-2.5X attached cloud biz and your down to 30-45% of revs. Then as open wgt models gain apply the 100% revenue retention vs. 60% on frontier and look at EBITDA % from frontier is 10-15% max. But nice try ;) No doubt Anthropic and OpenAI both stimulate demand for Amazon AWS. It creates 2x the cloud biz than it does the direct AI biz. So why not count the full picture of things vs just the #'s that fit one narrative.

• 
  X anonyn (@OmrX304) reported 14 minutes ago

  @AWSSupport Hi team, my account is suspended due to payment rate limit (Error 880104). I've sent a DM with my Case ID & details. Could you please escalate this to the billing team urgently? Thanks

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

• 
  Jonny Castles (@jonny_castles) reported 25 minutes ago

  Not seeing much on here, but seems like a massive outage across platforms? Looks like all AWS linked? @awscloud

• 
  BOB-DO-THEM (@osangesua) reported 26 minutes ago

  This is a blatant lie intended to mislead the electorate. The glitch synchronisation in the BVAS is the reason he won't effect the upgrade because if an upgrade is carried on the BVAS, the entire calibration of glitches will disappear and the fear that @awscloud may have disabled or blocked the application that allows them to manipulate the BVAS is the reason for this unprovoked lies

• 
  Vinit Upadhyay (@vinitcodes) reported 26 minutes ago

  @kirodotdev @awscloud @AWSSupport issues still persist i didn't got any update

• 
  Milan Jovanović (@mjovanovictech) reported 26 minutes ago

  @mrwcjoughin @awscloud @Azure I doubt this is a compute issue, looks like a bottleneck from past choices coming to bite you

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

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

• 
  Somers (@jake__somers) reported 29 minutes ago

  AWS keeps charging me 1000x what it should be for inference I try to use the new "generally available" Grok 4.6 Prompt caching doesn't work at all I spend $1.9 worth of inference testing caching I see my AWS bill is now $3400 This was an issue months ago as well. @AWSSupport

• 
  Brad (@beeradmoore) reported 30 minutes ago

  @QuinnyPig @awscloud I made a thing that posts in Slack when a new AZ goes live. It has pipped up twice in two days. I thought that was odd, it’s sat silent for so long and now twice in two days! Turns out it’s broken and will just repeat until I tell it that yes I know about eu-west-2d

• 
  Jacklyn Taylor (@Ronindrake2) reported 32 minutes ago

  @awscloud @AmazonHelp @amazon Yo, can any of yall explain why a review that gets flagged for "community guidelines" refuses to tell you what the issue is? Like yall's bot goes "it violates rules!" But cant tell me what part? It obviously had to note what the issue was...

• 
  Rohit Dhawan (@rohitdhawan26) reported 36 minutes ago

  @AWSSupport @awscloud I send a DM on 17th july with same issue but no one responded to that.

• 
  WPBeginner (@wpbeginner) reported 37 minutes ago

  You have spent months building your WordPress site. What happens the day it suddenly goes offline? 😱 It happens all the time. We have heard several scary stories. A plugin conflict, a bad update, or a security breach can wipe out your complete website without any warning. The scary part is that most site owners assume their host has them fully covered, right up until they actually need to restore. We have tested countless backup tools on our own projects, so we put together the exact methods we trust to keep a site safe. Here is what you will learn: ✅ Pick the Right Method: Compare backup plugins, host backups, and manual cPanel or FTP so you know which fits your skill level. ✅ Back Up the Full Site: Save your database, themes, plugins, and uploads together so you can restore everything, not just your posts. ✅ Automate It With @DuplicatorWP: Schedule daily or weekly backups and send them straight to the cloud so you never have to remember. ✅ Store Copies Off Your Server: Keep backups in Google Drive, Dropbox, or Amazon S3 so one server crash never takes your site and its backup at once. ✅ Restore in Minutes: Use a disaster recovery link to bring your site back even when it is completely broken. Ready to protect all that hard work before disaster strikes? Read our complete step-by-step guide from the link in the comments 👇 (Link is in the thread below)