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:

• 
  June Kwan - Bali (@junekwan6688) reported 6 minutes ago

  @awscloud @OpenAI If I choose 2 different kinds of AI (Chinese & American) in 1 device, will you 2 fight and not supporting each other or maybe try to fail each other down???

• 
  Astro Kanu (@AstroKanu) reported 8 minutes ago

  @awscloud @AWSSupport you need to give me an e mail address to write to as I’ve no option to log into AWS as your team has deactivated my account. Now it’s time to take this issue seriously as I’ve been raising it patiently for 36 hours while my live project is disrupted

• 
  Chocobo (@chocobo2837) reported 11 minutes ago

  @awscloud Amazon complaining to the US government about the lastest frontier model and getting it shut down.

• 
  esyx (@esyx0) reported 16 minutes ago

  Today i got email from AWS that they can't approve my request for **** SES no explanation at all, only generic "During our evaluation, we identified some concerns that prevent us from approving your request. Due to security reasons, we are unable to provide specific details about our assessment criteria." has anyone had to deal with this? All i wanna use the SES for is transactional mails like verification, reset, notifications about your account etc @awscloud @AWSSupport Can you please help? At least tell me what's wrong so i can fix it, i genuinely have no idea

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

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

• 
  John Mason 🐝 (@john_mason_) reported 30 minutes ago

  @wattreach @AWS @awscloud Good luck, AWS Support has been going down the tubes.

• 
  Dude 3.0™ (@NamelessDudeZA) reported 31 minutes ago

  This is a real threat, WebAfrica was running their web hosting billing and support on WHMCS. So for the past few months WHMCS software has been under attack from hackers. My own server was attack through SQL injection of users fortunately I had to isolate and migrate to fresh new server provided by Amazon AWS.

• 
  Astro Kanu (@AstroKanu) reported 35 minutes ago

  @awscloud @AWSSupport it’s been more than 4 days inspite of high billing cleared no access to my account nor able to login - live project disrupted- how are you resolving this ?? #aws

• 
  Astro Kanu (@AstroKanu) reported 36 minutes ago

  @awscloud @AWSSupport if u don’t resolve this on urgent basis I’m going to start telling my clients who have paid for my services- which are down because of you to start writing to u to claim a refund - you cannot disrupt a live project and be so causal about this #aws #awsscam

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

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

• 
  angelmilkcry (@alina_aalx) reported 41 minutes ago

  @awscloud Maybe it’s your inability to adapt. You are used to development being a slow and manual process…that's how you sell more of your services

• 
  Cornfields1 (@CornFieldsOne) reported 43 minutes ago

  @IAGovernor @awscloud @Cognizant This is extremely disappointing, selling out hard working IOWANS for Indians. Terrible. DOJ needs to step in

• 
  Mashood tried Ops (@fromcodetocloud) reported 45 minutes ago

  🤯AWS S3 Outage (2017) : In 2017, a routine maintenance task inside AWS turned into one of the most famous outages in cloud computing history. An engineer working on Amazon S3 executed a command with an incorrect parameter, causing more servers to be removed from service than intended. What followed was a chain reaction that affected thousands of websites and applications across the internet. The outage lasted around 4 hours, but the impact was far bigger than the downtime itself. Companies suddenly realized that services they considered independent were actually relying on the same underlying cloud infrastructure. Slack, Trello, Quora, and countless others experienced disruptions because a critical dependency had failed. The most interesting part? The incident wasn’t caused by hackers, hardware failures, or a sophisticated cyberattack. It was caused by a routine operational task performed by a human.

• 
  L'éclaireur (@apex_leclaireur) reported 47 minutes ago

  @luckychappy_ Only in your head, reality is they had a 6 year contract with a server provider and then switched to amazon aws servers. So your claims are bs. I studied computers and you dont understand anything. All battle royal games use 20hz servers that dont fail but your connection does