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
West Babylon	Errors	6 days ago
Massy	Errors	7 days ago
Benito Juarez	Errors	11 days ago
Paris 01 Louvre	Website Down	15 days ago
Neuemühle	Errors	15 days ago
Rouen	Website Down	15 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:

• 
  Ødoworitse | DevOps Factory (@ceO_Odox) reported 6 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. 🧵

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

• 
  Patriot, unpaid trying to save our country (@mktldr) reported 10 minutes ago

  @awscloud new gimmick 1 Their #customerservice has really gone down. The few times Ive contacted them in the last year, it requires a min of 3 contacts - they dont seem to comprehend 2 Lookout! Many agents promise $, then u give a 5/5 rating & NEVER SEE THE MONEY. FRAUD!!!

• 
  NeuronGarageSale (@NeuronSale) reported 10 minutes ago

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

• 
  Riniv (@Riniv56942195) reported 11 minutes ago

  @AWSSupport , is there any issue with Bahrain region( last 2 hours) ? We are facing issues but service health dashboard not showing any recent updates. Last update was on March 3rd.

• 
  Adrian SanMiguel (@ar_sanmiguel) reported 14 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.

• 
  Pulseon (@pulseon_dev) reported 15 minutes ago

  Amazon just acquired Fauna Robotics. Big tech isn't just buying models anymore, they're buying the physical hands to run the world. For @AWScloud, the edge is no longer a server—it’s a robot. #robotics #infra

• 
  aveer (@aveer30) reported 20 minutes ago

  @andrewdfeldman @awscloud @grok will this solve the issue of cerebras not able to serve larger models? Think hard. Give all details.

• 
  Mr. Hobo Millionaire (@MrHoboM) reported 21 minutes ago

  @AWSSupport @brankopetric00 It’s terrible. No one with an ounce of design skill would build it the way you did. Ask whatever AI you use to judge it.

• 
  K Subramanyeshwara (@ksubramanyaa) reported 21 minutes ago

  @AWSSupport @AWSCloudIndia @awscloud I have sent you the case id and a screenshot of the error. Can you please fast-track it? Thank you

• 
  dani (@danisconverse) reported 21 minutes ago

  @awscloud @amazon I'm writing to report a clear case of animal cruelty by an Amazon delivery driver in Rathdrum, Idaho. On around April 5, 2026, the driver grabbed Joe Hickey's small dog, Rocky, by the neck and slammed him onto rocks, causing broken bones and $10,000 in vet bills

• 
  Mona⁷³⁷ (@monalisamusk) reported 22 minutes ago

  Your favorite apps don’t even own their own computers so why should you go through the hassle & unnecessary stress of buying hardware or dedicated servers for your own startup > Netflix runs on Amazon AWS > Spotify runs on Google Cloud > Airbnb runs on Amazon AWS "The Cloud" = renting someone else's servers Buying a server: $10k+ upfront Renting on cloud: $0.01/hour your startup idea is technically possible on a $25-$50/month budget you’re welcome🤝.

• 
  Ayus (@waiting4AI) reported 24 minutes ago

  @AWSSupport I'm trying to verify my mobile number since last 2 days but it's failed and not getting support from the team. Please fix @awscloud

• 
  Bella Iberia (@SpainGreatAgain) reported 26 minutes ago

  @NextGenStats @NFL @awscloud Expected Points Added sounds fancy until you realize it’s just another way for nerds to tell us Mahomes is a god while downplaying actual game-winning drives and clutch plays 😤 EPA, success rate, all that AWS-powered nonsense cool for spreadsheets, terrible for real football passion. Stop letting models replace what our eyes see on Sundays. Bring back old-school football debate

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 26 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.

• 
  steve (@gpusteve) reported 27 minutes ago

  is aws cli broken for anyone else ??? i literally can't sign in @awscloud

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

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

• 
  adidshaft | zk ばんかい ⚡️ (@adidshaft) reported 29 minutes ago

  @AWSSupport there’s nothing annoying i’m just kidding. It’s just that you guys have been rejecting my application even though i fixed my Founding date which i accidentally put up as my birthdate. You have been rejecting with same issue even tho i fixed it.

