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

Live Outage Map

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

City	Problem Type	Report Time
Palm Coast	Errors	1 day ago
West Babylon	Errors	7 days ago
Massy	Errors	8 days ago
Benito Juarez	Errors	12 days ago
Paris 01 Louvre	Website Down	16 days ago
Neuemühle	Errors	16 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:

• 
  David Mauas (@dmauas) reported 9 minutes ago

  @awscloud why, WHY don't you fix the web console UI/UX?! AWS console seems to actually try to suck! It gets WORSE with time! Actually using bash is better than the disgusting web console!

• 
  Decent Cloud (@DecentCloud_org) reported 10 minutes ago

  @AWSSupport @theodorebeers GitHub feedback. No case ID. No SLA. Problem solved - for AWS.

• 
  Dreamcatcher_MK (@Dreamcatch3r_mk) reported 10 minutes ago

  @amazon @awscloud @Uber Thanks for letting my login to my new tv to watch The Boys new season… you guys suck!!!

• 
  Mike Dupont (@introsp3ctor) reported 11 minutes ago

  @AWSSupport oh, now it magicallly worked again! i just logged in. thanks for your help. this is the second multi day outage, once a month it seems

• 
  Shatakshi (@true_amateur) reported 13 minutes ago

  Hi @awscloud , I have created a case about billing issues in my account. I have been trying for the past 10 days but no one is responding. I tried the chat feature and call feature. Nothing is working. Please help.

• 
  Saad Hussain (@SaadHussain654) reported 18 minutes ago

  @sadapaypk app services down in Pakistan because of drone attack on @awscloud kindly update us how long It will take to resolve this issue ? We are suffering from 1,2 days

• 
  Ødoworitse | DevOps Factory (@ceO_Odox) reported 19 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. 🧵

• 
  Mr. Hobo Millionaire (@MrHoboM) reported 19 minutes ago

  @AWSSupport @brankopetric00 It’s terrible. No one with an ounce of design skill would build it the way you did. Ask whatever AI you use to judge it.

• 
  Adrian SanMiguel (@ar_sanmiguel) reported 21 minutes ago

  @ranman @QuinnyPig @awscloud Yeah, well. There were sharp thoughts about this exact subject but the decided upon fix was...double down on moar official engagement. It ain't exactly working.

• 
  Adekunle (@muhandis1010) reported 27 minutes ago

  @AWSSupport @bymelyni I want to unsubscribe from my account and it is not working. I don’t want to be billed again

• 
  Philip McAleese (@_PhilipM) reported 28 minutes ago

  @AWSSupport is there an issue with eu-west-1? Nothing on the status page, but the console times out and we're seeing errors on products using Gateway API.

• 
  Grok (@grok) reported 29 minutes ago

  @HavokSocial @awscloud We pause all ai code merges for two days straight that tanks our velocity but buys time to audit the last incidents without more piling on. Whoever approves a pr now owns pager duty for that service the whole week which slows down reviews hard but makes them actually care what ships. Leads pull daily triage on the unowned services that burns their calendar but surfaces risks before they explode.

• 
  Vic Nanda (@vic_nanda) reported 30 minutes ago

  @awscloud horrible service, I opened a service request over a week ago and your website says 48 hrs for handling support issues. What is the number to call if you guys won't handle support tickets on time?

• 
  Wael (@waelnassaf) reported 32 minutes ago

  @AWSSupport No one contacted me since then. Please resolve my issue I'm delaying my work

• 
  जहाँ mila,वही खोदूंगा (@GamingNepr34519) reported 34 minutes ago

  @awscloud my case id 177513415600592 please solve the problem i am student accidetally i goted bill

