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
Rostock	Website Down	5 hours ago
Glendale	Website Down	11 days ago
Oakland	Sign in	13 days ago
Greater Noida	Errors	13 days ago
Alamogordo	Website Down	18 days ago
San Francisco	Website Down	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:

• 
  Basim Khalid (@basimkhalid) reported 3 minutes ago

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

• 
  Rahul Patel (@U_N_R_3_A_L) reported 3 minutes ago

  @AWSSupport I'm trying to reach out AWS support through chat but 1 hour in the chat and no one is joining, this is the 2nd time I'm facing this issue in month where I have to keep on waiting for the production issue.

• 
  JustAnotherEarthling *humorous/satirical* (@RobBoggs4) reported 3 minutes ago

  @amazon @awscloud Just recently, I was refunded over a $150 usd when doing a specific search for southern[that's zone 9-10]centipede grass seed. Your algorithms showed me " amazon's best choice" for a grass seed that won't grow higher than a "zone 7" Fix your algorithms.

• 
  alexand.ro (@alexand__ro) reported 5 minutes ago

  @AWSSupport 1 year old AWS account is blocked all of a sudden for not providing documents (after 1 year with no problems), but when I do provide them, I receive the same email back requesting the same documents. Please help me unblock this faster, my applications are down

• 
  None (@BourDeniz) reported 9 minutes ago

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

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

• 
  InnoCommerce (@InnoCommerce) reported 13 minutes ago

  @AWSSupport It's been almost 2 weeks and nobody is helping me while i have some serious problems with my AWS account. That's unbelievable

• 
  The OddsBreakers (@theoddsbreakers) reported 14 minutes ago

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

• 
  POWER magazine (@POWERmagazine) reported 16 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.

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

• 
  Maroun Mourani (@MarounMourani) reported 25 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 ?

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

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

• 
  monkey ∞ icp (@monkey898898) reported 29 minutes ago

  @RealAllinCrypto @coinbase @awscloud And $AWS has just brought down Coinbase for hours now (its still down indefinitely)! 😱

• 
  yourclouddude (@yourclouddude) reported 29 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 💸

• 
  Global Pulse (@Globalstats_77) reported 29 minutes ago

  🌐 Biggest Internet Outages in History ❶ 🇺🇸 CrowdStrike–Microsoft Outage (2024) — ~12+ hours ❷ 🇺🇸 Facebook Global Shutdown (2021) — ~6 hours ❸ 🇺🇸 Dyn Cyberattack (2016) — ~11 hours ❹ 🇺🇸 Amazon AWS S3 Outage (2017) — ~4 hours ❺ 🇺🇸 Fastly CDN Outage (2021) — ~1 hour ❻ 🇨🇦 Rogers Network Outage (2022) — ~24 hours ❼ 🇺🇸 Google Services Outage (2020) — ~45 minutes ❽ 🇺🇸 Cloudflare Global Outage (2025) — ~2.5 hours ❾ 🌍 Kazakhstan Internet Blackout (2022) — ~5 days ❿ 🇺🇸 X (Twitter) Global Outage (2025) — ~3 hours

• 
  TLM13 (@accuratetlm13) reported 31 minutes ago

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

• 
  Exchange Invest (@Exchange_Invest) reported 35 minutes ago

  Worrying times for @awscloud as various exchanges suffer another outage. More in today’s #ExchangeInvest.

• 
  Kunal (@kunal_twts) reported 39 minutes ago

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

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

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

• 
  Seedling (@Seedling001) reported 42 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.

• 
  CodieEditor (@CodieEditor) reported 44 minutes ago

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

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

• 
  tsonubin (@tsonubin) reported 46 minutes ago

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

• 
  Gajanan (@Gajanan_Shetkar) reported 51 minutes ago

  @AWSSupport Hope AWS continues supporting Indian startups during difficult situations like this. After 5 years of building on AWS, we’re still waiting for resolution while our production platform remains down. Requesting urgent assistance.

• 
  Dr. Mihir Sharma (@mihircurovana) reported 52 minutes ago

  @AWSSupport Hi @AWSSupport I don’t see any such option in the widget or anywhere in the console, is this an AISL or India specific issue maybe? I see no options to upgrade

• 
  Ødoworitse | DevOps Factory (@ceO_Odox) reported 55 minutes ago

  Every DevOps engineer knows "It works on my machine" is a lie. Hit a wall today deploying to @awscloud EC2—*** was begging for a password in a headless shell. ​Error: fatal: could not read Username. Reality: The source URL drifted, and the automation had no keyboard to answer. 🧵

• 
  Kai Antonio (@KaiAntonio61428) reported 55 minutes ago

  @awscloud Juggling all that info definitely slows things down. Centralizing it sounds like a smart move.

• 
  Andrew Sam (@egy_pl_eagle) reported 56 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

• 
  Rahul Khatri (@Rahulk644) reported 56 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

• 
  Henrique Lima (@HenriqueLi88059) reported 1 hour ago

  @AWSSupport @awscloud Update: our account has been reactivated! ✅ After 36+ hours down, our Medical Imaging platform is back online. Thank you to @AWSSupport and the verification team for resolving this. We hope no other healthcare platform has to go through this. 🙏