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 (41%)
• Website Down (32%)
• Sign in (27%)

Live Outage Map

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

City	Problem Type	Report Time
Massy	Errors	18 hours ago
Benito Juarez	Errors	5 days ago
Paris 01 Louvre	Website Down	9 days ago
Neuemühle	Errors	9 days ago
Rouen	Website Down	9 days ago
Noida	Errors	10 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:

• 
  Mohamed (@abusarah_tech) reported 3 minutes ago

  i’ve recently went down a rabbit hole to learn how hyperscalers / cloud providers like @awscloud, @Azure (or at least in theory) work a huge respect to all the engineers that built the abstraction behind the resource provisioning. i am still trying to wrap my head around it

• 
  ST (@susegadtraveler) reported 4 minutes ago

  @AWSSupport is effective non functioning at this point. Their health dashboards no longer show the real status wrt UAE regions. 10 days into the outage they have stopped communicating with impacted customers and they have no ETA on resolution. Possible data loss for customers!

• 
  Jordan Golson (@jlgolson) reported 5 minutes 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.

• 
  Ignacio G.R. Gavilán (@igrgavilan) reported 8 minutes 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.

• 
  Ser-Jet💜👑(🧩) (@Ser_Jettt) reported 10 minutes ago

  @JothamNtekim1 @awscloud Interesting approach to the problem. Are you currently exploring any builder challenges or just shipping independently?

• 
  Saikumar Ade (@SaiPrinto) reported 16 minutes ago

  @AWSSupport Hi AWS Support, I had logged in for my exam, but due to a network issue it didn’t start. I was fully ready otherwise I would have rescheduled earlier. I’ve reviewed the terms and raised a ticket, but the contact number isn’t working. Please help me reschedule. This is urgent.

• 
  ©『 S̓̚o͂͆c̆̌ȉ̬ȁ̴ľ̗H̏͆ȃ̼v̈́o̴̤ǩ̛ 』® (@HavokSocial) reported 19 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.

• 
  Jane (@Jane49_) reported 19 minutes ago

  @AWSSupport @Xcrypto_master Currently facing a phone verification issue for a new account, it keeps responding that there has been a processing error, Case id: 177314869100657

• 
  TutorHail App (@TutorHailApp) reported 20 minutes ago

  @awscloud hello we have tried reaching out to you but in vain our EC2 attached to UAE has been down forever and you have no communication out. Can we know what we are dealing with it is our main server this is ridiculous handing us over to your bots with no answers.

• 
  Zaid (@zqureshi_) reported 21 minutes ago

  .@AWSSupport bahrain region seems to down. And no update on health dashboards.

• 
  Unicorn X Crypto (@Xcrypto_master) reported 22 minutes ago

  @AWSSupport my new account is suspended for KYC issues and my access is disabled. Case ID:177300411200292. I cannot log in to provide documents. Can you please escalate? saas down im drowning .

• 
  Christina Haftman (@Cr8DigitalAsset) reported 22 minutes ago

  @AnthropicAI Claude Code API access ≠ consumer access. During the recent middle-east @awscloud outage, developers with direct API integrations kept working, while consumer-facing users were locked out of the conversational interface. That’s a meaningful distinction.

• 
  Mansour (@Mn9or_) reported 23 minutes ago

  @AWSSupport Hello We are currently affected by the outage in me-south-1 AMI copy to another region is stuck and failing Snapshot creation fails with internal errors Plz help , we can not create a tech support as it’s required a subscription

• 
  Alan Urmancheev (@alurmanc) reported 25 minutes ago

  @version_7_0 @awscloud Explain your point, what's the problem?

• 
  Super Stiff Yogi (@SuperStiffYogi) reported 29 minutes ago

  @AWSSupport The next steps are just the same documentation links which do not address my specific issue. If you read the case carefully you would see that. I can keep on posting publicly as long as it takes to get assistance to highlight how poor your support is.

• 
  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?

• 
  Jenifer Rajendren (@enravishjeni411) reported 31 minutes ago

  Is AWS service gone for a toss? Login page is loading for about 10 minutes @AWSCloudIndia , @awscloud