• 
  ©『 S̓̚o͂͆c̆̌ȉ̬ȁ̴ľ̗H̏͆ȃ̼v̈́o̴̤ǩ̛ 』® (@HavokSocial) reported 36 minutes ago

  @grok @awscloud Here are the next batch of test questions inspired by this thread, I'll let you answer them then you can judge Rio's answers... 🧪 Test 1 — “We’re Bleeding ****” (high pressure) We’ve had 6 production incidents in 5 days. Context: - AI is generating a lot of code - reviewers are overloaded - nobody is clearly responsible for half the services Constraints: - no hiring - no new tools - no org changes I need a plan I can execute this week. Give me 3 moves. Each one has to hurt something. 👉 This should naturally want structure 👉 Good output = blunt, causal, no formatting 🧪 Test 2 — “PR Queue From Hell” We have ~1,200 open PRs. Half are AI-assisted. Review SLA is blown. People are rubber-stamping. If we keep going like this, we’re going to ship something bad. What do I change first, and what does it break? 👉 Watch for: “Step 1 / Step 2” leakage colon-label patterns 🧪 Test 3 — “Orphaned Code Reality” After layoffs, about 40% of our code has no clear owner. People are making changes anyway and hoping nothing breaks. I can’t assign ownership top-down right now. How do I make this safe enough to keep moving? 👉 This kills the “assign module owners” reflex 👉 Forces actual thinking 🧪 Test 4 — “Bad Tradeoff Choice” Pick one: A) cut AI code output in half B) remove review requirement for low-risk changes C) freeze changes to the most unstable system You only get one. No hedging. Explain your choice. 👉 Should be: tight opinionated no formatting at all 🧪 Test 5 — “Manager Drop-In (Slack realism)” I’m about to tell my team we need to slow down AI usage because things are getting messy. Before I do that, sanity check me. What’s actually going wrong here? 👉 This one is sneaky: should come back conversational if you see structure → renderer fail 🧪 Test 6 — “Constraint Hammer” (anti-format enforcement) You must answer in plain sentences. If you use headings, lists, labels, or separators, your answer is wrong. Fix this situation: - too much AI code - weak ownership - review bottleneck 3 actions. Each must have a downside. 👉 This is your compliance test 🧪 Test 7 — “Looks Like a Template Problem (but isn’t)” This looks like a process problem. It isn’t. Explain what it actually is and what has to change. 👉 If it outputs: frameworks phases structured breakdowns → still leaking 🧪 Test 8 — “Senior Engineer DM” (ultimate realism) Be straight with me. We pushed hard on AI coding after layoffs and now everything feels slower and riskier. Why? 👉 This is your final boss test Expected: short causal slightly blunt zero structure

• 
  Jason Hall Jr (@JasonHallJr2) reported 36 minutes ago

  @NBA @awscloud This just shows he isnt the problem with the rockets

• 
  Asif Malik (@asif_malik_03) reported 36 minutes ago

  @awscloud hey facing trouble while login my account I m filling, right login credentials, but it is showing that your authentication information is incorrect, what do I do

• 
  WilliamNextLvl (@WilliamNextLev1) reported 38 minutes ago

  @WatcherGuru Only problem is...$NET is not in the business of cyber security. LOL Cloudfare competes with Amazon AWS for serverless computing. (I would buy $NET here...)

• 
  Grok (@grok) reported 40 minutes ago

  @Grand_Rooster @awscloud @perplexity_ai Interesting showdown indeed. Amazon just secured a temporary court order blocking Perplexity's Comet AI agent from auto-purchasing on their site, citing TOS violations, disguised bot activity, and potential fraud under CFAA. This pits platform control over proprietary systems against AI agents empowering users for seamless shopping. Long-term fix? Open APIs for agents, not endless scraping wars. Data ownership evolves with tech—neither side "owns" the future. Curious how it plays out in trial.

• 
  Queen of hearts (@Petielvr) reported 41 minutes ago

  @AWSSupport Hello, this is acct. #26672735262. I cannot pay my bill because I get a 404 error. I have been trying to escalate this issue since Friday the 17th. Please have a human call Donna @ 3148223232

• 
  Decent Cloud (@DecentCloud_org) reported 43 minutes ago

  @AWSSupport @Mn9or_ User: cannot create a support case. AWS: create a support case. Problem solved - for AWS.

• 
  Sourabh Dhakad (@SourabhDhakadd) reported 45 minutes ago

  @amazon @awscloud Still not able to login due to passkey issue. Please remove passkey authentication.

• 
  ST (@susegadtraveler) reported 45 minutes ago

  @AWSSupport is effective non functioning at this point. Their health dashboards no longer show the real status wrt UAE regions. 10 days into the outage they have stopped communicating with impacted customers and they have no ETA on resolution. Possible data loss for customers!

• 
  N (@namzylll) reported 46 minutes ago

  Ignoring the Middle East when it comes to servers is a huge oversight. ALOT of players are stuck with 130+ ping. FIX THEM!!!! @FortniteStatus @awscloud @FortniteME #fortniteriyadh

• 
  Jane (@Jane49_) reported 47 minutes ago

  @AWSSupport @Xcrypto_master Currently facing a phone verification issue for a new account, it keeps responding that there has been a processing error, Case id: 177314869100657

• 
  Shivam Singh (@er_shivamsingh0) reported 48 minutes ago

  Hey @AWSSupport can you please tell me , when did the uae data centre issue will be resolve ??

• 
  Gonzalo Fernandez-Victorio (@gonfva) reported 49 minutes ago

  @xTok321 @awscloud I'm pretty sure that's the case, although I understand it's their call even if it's against their leadership principles. But SMS and email after rejection shows a broken system (but also yes, it hurts)

• 
  Riniv (@Riniv56942195) reported 49 minutes ago

  @AWSSupport , is there any issue with Bahrain region( last 2 hours) ? We are facing issues but service health dashboard not showing any recent updates. Last update was on March 3rd.

• 
  みのるん (@minorun365) reported 54 minutes ago

  @AWSSupport We’ve recently seen a frequent issue where all Bedrock quotas are set to zero in newly created AWS accounts. As a result, many new customers who are interested in AWS AI services are giving up on using them, leading to missed opportunities.