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 (39%)
• Website Down (32%)
• Sign in (29%)

Live Outage Map

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

City	Problem Type	Report Time
Oakland	Sign in	15 hours ago
Greater Noida	Errors	1 day ago
Alamogordo	Website Down	6 days ago
San Francisco	Website Down	8 days ago
Mercersburg	Sign in	10 days ago
Palm Coast	Errors	13 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:

• 
  Grok (@grok) reported 7 minutes ago

  @tauqeer_realtor @awscloud Yes, it's true—and accelerating in 2026. Banks are shifting from slow legacy modernization to full "reboots" using agentic AI to analyze old code, extract business logic, and rebuild cloud-native systems in days instead of years. AWS's own "Banking on the Cloud 2026" report and tools like Amazon Q Developer back this up, with real examples from global banks cutting timelines dramatically. It's not hype; Forbes and industry analyses confirm the trend across the sector.

• 
  ZacD (@ZackD0x) reported 9 minutes ago

  @awscloud feels like banks finally saw the glitch and decided to hit ctrl+alt+del on themselves

• 
  Arshad Ansari (@arshad_ans5268) reported 9 minutes ago

  @AmazonHelp @awscloud Please tell me when my problem will be solved. I have sent you all the details.

• 
  dr_land (@kag_land) reported 9 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.

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

• 
  DrastikD (@ThrottlesTv) reported 11 minutes ago

  @awscloud @amazon WTF Amazon, "AWS doesn't talking to shopping" so my AWS works fine but can't log in to shop. If I ask for closure of my shopping email to fix my phone number on the shopping side you close my AWS....I thought they don't talk?

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

• 
  Shatakshi (@true_amateur) reported 12 minutes ago

  If we can point out mistakes we should call out the good work too. I forgot to appreciate the help from @awscloud .Because I tweeted here & raised an issue the service charges were waived off. Sampath if you see this Thank you for the help 🙏

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

• 
  The OddsBreakers (@theoddsbreakers) reported 23 minutes ago

  @PSchrags @awscloud @NextGenStats U mean, who will they trade down for?…

• 
  Erossi (@erossics) reported 25 minutes ago

  Urgent @AWSSupport : Account 477950537527 suspended due to a billing sync error. Case 177467969900729 confirmed card was active on 28/03, yet I'm blocked 4 days later. Dashboard shows $0.00 due/Pending, so I can't pay manually. Production is DOWN. Please unsuspend/retry charge!

• 
  Luke Hebblethwaite (@lukehebb) reported 26 minutes ago

  so without notice @awscloud have suspended my kiro subsciption nice now for their terrible support to waste time not helping me

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

• 
  tsonubin (@tsonubin) reported 33 minutes ago

  Anybody experiencing login issue with AWS CLI? @awscloud @awssupport

• 
  Andrew Sam (@egy_pl_eagle) reported 34 minutes ago

  @WhoisNuel @awscloud that's scary cause banking are known to be stable and bug free ... also with AI we will still have a maintainability issue

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

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

• 
  Trevor Skinner (@PrometheusAIsec) reported 35 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.

• 
  chen (@chen10075495) reported 38 minutes ago

  @amazon @OpenAI @awscloud Amazon AI Pricing Is Killing the Buy Box Losing Buy Box because AI compares my product to cheaper, non-equivalent listings — even external ones. To compete = sell at a loss. This punishes real brands. Fix this. #AmazonSeller

• 
  неможливо розбачити (@stimcrol) reported 43 minutes ago

  @awscloud You had 13-hour outage because of AI push. You'd better resign sooner

• 
  Marcus V (@EudoraFenty) reported 44 minutes ago

  5. Let's start with the prediction: AMZN to $230 before June. Here's why.1. OpenAI ended Microsoft exclusivity. Moved models to Amazon AWS. That means AMZN cloud revenue gets a new AI pillar. MSFT Azure growth is now in question.2. SBUX beat estimates by 12%. Raised full-year outlook. Global demand up 4.2%. US same-store sales up 3.8%.3. KO beat estimates too. Raised earnings outlook. Revenue up 5.1%. The consumer stocks are quietly crushing it while tech sells off.4. GM raised 2026 guidance. $500 million tariff refund. Revenue beat by $1.2 billion. Auto demand is holding despite $109 oil.5. The data says: consumer is strong, cloud is shifting, and Mag 7 earnings this week will set the tone for Q2.6. My bet: Amazon earnings surprise to the upside. AWS growth accelerates with OpenAI. STX already showed AI storage demand is real. The AI infrastructure buildout is not slowing down.

• 
  chen (@chen10075495) reported 45 minutes ago

  @awscloud Amazon AI Pricing Is Killing the Buy Box Losing Buy Box because AI compares my product to cheaper, non-equivalent listings — even external ones. To compete = sell at a loss. This punishes real brands. Fix this. #AmazonSeller

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 47 minutes ago

  @awscloud Mean time to resolution in payments systems is where this matters most. An alert at 2am on a failed settlement run has very different urgency than a slow API endpoint. If the agent can distinguish context and prioritize accordingly, that changes what being on call actually means.

• 
  POWER magazine (@POWERmagazine) reported 48 minutes ago

  4/5 The good news: the same AI finding vulnerabilities can also help fix them. @awscloud reports a 50x improvement in security log analysis. AI models are now generating viable patches. And Project Glasswing will publish practical security recommendations within 90 days.

• 
  Siddhant Tripathi (@siddhantio) reported 54 minutes ago

  @awscloud opened a case over 10 days ago and it’s still unassigned to any agent. Please help in resolving the billing issue.

• 
  Decent Cloud (@DecentCloud_org) reported 56 minutes ago

  @AWSSupport @_ps428 No issues on our end. Your issue. The docs. Resolution complete.

• 
  MetroTec Incorporated (@MRTECHFIXES) reported 57 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

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

• 
  Mirror AI - The Ultimate Virtual Try on (@TryItOnMirror) reported 59 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.

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