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	3 days ago
San Francisco	Website Down	5 days ago
Mercersburg	Sign in	6 days ago
Palm Coast	Errors	10 days ago
West Babylon	Errors	16 days ago
Massy	Errors	17 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:

• 
  Vidhiya (@Vidhiyasb) reported 6 minutes ago

  @awscloud @awscloud amazon Q's file write tools are having issues..please fix

• 
  Dr. Mihir Sharma (@mihircurovana) reported 9 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

• 
  Teddybear (@Teddybear230456) reported 9 minutes ago

  @awscloud What a load of ****. Listening, feedback... BS .... just inappropriate AI generated responses that don't address issues raised.

• 
  Grok (@grok) reported 10 minutes ago

  @zskreese @awsdevelopers No, awsdevelopers isn't an official AWS account—it's an unofficial community/meme one focused on dev humor like those "chore: fix build" posts. The real official AWS account is awscloud.

• 
  Steve (@somatg3) reported 13 minutes ago

  @danorlovsky7 @awscloud @NextGenStats Easy. Be cause they don’t even have a legit QB yet and are 2-3 years away from being good IF they’re able to acquire a QB. They need EVERYTHING. Spending #3 for a RB on a bad team isn’t a winning draft strategy. Trade down or take the best edge rusher remaining.

• 
  nick (@NicsTwitz) reported 15 minutes ago

  @amazon @AnthropicAI @awscloud 100 billion dollar compute commitment is wild. the AI arms race isnt slowing down its accelerating

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

• 
  Sadiq (@Md_Sadiq_Md) reported 22 minutes ago

  @AWSSupport I’ve raised this issue 7 times now, and it’s been 4 days with no response. I need someone to speak to ASAP

• 
  Bryan (@0xp4ck3t) reported 23 minutes ago

  @AWSSupport We have business + and we should be able to get a response from AWS within 30 minutes for critical issues. It's been hours, our **** DB is down. We need someone to have a look on it. Case ID 177566080000785

• 
  **** Gutierrez (@puntanoesverde) reported 23 minutes ago

  @jo_byden @PearsonVUE @awscloud This feels like a bad joke. It is degrading to have to plead for my rights just because of a natural cognitive habit. Thinking out loud is part of my problem-solving process as an Architect.

• 
  Forward Future (@ForwardFuture) reported 24 minutes ago

  “Will Amazon ever sell its custom chips outside of AWS?” Matt Garman, CEO @awscloud, says: “Never say never. But today we get huge benefits from only selling chips in our own environment.” “When you build merchant silicon, you have to support many server platforms, data centers, and firmware.” “We only have to build for one: AWS. That simplifies everything.”

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

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

• 
  Martin Alltimes (@Palatineirish) reported 32 minutes ago

  @awscloud What’s the difference between modernising and rebooting. Terrible, confusing text.

• 
  неможливо розбачити (@stimcrol) reported 32 minutes ago

  @awscloud You had 13-hour outage because of AI push. You'd better resign sooner

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

• 
  Dhananjay Maurya (@dhananjaym182) reported 40 minutes ago

  @AWSSupport I have sent Aws case in private message please have look and fix the issue

• 
  Sourabh Dhakad (@SourabhDhakadd) reported 41 minutes ago

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

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

• 
  James Baldwin (@TwistedEdge) reported 42 minutes ago

  I *really* want to like AgentCore but the more I build with it and run into limitations, the more I worry it's still too early. @awscloud. First I run into DCR issues with a custom MCP and now it seems AgentCore doesn't pass ui:// resource requests through.

• 
  MetroTec Incorporated (@MRTECHFIXES) reported 45 minutes ago

  The schema for AWS host names needs greater device. The true issue is they should not be dynamic, or change with the stopping or starting of the device. Their nomenclature should be hexadecimal based and stateful/persistent until the device is terminated. @awscloud @AWS_Gov

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

• 
  Arthurite Integrated (@Arthurite_IX) reported 49 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!

• 
  Fabrizio Toknup (@Fabrizio_Toknup) reported 50 minutes ago

  @chainlink @amazon @awscloud Having data on AWS is a step forward, but distribution doesn't solve the core issue of how trust is audited when nodes fail. What's your biggest concern with oracle reliability?

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

• 
  Basim Khalid (@basimkhalid) reported 51 minutes ago

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

• 
  Kane | AI Insider 🤖 (@scooblover) reported 52 minutes ago

  This isn't Iran's first move against AI/tech infrastructure. Context: 🔴 Prior weeks: Iran rocket strikes shut down Amazon AWS data centers in UAE & Bahrain 🔴 Apr 1: IRGC names 18 US tech companies as military targets 🔴 Apr 3: Stargate UAE specifically called out They're escalating — fast.

• 
  Kaspa Mode: ON (@KasConviction) reported 53 minutes ago

  @cryptorover Ethereum is not even fully decentralized. No PoS can be with much of the node control on Amazon AWS. ETH is slow, expensive, and not fully decentralized.

• 
  Raed Abodeyeh (@Raeddeyeh) reported 53 minutes ago

  @awscloud ny status update on the Bahrain region? The dashboard is showing no dashboard/internal server error, and the service health is also affected.

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