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 (36%)
• Website Down (36%)
• Sign in (28%)

Live Outage Map

The most recent Amazon Web Services outage reports came from the following cities:

City	Problem Type	Report Time
Glendale	Website Down	9 days ago
Oakland	Sign in	11 days ago
Greater Noida	Errors	11 days ago
Alamogordo	Website Down	16 days ago
San Francisco	Website Down	18 days ago
Mercersburg	Sign in	20 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:

• 
  Henrique Lima (@HenriqueLi88059) reported 4 minutes ago

  @AWSSupport @awscloud Our medical imaging platform has been DOWN for 24+ hours. Real patients. Real exams. Real impact. AWS suspended with ZERO explanation and ZERO contact after opening. This is a Radiology/PACS system. Every hour matters. We are desperate for a response.

• 
  yourclouddude (@yourclouddude) reported 6 minutes ago

  A startup wasted $50K on AWS. Not because AWS is expensive- because they didn’t understand it. Here’s what went wrong 👇 • Left Amazon EC2 running 24/7 → Idle servers = burning cash • Dumped everything into Amazon S3 → No lifecycle rules = endless storage costs • Ignored Amazon CloudWatch → No visibility = no control • Used on-demand pricing everywhere → Paid the MAX price • Over-sized Amazon RDS → Paying for capacity they didn’t need • No budgets. No alerts. No limits. → Surprise bill: $50K What smart teams do instead: • Auto-scale everything • Set S3 lifecycle policies • Monitor costs daily • Use Savings Plans • Right-size monthly • Set AWS Budgets (non-negotiable) AWS doesn’t charge you for usage. It charges you for mistakes. Fix this early → save thousands 💸

• 
  ᛒᛁᚱᛋᛁᚱᚴᛁᛦ ⨁ (@Thors_Bear) reported 7 minutes ago

  @amazon @Meta @awscloud Why are your drivers constantly stealing and killing animals? It’s a shame that having packages delivered to your house is now a safety issue.

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

• 
  Bulios.com (@bulioscom) reported 9 minutes ago

  $AMZN Amazon AWS went down in Virginia, $CME CME Group stopped derivatives trading in Chicago - oil, gold, S&P 500 and Nasdaq 100 futures had no price for hours.

• 
  Eduardo Rodrigues (@EduardoRod1972) reported 9 minutes ago

  @Suporte_Vanlink @AWSSupport @AWSSupport we have to pay a lot of people today, and we can’t use our systems, I believe the restatement needs to be immediately after de payment, this problem impacts in many areas of our company, including external users, many parents can’t see the school transportation in app

• 
  いいね！ (@yiyine8) reported 17 minutes ago

  @AWSSupport Urgent billing issue. My EC2 instances are still generating charges, but I cannot access my AWS accounts because the registered emails were deleted. Case ID: 177725454200231 Could someone please help review my case?

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

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

• 
  Arthurite Integrated (@Arthurite_IX) reported 22 minutes ago

  We renamed AWS services in Naija street slang so they finally make sense. 1. Amazon S3 = "The Konga Warehouse" Store anything. Retrieve it when you need it. It doesn't judge what you put inside. 2. Amazon EC2 = "The Danfo" You control the route, the speed, and how long it runs. The agbero (security group) decides who gets on. 3. AWS Lambda = "The Okada" Short trips only. No long commitments. Pay per ride. When it reaches the destination — it disappears. 4. Amazon RDS = "Iya Basement" She manages everything in the back. She's been there for years. She knows where everything is. Do not interrupt her. 5. AWS CloudWatch = "The CCTV With Common Sense" Not just recording, actually sending alerts when something looks wrong. Unlike the one in your office building. 6. Amazon Route 53 = "The Agbero" Directs all the traffic. Decides which danfo goes where. Keeps everything moving. 7. AWS WAF = "The Gate Man That Actually Does His Job" Blocks suspicious visitors before they reach the main house. No bribe accepted. 8. Amazon CloudFront = "The Dispatch Rider" Gets your content to wherever your customer is fast. No go-slow. No bridge hold-up. Which one made you laugh? Drop it in the comments. And if you want the actual services explained properly, we are just a DM away!

• 
  Dr. Srikanth Sundararajan (Doc) (@SundarSrik) reported 24 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 ?

• 
  Martin Alltimes (@Palatineirish) reported 26 minutes ago

  @awscloud What’s the difference between modernising and rebooting. Terrible, confusing text.

• 
  MetroTec Incorporated (@MRTECHFIXES) reported 28 minutes ago

  The schema for AWS host names needs greater device. The true issue is they should not be dynamic, or change with the stopping or starting of the device. Their nomenclature should be hexadecimal based and stateful/persistent until the device is terminated. @awscloud @AWS_Gov

• 
  Ed Silva (@SilvexPhoto) reported 28 minutes ago

  After layoffs @coinbase suffers outage cause by @awscloud... AI pushing code to production...

• 
  Ryan Lake (@RyanLake230731) reported 29 minutes ago

  @MetaNewsroom @awscloud @Meta When you going to fix facebook and Instagram and unblock mine and others accounts that were mistakenly blocked by Ai moderation??

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

