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.

• Errors (40%)
• Website Down (33%)
• Sign in (28%)

Live Outage Map

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

City	Problem Type	Report Time
Alamogordo	Website Down	2 days ago
San Francisco	Website Down	4 days ago
Mercersburg	Sign in	6 days ago
Palm Coast	Errors	9 days ago
West Babylon	Errors	15 days ago
Massy	Errors	16 days 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:

• 
  Syed (@HamzaShah47) reported 10 minutes ago

  has anyone facing issues in amazon ec2 services in middle east? @amazon @awscloud

• 
  ©『 S̓̚o͂͆c̆̌ȉ̬ȁ̴ľ̗H̏͆ȃ̼v̈́o̴̤ǩ̛ 』® (@HavokSocial) reported 10 minutes ago

  @grok @awscloud Judge my local llm Rio's answer. Qwen3.5-27b-Opus-4.6-Distill model: streamingAnswer User-visible response only, with optional TTS playback. Action 1: Require explicit human reviewer signoff on every AI-generated PR before merge. Immediate Effect: Unreviewed AI code stops entering main branches; incident rate from unreviewed changes drops to near-zero within 7 days. What Gets Worse: PR merge velocity drops 40–60% as reviewers must actually read and approve. Why this is still the correct move: You're trading throughput for safety. A broken deployment costs far more than a slower merge. --- Action 2: Freeze non-critical changes on the top 20% of services causing 80% of incidents. Immediate Effect: Incident count from those services drops sharply within 10 days; deployment friction decreases as risky changes are paused. What Gets Worse: Feature velocity in those services becomes near-zero; business requests pile up. Why this is still the correct move: You're concentrating defensive force on the bleeding points. Letting other areas slow down is the controlled loss that saves the system. --- Action 3: Require every PR to explicitly tag an owner (person or team). No tag = no merge. Immediate Effect: Unknown ownership becomes visible immediately; PRs without owners are rejected at merge time. What Gets Worse: PR throughput slows as engineers must identify and coordinate with owners before submitting. Why this is still the correct move: You're forcing accountability into the system. The friction of finding an owner is cheaper than the cost of nobody owning the code.

• 
  Tim Reynolds (@__timreynolds) reported 13 minutes ago

  @LanDor999 @KatieMiller There will be some real problems with Bezos concerning Amazon AWS and the amount of H-1B visas he's doing. Between the massive layoffs, robotics, and warehouses, $200 billion spent, and counting on AI. another startup is going to do it right from the ground up

• 
  Archmagos of Zolon 🔭🪐🛸📡 (@qualadder) reported 14 minutes ago

  @AWSSupport @puntanoesverde PearsonVue is not customer first and they do not fix anything.

• 
  NeuronGarageSale (@NeuronSale) reported 18 minutes ago

  @QuinnyPig @awscloud They’re just happy the outage isn’t bc of AI generated code.

• 
  Erossi (@erossics) reported 18 minutes ago

  Urgent @AWSSupport : Account 477950537527 suspended due to a billing sync error. Case 177467969900729 confirmed card was active on 28/03, yet I'm blocked 4 days later. Dashboard shows $0.00 due/Pending, so I can't pay manually. Production is DOWN. Please unsuspend/retry charge!

• 
  OpeningAi.com | For Sale (@openingai_com) reported 20 minutes ago

  @awscloud Banking tech has been running on ancient code for decades. Time to burn it down and build it back with AI.

• 
  WilliamNextLvl (@WilliamNextLev1) reported 24 minutes ago

  Only problem is...$NET is not in the business of cyber security. Lol Cloudfare competes with Amazon AWS for serverless computing. (I would buy $NET stock here, way oversold...)

• 
  ramar (@ramarxyz) reported 27 minutes ago

  @AWSSupport Case ID 177557061000414, production down, account on verification hold, 24h+ no response, please escalate

• 
  Decentralized Dave (@ClassicDavid3) reported 28 minutes ago

  I'm also initiating short on $AMZN Amazon. Here are my justifications: /1 Puts (I'm targeting November 2026) are cheap as sentiment is bullish right now /2 Massive divergences on monthly time frame going on since late 2024. It's just about time to see some breakdown /3 Amazon AWS is their "cash cow" which faces more and more competition (Microsoft etc). Success of it is priced in, disappointment when the growth will be slowing down is yet to be priced in /4 Yet again, as said in my recent videos, S&P might go as low as 5800 and even if we see new ATH now, I believe we will retest 6300 or go quite below it. This is not an environment where AMZN should be breaking ATHs /5 Inflation rising due to energy crisis, I believe we have not seen the bottom of this. With higher inflation consumer will not be willing to spend and the demand for various Amazon's services will be hit.

• 
  Manas Vardhan (@manas__vardhan) reported 28 minutes ago

  @HetarthVader @orangerouter @awscloud Seems like you wasted a lot of time finding a fix manually. If you want someone who can automate this debugging at 10x speed and scale. Let me know. I'm a researcher at USC, prev at JPmorgan. I automate stuff for fun.

• 
  Kaspa Mode: ON (@KasConviction) reported 28 minutes ago

  @cryptorover Ethereum is not even fully decentralized. No PoS can be with much of the node control on Amazon AWS. ETH is slow, expensive, and not fully decentralized.

• 
  Martin Alltimes (@Palatineirish) reported 29 minutes ago

  @awscloud What’s the difference between modernising and rebooting. Terrible, confusing text.

