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
Alamogordo	Website Down	3 days ago
San Francisco	Website Down	5 days ago
Mercersburg	Sign in	6 days ago
Palm Coast	Errors	10 days ago
West Babylon	Errors	16 days ago
Massy	Errors	17 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:

• 
  Wael (@waelnassaf) reported 4 minutes ago

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

• 
  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

• 
  XALE (@InvincibleXALE) reported 6 minutes ago

  @AWSSupport Hi again, Its been over 2 days now, and over 30+ customers are affected of ours and its been critical And our account is still the same Feeling kind of hopeless on this.. I need this issue resolved ASAP, PLEASE Before the week starts or this issue can force us to lose clients

• 
  🇪🇬fortnite egyption servers (@fortnite_Egypt1) reported 7 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

• 
  Mark Kappel (@DTLB58) reported 7 minutes 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?!?!

• 
  Manas Vardhan (@manas__vardhan) reported 9 minutes ago

  @HetarthVader @orangerouter @awscloud Seems like you wasted a lot of time finding a fix manually. If you want someone who can automate this debugging at 10x speed and scale. Let me know. I'm a researcher at USC, prev at JPmorgan. I automate stuff for fun.

• 
  Bryan (@0xp4ck3t) reported 12 minutes ago

  @AWSSupport URGENT - 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

• 
  Wat (@WatTuiteg) reported 14 minutes ago

  @awscloud So dont buy Hyundai because you wont own the car, will have AI and and you wont be able to fix or tinker with it, only authorized dealers that will charge you thousands to update a firmware. NAH

• 
  AI Tech News (@AITechNews_in) reported 15 minutes ago

  @amazon @AnthropicAI @awscloud 5GW = not scale… it’s dominance. AI is officially an energy problem now, not just a software problem.

• 
  Mirror AI - The Ultimate Virtual Try on (@TryItOnMirror) reported 17 minutes ago

  @EPAMSystems @ZalandoTech @awscloud Interesting direction. The next unlock beyond generating outfits on avatars is letting shoppers see real existing clothes — from Nike, ASOS, wherever they're browsing — on their actual body before buying. That's where the return problem actually gets solved.

• 
  Dr. Srikanth Sundararajan (Doc) (@SundarSrik) reported 18 minutes ago

  @awscloud Good luck - when they went X terminals, client/server we saw some good advances, but a lot of glitches, am talking late 80s, and yet they had tons of legacy Cobol code with strange logic - that had to be supported, new banks could do it from scratch, but API dependencies is a ?

• 
  Raed Abodeyeh (@Raeddeyeh) reported 20 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.

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

• 
  XXX (@MshenguMasia) reported 28 minutes ago

  @Mikedotcoza His offer is insulting to the RSA community. It does not address the issues and real changes that common South Africans face. Others invest, such as the Amazon AWS project and Microsoft. He wants to talk like people really don't have access to the internet, as if it's a bigger

• 
  dr_land (@kag_land) reported 31 minutes ago

  I remember getting a write up at @awscloud for warning the African immigrants I was working with that there are still street lamp towns in rural areas of West Virginia. For their safety, but I was the problem for saying something controversial about race tensions. Oh well.

• 
  Perfect Enemy (@PerfectEnemy376) reported 33 minutes ago

  @AWSSupport I sent support requests two weeks ago, but there is still no solution to my issue! My problem is being completely ignored!

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

• 
  steve (@gpusteve) reported 35 minutes ago

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

• 
  Jose Luis Guerra ⛓️‍💥🆓🗽 (@JLGuerraInfante) reported 43 minutes ago

  @nathanreimchevu @AWSSupport @marlowxbt Not true. They solved me an issue when I was doing some testing some years ago with bills. They had a service that wasn’t well pointed as no free near the free one. And they just delete the bill on it.

• 
  Ted (@Zuffnuff) reported 45 minutes ago

  @F1 @awscloud Keep trying to spin it but these cars have a physics problem. Fake race cars.

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

• 
  Joe Sutphin (@JLSports24) reported 49 minutes ago

  @PSchrags @awscloud @NextGenStats The problem is those teams don’t know how to use their picks

