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:

• 
  The OddsBreakers (@theoddsbreakers) reported 54 seconds ago

  @PSchrags @awscloud @NextGenStats U mean, who will they trade down for?…

• 
  Sadiq (@Md_Sadiq_Md) reported 4 minutes ago

  @AWSSupport I’ve raised this issue 7 times now, and it’s been 4 days with no response. I need someone to speak to ASAP

• 
  みのるん (@minorun365) reported 5 minutes ago

  @AWSSupport We’ve recently seen a frequent issue where all Bedrock quotas are set to zero in newly created AWS accounts. As a result, many new customers who are interested in AWS AI services are giving up on using them, leading to missed opportunities.

• 
  Arshad Ansari (@arshad_ans5268) reported 6 minutes ago

  @AmazonHelp @awscloud Please tell me when my problem will be solved. I have sent you all the details.

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

  @HashiCorp @awscloud Unmanaged secrets in S3 is a real problem especially in fintech where you have long running services that accumulate config files, export artifacts, and database dumps over years. The hard part is not the scanning, it is what you do with the findings. Rotation pipelines and downstream dependency mapping are where most teams get stuck after discovery.

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

• 
  Mike Dupont (@introsp3ctor) reported 12 minutes ago

  @AWSSupport the billing ticket is open for days, and the discord and the github and absolutly no response from aws or kiro. Its seems like another release on a friday issue, so i will wait a bit happy holidays. my guess is they ran out of money and had to pause a bunch of accounts in loss.

• 
  JustAnotherEarthling *humorous/satirical* (@RobBoggs4) reported 13 minutes ago

  @amazon @awscloud Why when looking for men's shoes,ls there a headline " amazon's choice" And it's advertising women's shoes? Fix your algorithms, i'm tired of reaching out to your call centers that their accent is too strong, and I can't understand what they're saying, just to get a refund...

• 
  Aravida Shenoy (@AravindaShen0y) reported 17 minutes ago

  @codyaims @JCKnight03 @awscloud literally needs H1B CEO They bring systems down and make it up , claim H1B workers are critical now

• 
  Neal🅾️ (@BuddyPotts) reported 17 minutes ago

  @danorlovsky7 @awscloud @NextGenStats The defense was horrendous last year and all they added was Edmunds but lost Okereke and Flott. They cant stop the run at all, they should trade down and collect more picks and build the defense

• 
  DrastikD (@ThrottlesTv) reported 17 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?

• 
  Super Stiff Yogi (@SuperStiffYogi) reported 17 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.

• 
  **** Gutierrez (@puntanoesverde) reported 21 minutes ago

  @jo_byden @PearsonVUE @awscloud This feels like a bad joke. It is degrading to have to plead for my rights just because of a natural cognitive habit. Thinking out loud is part of my problem-solving process as an Architect.

• 
  zI£|~ (@Stunner_99) reported 25 minutes ago

  @AWSSupport I have an issue with the OnVUE exam I can't take a physical exam because of my schedule Now online option seems to be the worst It tells something unusual has happened each time it wants to launch my exam after going through alot of stress This is annoying

• 
  Jenifer Rajendren (@enravishjeni411) reported 27 minutes ago

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