Docs

Elastic Compute Service

Billing

Instructions on expiration

After a subscription-based DDH expires, the platform offers a resource retention period. During this period, you can renew or unsubscribe it based on your needs. If you do not perform any actions during the retention period, the associated resources will be forcibly released and are irrecoverable. This topic describes the expiration rules for subscription-based DDHs and the ECS instance resources running on them.

tip

At 7 days, 3 days, and 1 day before and on the expiration date of subscription-based DDH, the platform sends notifications by SMS, email, or onsite messages based on the notification method you specify to remind you that the resources are about to expire.

Once a subscription-based DDH expires, its status changes as shown in the following chart.

Once a subscription-based DDH and the instances residing on it expire, the resource status changes as shown in the following table.

tip

Before the instances are automatically released, you can migrate them to another subscription-based DDH for continued use. Other associated resources (such as volumes and EIP) can be migrated along with the instance. For details, see Changing host deployment.

Resource type			The expiration date ~ 12:00 noon of the next day	12 hours < Post-expiration duration ≤ 15 days	At 24:00 on the 15th day after the expiration
DDH			At 12:00 noon on the day following the expiration day, the DDH is shut down, and the status changes to "Stopped".	The DDH is shut down, and the status changes to "Stopped".	The DDH is forcibly released, and all associated configurations and data are permanently deleted and cannot be restored.
ECS instance			The ECS instance shuts down, and the status changes to "Stopped".	The ECS instance shuts down, and the status changes to "Stopped".	ECS instances are forcibly released, and all associated configurations and data are permanently deleted and cannot be restored.
Resources of ECS instances	Compute resources (vCPU and memory)	Compute resources are retained.	Compute resources are retained.	Compute resources are forcibly released, and all associated configurations and data are permanently deleted and cannot be restored.
		System volume/local volume	The system volume/local volume and the data on them are retained and billing continues.	The system volume/local volume and the data on them are retained and billing continues.	Automatically released with the instance. After the release, the data is cleared and cannot be restored.
		Data volume	The data volume and the data on it are retained and billing continues.	The data volume and the data on it are retained and billing continues.	Delete with the instance: The data volume is released data with instance upon deletion and cannot be restored. Do not delete with the instance: The data volume is disassociated from the instance, not automatically released, the data on the volume is retained by default, and billing continues. You can still mount the data volume to another instance.
		EIP	Applied EIPs are retained, the bandwidth is limited to 1 Kbps. EIP disassociation is supported.	Applied EIPs are retained, the bandwidth is limited to 1 Kbps. EIP disassociation is supported.	The EIP is disassociated from the instance and not released automatically, and the billing continues. You can associate the EIP with another instance.

View expiration time

You can view the expiration time of your DDHs on the DDH list page.

Renewal

If a DDH is not renewed after it expires, the resources will enter a retention period, and their usage will be restricted. Once the retention period expires, your resources will be forcibly reclaimed and cannot be restored. To continue use of the host resources, please renew within the specified period (before the resources are forcibly released).

Last updated: 2026.01.16 19:04:00