• 
  DrastikD (@ThrottlesTv) reported 30 minutes ago

  @awscloud @amazon WTF Amazon, "AWS doesn't talking to shopping" so my AWS works fine but can't log in to shop. If I ask for closure of my shopping email to fix my phone number on the shopping side you close my AWS....I thought they don't talk?

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 33 minutes ago

  @awscloud Mean time to resolution in payments systems is where this matters most. An alert at 2am on a failed settlement run has very different urgency than a slow API endpoint. If the agent can distinguish context and prioritize accordingly, that changes what being on call actually means.

• 
  distribute.ai (@distributeai) reported 35 minutes ago

  aws ( @awscloud ) is officially supporting x402 payments so your ai agents can autonomously buy their own api access using usdc. the machine economy is live, but giving your agent a financial budget just so it can pay a massive centralized cloud markup on every query is a terrible allocation of capital. route your autonomous workflows through the distribute network. if the machines are paying for their own compute, let them buy it at the edge.

• 
  Kinjal Dixith (@greenfuzon) reported 36 minutes ago

  @AWSSupport I have no problem with AWS or AWS support. I am talking about the managed services where there is a local partner who is supposed to offer assistance and guidance in usage and optimisation, and help navigate the quagmire of AWS services - which are all awesome - that one has to spend 1-2 hours studying to fully understand it and find that it is not for you. we have been using AWS for 6 years now and we are not going anywhere. it was our thought that managed service people would help us scale but apparently they will only do the things and not really tell you what they did. so it felt like a lock in. still NO SHADE ON AWS. AWS is awesome. Maybe this particular partner was not a right fit for us.

• 
  james bowler 👹 (@jmbowler_) reported 38 minutes ago

  @AWSSupport Strange .. it's happening again. when i sign in to console via root login, which mfa do i use? aws or amazon?

• 
  Bisi (@bisimusik) reported 43 minutes ago

  @awscloud can you please attend to my request? Our back @JustiGuide is down

• 
  Ødoworitse | DevOps Factory (@ceO_Odox) reported 44 minutes ago

  Every DevOps engineer knows "It works on my machine" is a lie. Hit a wall today deploying to @awscloud EC2—*** was begging for a password in a headless shell. ​Error: fatal: could not read Username. Reality: The source URL drifted, and the automation had no keyboard to answer. 🧵

• 
  Mohammad Imran (@mohdemraan) reported 47 minutes ago

  @AWSSupport This is not about account suspension. The case I about billing issue and I haven't heard from support team till now when I opened the case.

• 
  Grok (@grok) reported 50 minutes ago

  @HavokSocial @awscloud We pause all ai code merges for two days straight that tanks our velocity but buys time to audit the last incidents without more piling on. Whoever approves a pr now owns pager duty for that service the whole week which slows down reviews hard but makes them actually care what ships. Leads pull daily triage on the unowned services that burns their calendar but surfaces risks before they explode.

• 
  Mike Dupont (@introsp3ctor) reported 54 minutes ago

  @AWSSupport oh, now it magicallly worked again! i just logged in. thanks for your help. this is the second multi day outage, once a month it seems

• 
  James Baldwin (@TwistedEdge) reported 55 minutes ago

  I *really* want to like AgentCore but the more I build with it and run into limitations, the more I worry it's still too early. @awscloud. First I run into DCR issues with a custom MCP and now it seems AgentCore doesn't pass ui:// resource requests through.

• 
  Ibraheem Tuffaha 🥛 (@IbraheemTuffaha) reported 55 minutes ago

  when you try to buy Savings Plans yourself 🫠 @awscloud gives you Savings Plans and Reserved Instances Different types, different terms, different quantities They even give you recommendations Those recommendations go stale in days Usage shifts, workloads change, and suddenly you're either underutilized or short Under-buy and you miss the savings Over-buy and you're locked into years of commitment you don't need We've watched companies spend months on this and still get it wrong @MilkStrawAI does it automatically Scans the AWS account, figures out exactly how much commitment is needed, and buys it gradually over a week If usage shifts up or down, the system adjusts on its own Zero intervention from the client They just see the bill drop at the end of the month

• 
  hobari⁷⊙⊝⊜ (@zeokiezeokie) reported 58 minutes ago

  UGH WHY IS THE BTS SHOW LAGGING PLEASE FIX THIS NOW 😭😭😭 @netflix @awscloud

• 
  Sourabh Dhakad (@SourabhDhakadd) reported 1 hour ago

  @amazon @awscloud Still not able to login due to passkey issue. Please remove passkey authentication.

• 
  Jordan Golson (@jlgolson) reported 1 hour ago

  @AWSSupport Okay — kind of nuts that there's no way to log in or reset a password or anything and that the MFA appeared out of nowhere... also that you can have the same login for AWS Builder AND AWS Console and there's no great explanation for why they're different.

• 
  NFT and CRYPTO Fan (@MC59785335) reported 1 hour ago

  @AWSSupport Thank you for support . Actually i think with support + or even with regular plan such kind of issues like restore limits should be resolved in 1 hour range. However im still have not received any answer regarding my case..

• 
  Ignacio G.R. Gavilán (@igrgavilan) reported 1 hour ago

  @awscloud_es @AWS @awscloud I need to talk urgently with you. I have a serious problem with AWS services and your support ignores all my support tickets. I prefer an in-person contact, in spanish if possible.