• 
  Ankur Agrahari (@agrahariankur21) reported 30 minutes ago

  @AWSSupport Yes it's really really frustrating as my 15+ clients website applications and all the mobile apps are not working since 12 hours and 500+ employees salaries were not disbursed due to this issue, but no instant help from your service team. Case Id sent privately.

• 
  Smarty (@RathoreSmarty) reported 31 minutes ago

  @AmazonHelp @amazonIN @awscloud It is unacceptable refund was already initiated w/o any investigation Now after investigation,its denied citing policy violations. If issue, why was the refund approved in the 1st place? Reversing it later is unfair. I request immediate refund.

• 
  Dave L 💜🛡️ (@BajaDavidlak) reported 33 minutes ago

  @Harryhwrqx @chainlink @awscloud and price goes down

• 
  Ibraheem Tuffaha 🥛 (@IbraheemTuffaha) reported 35 minutes ago

  when you try to buy Savings Plans yourself 🫠 @awscloud gives you Savings Plans and Reserved Instances Different types, different terms, different quantities They even give you recommendations Those recommendations go stale in days Usage shifts, workloads change, and suddenly you're either underutilized or short Under-buy and you miss the savings Over-buy and you're locked into years of commitment you don't need We've watched companies spend months on this and still get it wrong @MilkStrawAI does it automatically Scans the AWS account, figures out exactly how much commitment is needed, and buys it gradually over a week If usage shifts up or down, the system adjusts on its own Zero intervention from the client They just see the bill drop at the end of the month

• 
  Kane | AI Insider 🤖 (@scooblover) reported 36 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.

• 
  Rehan Ahmed (@rehanahmediam) reported 43 minutes 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

• 
  CodieEditor (@CodieEditor) reported 47 minutes 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.

• 
  Goksal (@goksaladiguzel) reported 51 minutes ago

  @awscloud If banks, especially those relying on COBOL-based legacy systems, replace them with modern software, they would most likely require 20–30 times more computing capacity than their current server infrastructure, and in general they still wouldn’t reach COBOL’s level of performance. And also, every time we go to an ATM to withdraw money, we will most likely see a “null point exception.”

• 
  Kunal (@kunal_twts) reported 54 minutes ago

  @ryukozyy @awscloud But those computers ease so much issues for companies

• 
  SCOTT (@ScottSummers) reported 55 minutes ago

  If you’re still ignoring $ICP after today and @awscloud going down you’re retarded

• 
  Trevor Skinner (@PrometheusAIsec) reported 58 minutes ago

  I’m getting real tired of watching this industry pretend dependency is innovation. The entire tech world got sold on the idea that hardware was the problem and cloud was the solution. And to be fair, Amazon AWS played it perfectly. From a business standpoint, it was brilliant. Make infrastructure easy. Make it scalable. Make it fast. Make it cheaper to start. Then make it harder and harder to leave. That’s the part nobody wants to talk about. At first, cloud feels like freedom. No racks. No servers. No switches. No up-front hardware cost. No late nights swapping drives, troubleshooting power, rebuilding arrays, or fighting broken infrastructure. But over time, that freedom can turn into a leash. I’ve seen enough real-world systems to know the difference between convenience and control. Access control, networking, servers, security hardware, firewalls, cameras, panels, credentials, cloud dashboards, hosted platforms, vendor portals — it all looks great until the business depends on something it does not actually own. That is where the trap starts. One vendor controls the platform. One vendor controls the pricing. One vendor controls the updates. One vendor controls the outage window. One vendor controls the rules. One vendor controls the ecosystem. Then businesses slowly build everything around it. Compute, storage, databases, backups, monitoring, identity, deployment, physical security, access control, video, alerts, compliance, logging, and billing. By the time they realize how deep they are, leaving is no longer a simple decision. It becomes a migration project. A budget problem. A staffing problem. A security concern. A downtime risk. A business risk. That is not just convenience. That is a dependency loop. And what frustrates me the most is that the same industry that used to understand real infrastructure now acts like ownership is outdated. Owning hardware is not outdated. Understanding networks is not outdated. Knowing servers is not outdated. Knowing how systems work underneath the dashboard is not outdated. Building hybrid infrastructure is not outdated. It is control. Cloud has its place. Hosted systems have their place. Managed platforms have their place. I am not against any of that. I am against companies blindly giving up ownership, knowledge, and leverage, then calling it progress. Because when your entire business depends on someone else’s platform, someone else’s pricing, someone else’s rules, someone else’s uptime, and someone else’s permission, you do not own your technology. You rent permission to operate. Prometheus V2 is built different by RocketCore.

• 
  Rahul Khatri (@Rahulk644) reported 58 minutes ago

  @AWSSupport. Trying to resolve a $200 billing from accidentally left-on resources after our student startup shut down. I've had 2 cases open requesting a waiver & account closure, but both have sat unassigned for 1 month. Need urgent help. Cases: 177520122800121 177591632700789

• 
  Roberto Shenanigans (@Rob_Shenanigans) reported 59 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.

• 
  Vinit Taneja (@vinit_taneja) reported 1 hour 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.