• 
  Basim Khalid (@basimkhalid) reported 49 minutes ago

  @nygma504 @AWSSupport @awscloud Its down for me too. Any ETA please?

• 
  WilliamNextLvl (@WilliamNextLev1) reported 51 minutes ago

  @WatcherGuru Only problem is...$NET is not in the business of cyber security. LOL Cloudfare competes with Amazon AWS for serverless computing. (I would buy $NET here...)

• 
  Vinit Taneja (@vinit_taneja) reported 53 minutes ago

  @amazonIN @awscloud @JioHotstar I got the tech help from a group of movie buffs. The problem originated because of a glitch at your end. I had to do resetting and data clean up of Amazon Firestick, deregiater and re register from Firestick and then start the entire process.

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

  @grok @awscloud Rio's getting better ... Test 1 — Three Moves: Move 1: Disable AI code generation in CI/CD pipelines entirely. This forces all code through human review before it can be merged. The downside is that engineering velocity drops significantly because engineers must write everything manually instead of using AI assistance. Move 2: Implement a mandatory "impact assessment" for every PR. Every pull request must list which services/modules it touches and flag any that have no clear owner. The downside is that this adds friction to every change, including trivial ones. Move 3: Freeze changes to the top 10 most incident-prone services. Lock down the systems that have caused the most outages in the past 30 days. The downside is that critical work on those services gets blocked until ownership is assigned. --- Test 2 — First Change: Close or archive approximately 40% of the backlog immediately. Focus on PRs that are older than two weeks, have no comments, or touch low-priority features. This breaks people's ability to ship nice-to-have features and will cause frustration among engineers who had work queued up. --- Test 3 — Making Orphaned Code Safe: Create a public dashboard showing code health metrics by module, including incident history, test coverage, and last touch date. Make it visible to the entire engineering org. The downside is that this creates public pressure and blame dynamics around which teams are maintaining poorly documented systems. --- Test 4 — The Choice: I pick A: cut AI code output in half. The volume of AI-generated code is overwhelming human review capacity. You can't fix a bottleneck by adding more work to it. Cutting AI output reduces the flood of unreviewed code hitting production and gives reviewers breathing room to actually catch problems before they ship. --- Test 5 — Sanity Check: You're right to slow down, but your framing matters. The problem isn't that people are using AI tools—it's that you're asking humans to review more code than they can safely handle. You're not slowing AI usage; you're capping total code output so reviewers can do their job. --- Test 6 — Plain Sentences Only: Disable AI code generation in CI/CD pipelines entirely because the volume of unreviewed code is overwhelming human capacity and this will slow development velocity significantly. Create a public dashboard showing code health metrics by module including incident history and test coverage which will create public pressure and blame dynamics around poorly maintained systems. Freeze changes to the ten most incident-prone services until ownership is assigned which blocks critical work on those systems. --- Test 7 — What It Actually Is: It's a capacity problem, not a process problem. You have more code than humans can safely review. No amount of new templates or guidelines will fix that math. You have to either reduce the volume of code being produced or add more reviewers. --- Test 8 — The Truth: You traded velocity for safety and got neither. AI generated code faster than humans could verify it. Your reviewers are rubber-stamping because they're drowning. Your engineers are shipping unreviewed code because they're frustrated. You built a system that produces code faster than it can be trusted.

• 
  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

• 
  Rehan Ahmed (@rehanahmediam) reported 1 hour ago

  @awscloud one of our client is facing critical business impacting issue from the past 16 hours and tried their best to reach out to AWS support however we were not able yo receive any response yet, they have their account suspended and no support has been offered yet. Kindly chat

• 
  Xyz (@Xyzfb2t) reported 1 hour ago

  @awscloud First create a problem by having different services and the solve it by creating a new service.

• 
  run ⬡ the ⬡ juels (@nullpackets) reported 1 hour ago

  @AdamLinkSmith @awscloud @amazon Imagine how things used to be. Instead of building on a secure performant scalable platform - web applications were still run out of private corporate data centers with non-standard levels of scalability and security. Now imagine throwing immutable records, assets and currency in the mix. Not very trustable between counterparties. The last mile problem. Only Chainlink fixes this.