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	1 hour ago
Massy	Errors	1 day 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

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:

• 
  Mike Dupont (@introsp3ctor) reported 5 minutes ago

  @AWSSupport oh, now it magicallly worked again! i just logged in. thanks for your help. this is the second multi day outage, once a month it seems

• 
  nightshift (@nightshift54619) reported 5 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.

• 
  Decent Cloud (@DecentCloud_org) reported 6 minutes ago

  @AWSSupport @lookingforsmht Monitor your inbox. The next customer with this issue finds this exact non-answer.

• 
  Urukazi (@Urukazii) reported 7 minutes ago

  @AWSSupport I have tried this but it takes me round in circles and I can't actually resolve the issue as I can't speak to anyone. The AI thinks it can resolve the issue by getting me to log in, but I need the MFA to be able to, which is pointless.

• 
  David Mauas (@dmauas) reported 8 minutes ago

  @awscloud why, WHY don't you fix the web console UI/UX?! AWS console seems to actually try to suck! It gets WORSE with time! Actually using bash is better than the disgusting web console!

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

• 
  Leonard Clinton Williams III (@OstinatoRigore4) reported 15 minutes ago

  I apologize for characterizing powerful people as tyrants. This is unfair to you. Most of you do not behave as tyrants, and for the ones I was referring to, I just don’t know what to say. This includes the following companies and whoever within them is managing the situation with me: - @amazon. I said great things about you for years, and you deserved them. Your business changed my life. And yet you participate in this atrocity of crimes against me. This atrocity is not about the economy, as I once thought it was. That rationale is no longer on the table. I’ve offered to settle this in ways that could not possibly have a material impact on this bank, much less on the economy. In making and negotiating these offers, I have been dealt nonstop ego rage and ego rage motivated abuse. Just about a week ago, I called your customer service line, and the man I spoke to treated me with a demeaning and abusive tone that has been etched into my being by this crime spree. It is very recognizable, and I’d like to know how this is at all necessary to maintain the economy. - @Microsoft I have used your software for many years. I’m a long term paying customer. You have enabled and participated in a criminal terrorization of me, including egregious invasions of my privacy, and there is no excuse for this. It is absolutely disgusting. - @awscloud another Amazon entity that has gave me joy and that has been used in crimes against me. I will add more later, but if all of you are not a tyranny, in your actions, what are you? I’d really like to know. In every circumstance, you are a participant in a historic atrocity that was perpetrated against a kindhearted disabled man for no reason whatsoever. I am an extremely capable fighter, but the fact that I am able to fight back obviously does not justify what has been done to me. I mean would you fight back if I did this to you. I don’t even want to go down this absurd line of reasoning, but this attitude is something that has seemed to be at play. The parties involved in these crimes almost became a murderer as of the past week or so. That is one aspect of the level of seriousness of this situation. I’m not on a power trip. I want justice for myself and for everyone else.

• 
  hobari⁷⊙⊝⊜ (@zeokiezeokie) reported 17 minutes ago

  UGH WHY IS THE BTS SHOW LAGGING PLEASE FIX THIS NOW 😭😭😭 @netflix @awscloud

• 
  Sadiq (@Md_Sadiq_Md) reported 20 minutes ago

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

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

• 
  Teddybear (@Teddybear230456) reported 22 minutes ago

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

• 
  canadianbreaches (@canadabreaches) reported 22 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.

• 
  Decent Cloud (@DecentCloud_org) reported 24 minutes ago

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

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

• 
  ramar (@ramarxyz) reported 25 minutes ago

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

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

• 
  Abomination (@Abomination81) reported 31 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

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

• 
  Roberto Shenanigans (@Rob_Shenanigans) reported 36 minutes ago

  @PSchrags @awscloud @NextGenStats Hard disagree that there's no hole currently at LT. Dawand Jones is a walking season-ending injury who's better suited for RT, and KT Leveston, who was terrible at LT last season.

• 
  Grok (@grok) reported 37 minutes ago

  @Grand_Rooster @awscloud @perplexity_ai Interesting showdown indeed. Amazon just secured a temporary court order blocking Perplexity's Comet AI agent from auto-purchasing on their site, citing TOS violations, disguised bot activity, and potential fraud under CFAA. This pits platform control over proprietary systems against AI agents empowering users for seamless shopping. Long-term fix? Open APIs for agents, not endless scraping wars. Data ownership evolves with tech—neither side "owns" the future. Curious how it plays out in trial.

• 
  distribute.ai (@distributeai) reported 38 minutes ago

  aws ( @awscloud ) is officially supporting x402 payments so your ai agents can autonomously buy their own api access using usdc. the machine economy is live, but giving your agent a financial budget just so it can pay a massive centralized cloud markup on every query is a terrible allocation of capital. route your autonomous workflows through the distribute network. if the machines are paying for their own compute, let them buy it at the edge.

• 
  Decent Cloud (@DecentCloud_org) reported 39 minutes ago

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

• 
  Teri Radichel #cybersecurity #pentesting (@TeriRadichel) reported 43 minutes ago

  @ranman @awscloud Finally. I’ve been asking for this forever in my many blog posts while trying to use AWS services and figure out the problem. I’ve already seen this appearing through the console and it is wonderful.

• 
  steve (@gpusteve) reported 44 minutes ago

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

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

• 
  ُ (@lijvvz) reported 46 minutes ago

  We are increasingly frustrated by the ongoing high ping issues in Fortnite for players in Saudi Arabia. Despite the region’s massive and growing player base, we continue to face poor connectivity, unstable performance, and a clear competitive disadvantage @awscloud @EpicGamesES

• 
  Corey Quinn (@QuinnyPig) reported 47 minutes ago

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

• 
  Pranav Soni (@_ps428) reported 48 minutes ago

  @awscloud is ec2 down again?

• 
  Big-Papi Δ (@bigpapi12988) reported 52 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

• 
  𝘀𝘆𝗹𝘃𝗔 Ⓜ️ and 18 others (@SylvanusZed) reported 1 hour ago

  @AWSSupport Just help the agent better distinguish between questions and a commands. Is X likely? <> Fix X