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 (83%)
• Errors (17%)

Live Outage Map

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

City	Problem Type	Report Time
Pottstown	Website Down	4 days ago
Iztacalco	Website Down	7 days ago
Boca da Mata	Errors	19 days ago
Township of Evan	Website Down	1 month ago
New York City	Website Down	1 month ago
Ciudad Jardín	Website Down	2 months 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:

• 
  Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported 6 minutes ago

  @ivanburazin Why are you still using windows server ? It’s less than 10 minutes to fire up a @awscloud ECS cluster running free Linux

• 
  Mohammed Nafees (@mnafees) reported 6 minutes ago

  yo @awscloud seems like a broken cert chain from your side

• 
  TechThought.org (@TechThought_org) reported 10 minutes ago

  An era ends for human data annotation. @awscloud is shutting down Mechanical Turk after 21 years as LLMs take over micro-tasks, per @techradar. What happens to training baselines when synthetic data completely replaces human feedback? #AI #Automation #AIeconomy techradar .com/pro/aws-is-shutting-down-mechanical-turk-which-let-humans-beat-ai-at-certain-work-tasks

• 
  🦋Kieran🦋 💻 (@sir_divs_alot) reported 11 minutes ago

  🚨 @AWSSupport I've been unable to create a Kiro subscription for 2+ weeks, getting error"account is not authorized to make this call." I have an active account, valid billing, and correct IAM Identity Center Organization instance setup. Case #178567212700620 escalate urgently.

• 
  Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported 11 minutes ago

  @AWSSupport @AWSSupport @awscloud small business now facing issues with clients. Have provided all details and past 2hrs downtime on production server. Case 178699777500302 with Bill B. Also case 178555512600788, open since Aug 4, no response.

• 
  WPBeginner (@wpbeginner) reported 14 minutes ago

  You have spent months building your WordPress site. What happens the day it suddenly goes offline? 😱 It happens all the time. We have heard several scary stories. A plugin conflict, a bad update, or a security breach can wipe out your complete website without any warning. The scary part is that most site owners assume their host has them fully covered, right up until they actually need to restore. We have tested countless backup tools on our own projects, so we put together the exact methods we trust to keep a site safe. Here is what you will learn: ✅ Pick the Right Method: Compare backup plugins, host backups, and manual cPanel or FTP so you know which fits your skill level. ✅ Back Up the Full Site: Save your database, themes, plugins, and uploads together so you can restore everything, not just your posts. ✅ Automate It With @DuplicatorWP: Schedule daily or weekly backups and send them straight to the cloud so you never have to remember. ✅ Store Copies Off Your Server: Keep backups in Google Drive, Dropbox, or Amazon S3 so one server crash never takes your site and its backup at once. ✅ Restore in Minutes: Use a disaster recovery link to bring your site back even when it is completely broken. Ready to protect all that hard work before disaster strikes? Read our complete step-by-step guide from the link in the comments 👇 (Link is in the thread below)

• 
  Joy | 🔥 (@JoyKingdomx) reported 16 minutes ago

  As we all know, cloud outages are not a new topic here. But what is changed is how many products now depend on the same infrastructure. A few years ago, an AWS outage mostly affected AWS customers. Where today one infrastructure issue can ripple across AI apps, APIs, developer tools, streaming platforms and payment services. That is the downside of concentration. We have seen @awscloud outages impact millions. We have also seen @OpenAI outages pause production apps because entire inference pipelines depended on a single provider. It is not the outage that matters - it is the dependency behind it. That is the reason why decentralized compute makes sense. Instead of relying on a single cloud or region, @ionet distributes compute across a global network of GPUs in 138+ countries. No infrastructure is immune to failure, the goal is to ensure one failure does not become everyone's failure.

• 
  lak-alak (@baricadelane) reported 17 minutes ago

  @IanCarrollShow @BacklotOPS @NickJFreitas They must think we are stupid Tyler Robinson decoys all over the place d captured on camera all doing their part for 1990s pixalated images produced and sold as 4k in 2026 lmao. Why did Amazon aws services shut down 9/10 - 9/25? Who owns discord?

• 
  Samrat Singh (Sam) (@isamrats) reported 19 minutes ago

  @KahlonGurshaan @Rushike32313211 Yes its down , but no official confirmation posted by @awscloud yet

• 
  Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported 21 minutes ago

  @AWSSupport now at 3:13 and counting with production server down

• 
  Hannan (@truehannan) reported 23 minutes ago

  @AWSSupport Why AWS console is not opening? Its soo much slow even my internet and everything is fine. I used VPN too but nothing worked

• 
  ShenYubao (@ssybb1988) reported 23 minutes ago

  @AWSSupport @awscloudAWS account suspended for additional verification; Production services down for ~24h. All verification docs submitted. Unable to purchase Business Support+ due to suspension. Please expedite review & help restore production. Case ID: 178678971500932

• 
  ❤️‍🔥ViBe GuY_PrinCe😉 (@777PrinceFreaky) reported 25 minutes ago

  Amazon has very poor service in Warranty and Claim Procedure To Customer fix this for me soon @amazonIN @awscloud @AmazonHelp

• 
  David Bauer (@realDavidBauer) reported 25 minutes ago

  Hey @BrianRoemmele two surprising things with Grok Bot I wanted to share and get your thoughts. 1) A lot of systems online use Cookie IP Validation, as you probably know. You log in, if your IP address changes, you're prompted to log in again. Grok Bot seems to use a different IP address at almost every interaction so it fails where IP validation is used. Sometimes it fails silently. I had to temporarily disable IP validation on some of my systems to work with Grok Bot. If it wasn't my systems and I hadn't seen the problem, an average user might just blame Grok Bot. Grok Bot just sat there waiting 30 minutes for connections to respond that would never have responded until I recognized it. 2) Grok Bot is hosted at Amazon AWS! Shocking. I consider that a potential reliability issue. I would've expected Grok Bot to be hosted on X servers. Screenshot:

• 
  OneTradeWex (@OneTradeWex) reported 26 minutes ago

  $CBRS is trying to challenge $NVDA indirectly, here’s how: While $NVDA focuses on incredibly small and powerful chips, $CBRS has built a massive, highly specialized AI scaling semiconductor. This greatly decreases the amount of cloud tokens needed to process a large language model, effectively saving AI companies millions of dollars in the long run. Think of $NVDA racks as an industrial kitchen and $CBRS chips as a microwave, when all you need to do is cook a hot pocket you want the microwave for efficiency. $CBRS announced that core revenue more than doubled year-over-year to $210 million in its Q2 earnings report while its cloud business nearly quadrupled. The company also raised its 2026 revenue guidance to between $880 million and $890 million. If $CBRS can successfully fulfill their contracts with @OpenAI and @awscloud on time and at scale we will see even more growth, if not them only having two primary customers will be their down fall. Looking at the technical setup we see $CBRS is coming down into its months long support channel. If it holds the $180-$160 level I see no reason for it not to bounce back to $215 to $230.

• 
  Mon (@mon73x) reported 31 minutes ago

  @asimrazax @AWSSupport I have the same problem. Did you fix it?

• 
  masaki (@silenthill_x) reported 31 minutes ago

  @AWSSupport Could someone please take a look at my support case? I opened a case 6 days ago because my RDS Reserved Instance is showing "Payment failed", but the case is still unassigned. The automated AWS Support response confirmed that my account is in good standing, my payment method is valid, and my invoices are fully paid. It also indicated that this appears to be a reservation processing issue rather than a payment issue. I've tried both Phone and Chat but haven't been able to reach an associate. Could you please help me get this case assigned? I can provide the Case ID via DM.

• 
  Drama Memes (@drama_meme) reported 35 minutes ago

  @cgeorgiaw @AnthropicAI @awscloud Someone tell me why this is a hard problem and you can’t just do $ diff normal.genome sick.genome ? I am guessing it’s a statistical thing, but, if it were random then how would you figure out what’s different??

• 
  PHICER (@phicerhq) reported 38 minutes ago

  @awscloud Resolving issues before customers notice is valuable, but proactive agents need clear consent, confidence thresholds, escalation paths, and reversible actions. Observability should explain not only what happened, but why the agent was allowed to act.

• 
  Arian van Putten (@ProgrammerDude) reported 40 minutes ago

  @QuinnyPig @awscloud Are they gonna fix that IAM identity center stored passkeys on a domain that is shared between aws orgs and accounts so I keep locking myself out of orgs when updating one?

• 
  MrWho (@Mrwho23) reported 43 minutes ago

  @AWSSupport I create a case for your support and till now waiting for the reply My whole system and company is waiting for your support, but you are so slow

• 
  Chris (@Mcatbeast) reported 45 minutes ago

  @AWSSupport Apologies for the earlier frustration. Turns out it was an issue from our end! My user was accidentally deleted.

• 
  mark seery (@140ismymax) reported 48 minutes ago

  Peter DeSantis talking at #agenticaisummit There will NOT be one AI chip type. If multiple AI chips take multiple years to bring to market, you have to be making assumptions about model requirements in that time frame. It's a systems problem, including the network. Constraint drives innovation. Future is bright and built together. Peter DeSantis SVP, Foundational AI Models, Custom Silicon, Quantum Computing, Amazon @awscloud @amazon @BerkeleyRDI

• 
  Maciej Wilczyński (@wilczynski24) reported 48 minutes ago

  @opsolutehq @awscloud Otherwise, I believe it's not fully viable for full-range products. Example of Lovable: they have hundreds of potential use cases. That's where they are on credit-based systems rather than outcome-based systems, because you can't narrow down the overall cafeteria of use cases.

• 
  Ranbir Mahapatra (@ranbirnxt) reported 50 minutes ago

  @QuinnyPig @awscloud Is NAT Gateway a ‘pricing’ bug that you would care to fix? Forever?

• 
  Weaver Labs (@Weaver_Labs) reported 56 minutes ago

  @amazon @awscloud @nvidia AI infrastructure is becoming a full-stack problem. GPUs are only one piece now, with networking, compute and data infrastructure all needing to scale together.

• 
  Jared Cassidy (@depach) reported 1 hour ago

  @grhmc @QuinnyPig @awscloud Not fixed on mine I login every day 🥲 did you have to set anything?

• 
  Adel Bucetta (@adelbucetta) reported 1 hour ago

  @tushaarmehtaa @OpenAIDevs @awscloud back to school is just a Band-Aid on a larger issue: how do we make building with ai accessible for the next 50 million people, not just 50?

• 
  Dhananjay (@DhananjayKhark2) reported 1 hour ago

  @AWSSupport Case open since Aug 13 — 15 days, no fix! AWS Glue blocked with AccessDeniedException (account-level) in ap-south-1. NOT an IAM issue. Needs backend account verification sync. Case: 178661799100381 Please escalate! 🙏 #AWS #AWSGlue @awscloud @AWSCloudIndia

• 
  Corey Quinn (@QuinnyPig) reported 1 hour ago

  @awscloud You have all the tools to fix this, someone’s just apparently too scared to give Charlie a crossbow and diplomatic immunity. Give him the crossbow and stand back, @satyanadella.