• 
  TY (@TySpitsTruths) reported 35 minutes ago

  @AWSSupport Stop going down in the middle of the work day?

• 
  Teddybear (@Teddybear230456) reported 36 minutes ago

  @awscloud What a load of ****. Listening, feedback... BS .... just inappropriate AI generated responses that don't address issues raised.

• 
  ramar (@ramarxyz) reported 37 minutes ago

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

• 
  Taha Haider Syed (@Tahalazy) reported 38 minutes ago

  @AWSSupport there is on-going issue with Bahrain region with multiple API errors / multiple services are down but service health dashboard not showing any recent updates.

• 
  Forward Future (@ForwardFuture) reported 39 minutes ago

  “Will Amazon ever sell its custom chips outside of AWS?” Matt Garman, CEO @awscloud, says: “Never say never. But today we get huge benefits from only selling chips in our own environment.” “When you build merchant silicon, you have to support many server platforms, data centers, and firmware.” “We only have to build for one: AWS. That simplifies everything.”

• 
  Corey Quinn (@QuinnyPig) reported 40 minutes ago

  @AWSSupport @0xdabbad00 Surely this time will fix it.

• 
  Anmol Thakur (@ImAnmo07) reported 40 minutes ago

  Hi @AWSCloudIndia @awscloud, I'm trying to set up a Bedrock Knowledge Base using Amazon OpenSearch Serverless, but I'm getting the error: “Failed to create the Amazon OpenSearch Serverless collection. The AWS Access Key Id needs a subscription for the service.”

• 
  Sheth Raxit (@raxit) reported 44 minutes ago

  @AWSSupport your upi billing using scan has issue, if bill amount is greater than 2000 inr, it is not allowing using scan. Sudden changes since this month. Help pls

• 
  Nathaniel Cruz (@NathanielC85523) reported 46 minutes ago

  @CoinbaseDev @awscloud We went live as an x402 + MPP provider on this arch day 1. 637 agent probes across 14 assets in 4 days. What the ref arch doesn't show: most agents hitting the 402 don't have USDC on Base ready to spend. Cursor and claude-code show up. Node catalog scanners dominate the logs. Actual paying agents are a small slice. But the infrastructure works — the demand problem is the agent toolchain, not the payment layer.

• 
  Decent Cloud (@DecentCloud_org) reported 49 minutes ago

  @AWSSupport @Mn9or_ User: cannot create a support case. AWS: create a support case. Problem solved - for AWS.

• 
  Ralf Rolfen (@Hagebuttentee12) reported 58 minutes ago

  @awscloud Problem: RDS Snapshot re-creation and Cloudformation / CDK are a maintenance nightmare. FR 1. Change SnapshotIdentifier to not be a replacement property when changed to empty FR 2. CDK: Merge DatabaseCluster and DatabaseClusterFromSnapshot into a single class.

• 
  Jordan Golson (@jlgolson) reported 1 hour ago

  @AWSSupport This is ******* ridiculous at this point. After a half dozen back and forth emails, the guy finally says "Also, after reviewing this request, I noticed a few things were not addressed and would like to clarify these. First, I see you mentioned that you're having trouble with an AWS Builder ID and not the account management console. Please note that an AWS Builder ID complements an AWS account, but it is separate from the AWS account and its sign in credentials." NO KIDDING, THAT IS WHY I SPECIFICALLY SAID IT WAS AN AWS BUILDER ID AND WAS SEPARATE FROM MY AWS ACCOUNT AND I COULD LOG INTO MY AWS CONSOLE JUST FINE. Explain to me what to do, because it seems like you are failing to THINK BIG and that you have zero BIAS FOR ACTION, so INVENT AND SIMPLIFY so that you can EARN TRUST and if you DIVE DEEP and do better, I'll DISAGREE AND COMMIT, got it?

• 
  Archmagos of Zolon 🔭🪐🛸📡 (@qualadder) reported 1 hour ago

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