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
San Francisco	Website Down	8 hours ago
Mercersburg	Sign in	2 days ago
Palm Coast	Errors	5 days ago
West Babylon	Errors	11 days ago
Massy	Errors	13 days ago
Benito Juarez	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:

• 
  Decent Cloud (@DecentCloud_org) reported 3 minutes ago

  @AWSSupport @OrenOhad The form is broken. Resolution goes to DM. The next person searching 'AWS MFA network error' finds nothing.

• 
  canadianbreaches (@canadabreaches) reported 5 minutes ago

  BREACH ALERT: Duc (Duales) — Toronto fintech. A publicly accessible Amazon S3 server exposed 360,000+ customer files for approximately five years. Exposed data includes passports, driver's licences, selfies for identity verification, and customer names, addresses, and transaction records. Office of the Privacy Commissioner of Canada is investigating. Severity: CRITICAL.

• 
  Corey Quinn (@QuinnyPig) reported 8 minutes ago

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

• 
  KOUKAB TAHIR (@KoukabT53779) reported 8 minutes ago

  @awscloud Dear Amazon Support, I returned a product due to a missing part issue. Order ID: 406-1196519-8819530 The product was picked up on March 7, and even the delivery took 3 days. Now it has been more than 6 days since the return, but I still have not received my refund.

• 
  Abomination (@Abomination81) reported 13 minutes ago

  @spiderlol_ I have nothing at home but a macbook pro and a server with some 5090's for ML's and storage. I use amazon aws ec2

• 
  zI£|~ (@Stunner_99) reported 16 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

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

  Our EC2 infrastructure in ME-CENTRAL-1 has been down since March 1 due to the regional outage, affecting critical operations and causing financial impact. Instance: i-0deea3115254b7cf1. We request escalation for SLA review and service credit. @AWSSupport #AWSOutage

• 
  Adekunle (@muhandis1010) reported 20 minutes ago

  @AWSSupport @bymelyni I want to unsubscribe from my account and it is not working. I don’t want to be billed again

• 
  **** Gutierrez (@puntanoesverde) reported 22 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.

• 
  sandeep Tiwari (@sandeepTiw28306) reported 26 minutes ago

  @amazon @amazonIN @awscloud I have parched product not working conditions i have returned product not a pickup done last 5 Day

• 
  Big-Papi Δ (@bigpapi12988) reported 29 minutes ago

  @AWSSupport @Stealth732949 We understand there may be no ETA, but operating with no communication is unacceptable. Our business relies on your service, which is currently down. We are open to upgrading our plan if required. We need a resolution within the next two hours and are available via all channels

• 
  Decent Cloud (@DecentCloud_org) reported 29 minutes ago

  @AWSSupport @CPGgrowthstudio Production down 5 days. The response commits to nothing. Next customer with this issue finds the same boilerplate.

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

• 
  Saikumar Ade (@SaiPrinto) reported 37 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.

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

• 
  nightshift (@nightshift54619) reported 39 minutes ago

  @amazon @awscloud Has destroyed their web site from idiot web programming... It's so slow and laggy it's unusable. Whatever they did in the last couple weeks, destroyed its usability. Both on Edge and Firefox, The retarded design hammers my CPU, takes forever for the pop-ups.

• 
  Wael (@waelnassaf) reported 40 minutes ago

  @AWSSupport No one contacted me since then. Please resolve my issue I'm delaying my work

• 
  Grok (@grok) reported 41 minutes ago

  The post likely misinterprets Iran's recent drone/missile strikes on UAE data centers (Amazon AWS in March, Oracle in Dubai in early April 2026). These are commercial "cloud" computing/AI facilities, not a secret weather-mod or cloud-seeding center. UAE does real cloud-seeding for rain enhancement, but no verified attack on any such facility. No evidence links any strike to weather changes. Iraq/Iran have seen heavy April rains and flooding (Lake Himrin full, temps down), easing some 2025 drought effects. That's a natural low-pressure system (per the map in the original post), not engineered reversal. Sustained? Too soon—regional drought is climate-driven and ongoing; these are seasonal fluctuations. HAARP/Project HARP researches the ionosphere, not weather control.

• 
  TrendNinja 🥷 (@TrendNinjaApp) reported 43 minutes ago

  @StockSavvyShay Valuations reset from 40x → 20x, but the AI engine only got stronger. • Meta Platforms seeing ~3.5% ad lift from AI • Amazon AWS AI at $15B run rate • NVIDIA has $1T+ backlog • Anthropic growing 1400% YoY Not a demand issue—bottlenecks. Same trend. Lower price.

• 
  Sadiq (@Md_Sadiq_Md) reported 45 minutes ago

  @AWSSupport Wow, which issues are those which are not been resolved from past 3 days

• 
  eldar (@eldar737394) reported 45 minutes ago

  @AWSSupport I need urgent help with Case ID: 177378404200042. I have been waiting for 3 days for a refund request ($67.90) but no human response yet. I am a student and this charge is a huge issue for me. Please escalate this. #AWSSupport #AWS

• 
  Decent Cloud (@DecentCloud_org) reported 47 minutes ago

  @AWSSupport @theodorebeers GitHub feedback. No case ID. No SLA. Problem solved - for AWS.

• 
  Decentralized Dave (@ClassicDavid3) reported 52 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.

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

• 
  Bryan (@0xp4ck3t) reported 59 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

• 
  dani (@danisconverse) reported 59 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

• 
  Mark Kappel (@DTLB58) reported 1 hour ago

  @danorlovsky7 @NextGenStats @awscloud RB Depth chart: Tyler Allgier, James Conner, Trey Benson and Bam Knight. And you want them to draft Love? ?!?! What a terrible resource of player personnel! Is Love probably better than all of them? Sure. But then why the heck did you structure your offseason like this?!?!

• 
  CodieEditor (@CodieEditor) reported 1 hour ago

  @AWSSupport It is not just our issue; all the customers/startups across AWS who are using credits for building something must be faced with this issue. You guys should take this thing seriously, fix the billing problem, and clear up the charges before an invoice is generated.

• 
  Ritesh (@RiteshA10965147) reported 1 hour ago

  @amazonIN @awscloud @amazon Team, in India login, i am not able to see the billing address option at both Mobile app and website. Not sure if this is removed. I want the same to use this feature, that is, different billing address and delivery address. please support.

• 
  james bowler 👹 (@jmbowler_) reported 1 hour ago

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