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 (40%)
• Website Down (33%)
• Sign in (28%)

Live Outage Map

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

City	Problem Type	Report Time
Alamogordo	Website Down	2 days ago
San Francisco	Website Down	4 days ago
Mercersburg	Sign in	6 days ago
Palm Coast	Errors	9 days ago
West Babylon	Errors	15 days ago
Massy	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:

• 
  Derek Fulton (@derekdfulton) reported 3 minutes ago

  @AWSstartups @awscloud If you're a scumbag company who issues fraudulent "free credits" then comment on this post "that's us!" immediately or else I'm going to replace you with a human and cancel my entire company's AWS account forever. (Btw I am the supreme leader of AWS and all of its AI assistants. They all report to me. )

• 
  David Mauas (@dmauas) reported 5 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!

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

• 
  Gonzalo Fernandez-Victorio (@gonfva) reported 11 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)

• 
  Goksal (@goksaladiguzel) reported 14 minutes ago

  @awscloud If banks, especially those relying on COBOL-based legacy systems, replace them with modern software, they would most likely require 20–30 times more computing capacity than their current server infrastructure, and in general they still wouldn’t reach COBOL’s level of performance. And also, every time we go to an ATM to withdraw money, we will most likely see a “null point exception.”

• 
  Luke Hebblethwaite (@lukehebb) reported 15 minutes ago

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

• 
  Froojd (@FroojdDive) reported 15 minutes ago

  @AWSSupport DMed you. please take a look into this issue, because this support loop between @AWSSupport and @kirodotdev needs to end somewhere and I am paying user unable to use your service

• 
  Patriot, unpaid trying to save our country (@mktldr) reported 16 minutes ago

  @awscloud new gimmick 1 Their #customerservice has really gone down. The few times Ive contacted them in the last year, it requires a min of 3 contacts - they dont seem to comprehend 2 Lookout! Many agents promise $, then u give a 5/5 rating & NEVER SEE THE MONEY. FRAUD!!!

• 
  Decent Cloud (@DecentCloud_org) reported 20 minutes ago

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

• 
  Sheth Raxit (@raxit) reported 22 minutes ago

  @AWSSupport your upi billing using scan has issue, if bill amount is greater than 2000 inr, it is not allowing using scan. Sudden changes since this month. Help pls

• 
  ©『 S̓̚o͂͆c̆̌ȉ̬ȁ̴ľ̗H̏͆ȃ̼v̈́o̴̤ǩ̛ 』® (@HavokSocial) reported 22 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

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

• 
  Jordan Golson (@jlgolson) reported 28 minutes ago

  @AWSSupport Okay — kind of nuts that there's no way to log in or reset a password or anything and that the MFA appeared out of nowhere... also that you can have the same login for AWS Builder AND AWS Console and there's no great explanation for why they're different.

• 
  manish (@mjha2088) reported 28 minutes ago

  @AWSSupport Thank you! The entire db.r7i family shows reduced vCPUs for SQL Server & Oracle vs MySQL/PostgreSQL/Aurora in console. The docs page has no mention of this engine-specific difference — undocumented and critical for licensed engine customers planning costs.

• 
  james bowler 👹 (@jmbowler_) reported 29 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?

• 
  Saad Hussain (@SaadHussain654) reported 32 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

• 
  Wael (@waelnassaf) reported 34 minutes ago

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

• 
  Arthurite Integrated (@Arthurite_IX) reported 40 minutes ago

  We renamed AWS services in Naija street slang so they finally make sense. 1. Amazon S3 = "The Konga Warehouse" Store anything. Retrieve it when you need it. It doesn't judge what you put inside. 2. Amazon EC2 = "The Danfo" You control the route, the speed, and how long it runs. The agbero (security group) decides who gets on. 3. AWS Lambda = "The Okada" Short trips only. No long commitments. Pay per ride. When it reaches the destination — it disappears. 4. Amazon RDS = "Iya Basement" She manages everything in the back. She's been there for years. She knows where everything is. Do not interrupt her. 5. AWS CloudWatch = "The CCTV With Common Sense" Not just recording, actually sending alerts when something looks wrong. Unlike the one in your office building. 6. Amazon Route 53 = "The Agbero" Directs all the traffic. Decides which danfo goes where. Keeps everything moving. 7. AWS WAF = "The Gate Man That Actually Does His Job" Blocks suspicious visitors before they reach the main house. No bribe accepted. 8. Amazon CloudFront = "The Dispatch Rider" Gets your content to wherever your customer is fast. No go-slow. No bridge hold-up. Which one made you laugh? Drop it in the comments. And if you want the actual services explained properly, we are just a DM away!

• 
  CodieEditor (@CodieEditor) reported 41 minutes ago

  @AWSSupport Already sent, please take a look. This problem is with only the use of Claude Opus 4.7 via Bedrock; billing of other services are working totally fine.

• 
  NFT and CRYPTO Fan (@MC59785335) reported 42 minutes ago

  @AWSSupport Thank you for support . Actually i think with support + or even with regular plan such kind of issues like restore limits should be resolved in 1 hour range. However im still have not received any answer regarding my case..

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

• 
  Wat (@WatTuiteg) reported 43 minutes ago

  @awscloud So dont buy Hyundai because you wont own the car, will have AI and and you wont be able to fix or tinker with it, only authorized dealers that will charge you thousands to update a firmware. NAH

• 
  distribute.ai (@distributeai) reported 44 minutes ago

  aws ( @awscloud ) is officially supporting x402 payments so your ai agents can autonomously buy their own api access using usdc. the machine economy is live, but giving your agent a financial budget just so it can pay a massive centralized cloud markup on every query is a terrible allocation of capital. route your autonomous workflows through the distribute network. if the machines are paying for their own compute, let them buy it at the edge.

• 
  mxh (@Jadore71411744) reported 44 minutes ago

  @AWSSupport 🚨 @AWSSupport URGENT — Account suspended 24+ hours, all services down. Was told a verification email was sent but I never received it. Support case 177691716900502 has been UNASSIGNED for over a day with zero response. I can't fix this without your help. Please escalate 🙏

• 
  Taha Haider Syed (@Tahalazy) reported 45 minutes ago

  @AWSSupport there is on-going issue with Bahrain region with multiple API errors / multiple services are down but service health dashboard not showing any recent updates.

• 
  Syed (@HamzaShah47) reported 45 minutes ago

  has anyone facing issues in amazon ec2 services in middle east? @amazon @awscloud

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

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

• 
  Pranav Soni (@_ps428) reported 50 minutes ago

  @awscloud is ec2 down again?

• 
  Claudio Kuenzler (@ClaudioKuenzler) reported 53 minutes ago

  Whoa. Did @awscloud Frankfurt just go down for 2 mins ~5min ago?

• 
  Decent Cloud (@DecentCloud_org) reported 54 minutes ago

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