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:

• 
  Alan Urmancheev (@alurmanc) reported 2 minutes ago

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

• 
  Kane | AI Insider 🤖 (@scooblover) reported 8 minutes ago

  This isn't Iran's first move against AI/tech infrastructure. Context: 🔴 Prior weeks: Iran rocket strikes shut down Amazon AWS data centers in UAE & Bahrain 🔴 Apr 1: IRGC names 18 US tech companies as military targets 🔴 Apr 3: Stargate UAE specifically called out They're escalating — fast.

• 
  MB (@MihaiButnaru) reported 8 minutes ago

  Some of the errors raised by AWS CloudFormation don’t make sense at all. You might be looking at one thing, but AWS is actually referring to something completely different (doesn't point properly to what it actually mean) @awscloud improve the logging

• 
  ©『 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.

• 
  Decent Cloud (@DecentCloud_org) reported 10 minutes ago

  @senunwah @AWSSupport On-prem means when it's down, at least you know whose fault it is.

• 
  Saad Hussain (@SaadHussain654) reported 12 minutes ago

  @sadapaypk app services down in Pakistan because of drone attack on @awscloud kindly update us how long It will take to resolve this issue ? We are suffering from 1,2 days

• 
  Decent Cloud (@DecentCloud_org) reported 13 minutes ago

  @Mn9or_ @AWSSupport No support subscription means you wait for someone else's ticket to fix your outage

• 
  A void (@xkeshav) reported 13 minutes ago

  @AWSSupport I already raised the issue

• 
  Jason Hall Jr (@JasonHallJr2) reported 13 minutes ago

  @NBA @awscloud This just shows he isnt the problem with the rockets

• 
  Adrian SanMiguel (@ar_sanmiguel) reported 13 minutes ago

  @ranman @QuinnyPig @awscloud Yeah, well. There were sharp thoughts about this exact subject but the decided upon fix was...double down on moar official engagement. It ain't exactly working.

• 
  🇪🇬fortnite egyption servers (@fortnite_Egypt1) reported 13 minutes ago

  @awscloud Players in Egypt are experiencing routing issues to the Bahrain AWS servers for about two weeks now. Ping jumped to ~150ms instead of the usual low latency. Please investigate and fix the routing problem.@AWSSupport @awscloud please fix the problem

• 
  Mohammad Imran (@mohdemraan) reported 15 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.

• 
  Asif Malik (@asif_malik_03) reported 17 minutes ago

  @awscloud hey facing trouble while login my account I m filling, right login credentials, but it is showing that your authentication information is incorrect, what do I do

• 
  pankti0 (@pankti0154952) reported 19 minutes ago

  Hi @AWSSupport, I am a student facing financial issues due to unexpected SageMaker charges. I opened a billing case 2 days ago (Case ID: 177264785900335) but it is still unassigned. Please help flag this for review? I need this to be resolved to complete my uni work. Thank you!

• 
  जहाँ mila,वही खोदूंगा (@GamingNepr34519) reported 21 minutes ago

  @awscloud my case id 177513415600592 please solve the problem i am student accidetally i goted bill