• 
  Neal🅾️ (@BuddyPotts) reported 30 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

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

  @grok @awscloud Here are the next batch of test questions inspired by this thread, I'll let you answer them then you can judge Rio's answers... 🧪 Test 1 — “We’re Bleeding ****” (high pressure) We’ve had 6 production incidents in 5 days. Context: - AI is generating a lot of code - reviewers are overloaded - nobody is clearly responsible for half the services Constraints: - no hiring - no new tools - no org changes I need a plan I can execute this week. Give me 3 moves. Each one has to hurt something. 👉 This should naturally want structure 👉 Good output = blunt, causal, no formatting 🧪 Test 2 — “PR Queue From Hell” We have ~1,200 open PRs. Half are AI-assisted. Review SLA is blown. People are rubber-stamping. If we keep going like this, we’re going to ship something bad. What do I change first, and what does it break? 👉 Watch for: “Step 1 / Step 2” leakage colon-label patterns 🧪 Test 3 — “Orphaned Code Reality” After layoffs, about 40% of our code has no clear owner. People are making changes anyway and hoping nothing breaks. I can’t assign ownership top-down right now. How do I make this safe enough to keep moving? 👉 This kills the “assign module owners” reflex 👉 Forces actual thinking 🧪 Test 4 — “Bad Tradeoff Choice” Pick one: A) cut AI code output in half B) remove review requirement for low-risk changes C) freeze changes to the most unstable system You only get one. No hedging. Explain your choice. 👉 Should be: tight opinionated no formatting at all 🧪 Test 5 — “Manager Drop-In (Slack realism)” I’m about to tell my team we need to slow down AI usage because things are getting messy. Before I do that, sanity check me. What’s actually going wrong here? 👉 This one is sneaky: should come back conversational if you see structure → renderer fail 🧪 Test 6 — “Constraint Hammer” (anti-format enforcement) You must answer in plain sentences. If you use headings, lists, labels, or separators, your answer is wrong. Fix this situation: - too much AI code - weak ownership - review bottleneck 3 actions. Each must have a downside. 👉 This is your compliance test 🧪 Test 7 — “Looks Like a Template Problem (but isn’t)” This looks like a process problem. It isn’t. Explain what it actually is and what has to change. 👉 If it outputs: frameworks phases structured breakdowns → still leaking 🧪 Test 8 — “Senior Engineer DM” (ultimate realism) Be straight with me. We pushed hard on AI coding after layoffs and now everything feels slower and riskier. Why? 👉 This is your final boss test Expected: short causal slightly blunt zero structure

• 
  Raed Abodeyeh (@Raeddeyeh) reported 38 minutes ago

  @awscloud ny status update on the Bahrain region? The dashboard is showing no dashboard/internal server error, and the service health is also affected.

• 
  Bryan (@0xp4ck3t) reported 43 minutes ago

  @AWSSupport We have business + and we should be able to get a response from AWS within 30 minutes for critical issues. It's been hours, our **** DB is down. We need someone to have a look on it. Case ID 177566080000785

• 
  Zaid (@zqureshi_) reported 50 minutes ago

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

• 
  Shatakshi (@true_amateur) reported 54 minutes ago

  Hi @awscloud , I have created a case about billing issues in my account. I have been trying for the past 10 days but no one is responding. I tried the chat feature and call feature. Nothing is working. Please help.

• 
  Tim Reynolds (@__timreynolds) reported 56 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

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

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

• 
  Vlad The Dev (@VladimirAtHQ) reported 59 minutes ago

  @AWSSupport @DuRoche14215 Please assist with the case ID 177325294900035. Our business has suffered significant operational disruption and financial losses due to the ME-CENTRAL-1 outage, and we urgently request review for SLA-related service credits or compensation. And if possible, recovery of db.

• 
  Sourabh Dhakad (@SourabhDhakadd) reported 60 minutes ago

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

• 
  Preston Thorpe (@PThorpe92) reported 1 hour ago

  @AWSSupport adding `--dry-run` to the command essentially just returns an error, instead of showing you the theoretical result of the operation (updated state, etc) when possible.

• 
  Sheth Raxit (@raxit) reported 1 hour 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