Skip to content

EC2 Instance Stuck in "Stopping" State after AWS Issue Last Night (MST)

-2

Can I please get the Instance ID: i-b749f963 in Availability Zone: use1-az4 (us-east-1b) stopped? All of my attempts to Stop and Force Stop from the console have failed.

This instance became unresponsive and went into an instance status check failed alarm last night (MST) due to an AWS issue. "Between Wed, 27 May 2026 03:53:06 GMT and Wed, 27 May 2026 04:29:00 GMT, a subset of EC2 instances were unavailable in the us-east-1 Region. The issue has been resolved and the service is operating normally. Your affected EC2 instances are listed in the “Affected resources” tab of the AWS Personal Health Dashboard."

Thank you, Timm

  • This is still not a place to enter techincal support cases. For technical support you should go through the AWS Support console with a paid techincal support plan. Requesting action to a public Q&A forum is not going to do anything.

  • For the user that flagged my post, I am UNABLE to create a TECHNICAL support case, even though I should be able to. Hence my post here.

  • No action will be taken then. Your severely misconstrued if you think AWS support takes actions based of some Q&A forum. If you can’t open a technical support case then you should have a paid plan or redeploy it with IaC like everyone else would.

asked 12 days ago43 views
2 Answers
1

I understand your EC2 instance is stuck in the "stopping" state following the AWS issue you experienced. This typically occurs due to underlying hardware problems with the host computer.

Since you've already attempted to force stop the instance from the console without success, here are your next steps:

Immediate Options:

  1. Try AWS CLI Force Stop: If you haven't already, you can attempt to force stop the instance using the AWS Command Line Interface with the stop-instances command and the --force parameter. The CLI may succeed even when the console method fails.

  2. Request AWS Support: Since your force stop attempts have failed, you should create a technical support case in the AWS Support Center. Given that this issue is related to the documented AWS service event, AWS support will be able to intervene directly with the underlying infrastructure to resolve the stuck instance.

  3. Post on AWS re:Post: Alternatively, you can request help on AWS re:Post for community assistance.

Important Notes:

  • There is no charge for instance usage while your instance is in the "stopping" state or any other state except "running"
  • If the instance cannot be stopped or terminated, you may need to create a replacement instance by creating an Amazon Machine Image (AMI) from the stuck instance and launching a new instance from that AMI

Given the connection to the documented AWS service event, I recommend opening a support case so AWS can directly address the underlying infrastructure issue affecting your instance.
Sources
Troubleshoot Amazon EC2 instance stop issues - Amazon Elastic Compute Cloud
Methods for stopping an instance - Amazon Elastic Compute Cloud

answered 12 days ago
AWS
EXPERT
reviewed 12 days ago
-1
Accepted Answer

Since it won't stop, and since AWS doesn't provide technical support for their issue, I terminated the EC2 instance. It is now stuck at "shutting-down" and has been for over an hour. Since I don't get billed for EC2 instance that are not in a "running" state, I guess it is AWS' problem.

Maybe it will just go away one day.

answered 12 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.