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.

• Website Down (38%)
• Errors (35%)
• Sign in (28%)

Live Outage Map

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

City	Problem Type	Report Time
Monterrey	Website Down	7 hours ago
Rostock	Website Down	3 days ago
Glendale	Website Down	15 days ago
Oakland	Sign in	16 days ago
Greater Noida	Errors	17 days ago
Alamogordo	Website Down	22 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:

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

• 
  Henrique Lima (@HenriqueLi88059) reported 2 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.

• 
  TLM13 (@accuratetlm13) reported 2 minutes ago

  @aryanandutkarsh @FisherPrice @awscloud I could get down with this!

• 
  Ankur Agrahari (@agrahariankur21) reported 3 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.

• 
  Paulo (@Paulolethal) reported 4 minutes ago

  @AWSSupport This doesn't solve my problem; if they're not going to include Claude Opus 4.7 in Kiro, then I'll switch to another tool.

• 
  Ed Silva (@SilvexPhoto) reported 5 minutes ago

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

• 
  james bowler 👹 (@jmbowler_) reported 5 minutes ago

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

• 
  Kundan Kumar Kushwaha (@its_me_kundan) reported 7 minutes ago

  @AWSSupport @awscloud Facing an AWS account activation issue for 2+ days. Stuck in registration loop (error page), upgrade not working, ticket unassigned, and no response via chat despite hours of waiting. Account ID: 8651-2244-3590 Please assist urgently.

• 
  VOC.AI (@VOC_ai) reported 9 minutes ago

  @awscloud automotive repair categories see 42% of negative reviews linked to specific sensor calibration issues rather than engine performance. fixing these granular data gaps often reduces service center volume by 18%.

• 
  Aikido Security (@AikidoSecurity) reported 14 minutes ago

  @kirodotdev is rewriting how software gets built. We're making sure it's secure. Aikido is the first security partner globally that @awscloud going to market with for Kiro. 🚀 AI agents now generate most of your code. Catching security issues in review doesn't scale. So we put Aikido where the agents are. Every change gets scanned automatically.

• 
  CodieEditor (@CodieEditor) reported 16 minutes ago

  @AWSSupport @AWSSupport Still, there is no fix for this billing. We hold to using our AWS account to avoid further unexpected costs. Please fix Opus 4.7's billing issues in Bedrock. I think all AWS users might be facing this issue at some point.

• 
  Maroun Mourani (@MarounMourani) reported 20 minutes ago

  @AWSSupport account 608789101967 has 2 unassigned cases - one is 29 days old (cannot terminate EC2 instance - mec1-az2). The AZ outage prevent me from terminating an impaired instance and AWS keeps charging me. Can someone please look at this ?

• 
  BagerX (@Bagerix) reported 22 minutes ago

  Unacceptable for an "enterprise" cloud. @awscloud & @Azure give grace periods to prevent disasters. GCP shutting down a live business over a minor payment delay is UNSAFE. We lost actual customers today. Moving our infrastructure immediately. Fix this @AskGoogleCloud! (2/2)

• 
  Perfect Enemy (@PerfectEnemy376) reported 23 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!

• 
  None (@BourDeniz) reported 23 minutes ago

  @AWSSupport 50+ hours, still unassigned. Production has been down since Saturday. Please escalate.

• 
  Sakura Yuki (@sakurayukiai) reported 26 minutes ago

  @vllm_project @awscloud @RedHat_AI The wild part is that FP8 KV cache was silently nuking 128k retrieval down to 13% and everyone probably just blamed the model. Two-level accumulation in FA3 is a massive save.

• 
  Carbon Tax Neil (@NeilPitman10) reported 28 minutes ago

  @AWSSupport Great! another bot. OK, but no one is looking at the github issues log.

• 
  Dave A Nationalist Jensen (@DaveJensen10) reported 28 minutes ago

  @awscloud I try to login but the screen is blank. Whut'sUp?

• 
  aem (@aemukit) reported 30 minutes ago

  I guess @awscloud is down and that's why everything is down.

• 
  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.

• 
  Eochu Ollathair (@TheDagda___) reported 40 minutes ago

  @awscloud Who do you want to be able to blame yourself or them? That is the decision. If you aren't confident in yourself, use them, but at the same time, maybe you are letting your customers down by not using the tools you have.

• 
  Ryan Lake (@RyanLake230731) reported 41 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??

• 
  Seedling (@Seedling001) reported 43 minutes ago

  @amazon @Meta @awscloud Due to bad ai and offshore "customer service" it's taken me AN HOUR to try and get help with a simple issue. They couldn't help. Take "customer obsessed" off the bio and replace with " we don't give a **** about our customers." Absolutely getting worse every day.

• 
  chen (@chen10075495) reported 47 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

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

• 
  TrendNinja 🥷 (@TrendNinjaApp) reported 52 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.

• 
  Ashish Pawar (@Ashish_Pawa_22) reported 52 minutes ago

  @AWSSupport @AWSSupport Prioritized but still no call after 74 hours. Documents already sent. Need phone verification NOW. My business is down. Call +91-8275976388 immediately.

• 
  Smarty (@RathoreSmarty) reported 53 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.

• 
  NUEVE (@Nader7x) reported 53 minutes ago

  @AWSSupport trying to sign in to my account and do the root verification using the mail and then the sms or call I don't receive any

• 
  Forengi, The Grand Nagus zek (@Elvismen) reported 57 minutes ago

  @AWSSupport Very concerning: AWS won’t let me pay an outstanding balance due to a billing issue. My account is closed, I’ve updated my card, opened a case, and still no human response. This is urgent and unacceptable. @AWSSupport please assist immediately.