You need to enable JavaScript to run this app.
Elastic Compute Service

Elastic Compute Service

Copy page
Download PDF
Billing
Instructions on expiration
Copy page
Download PDF
Instructions on expiration
After a Subscription instance expires, the platform offers a retention period. During this period, you can renew or unsubscribe it based on your need for continuous use. If you do not perform any actions during the retention period, the resources associated with the instance will be forcibly released and are irrecoverable. This topic describes the impact to Subscription instances when they expire, as well as the procedures for handling resources after expiration.​
tip​
If you no longer require a Subscription instance after it expires, manually delete it during the retention period. For more information, refer to Deleting instance.​
Impact of expiration​
Once a Subscription instance expires, the status of the instances changes as shown in the following chart.​
tip​
For Subscription instances, 7 days, 3 days, and 1 day before and on the expiration date, the platform sends notifications by SMS, email, or internal message based on the notification method you specify to remind you that the resources are about to expire.​
​​​
Instructions on release after expiration​
  • Expiration time: 23:59:59 on the expiration date.​
  • Stopping time: 12 hours after expiration.​
After the stop, the status of the Subscription instance changes to "Stopped". In the "Billing method" column, "Stopped" is displayed.​
  • Release time: 15 days after expiration.​
Instructions on resource status after expiration​
The following table shows the resource status at different stages after expiration.​
​
Resource type​
The expiration date ~ 12:00 noon of the next day​
12 hours < Post-expiration duration ≤ 15 days​
Post-expiration duration > 15 days​
Compute resources (vCPU and memory)​
The compute resources are retained.​
The following features are unavailable:​
  • Changing instance type​
  • Change the billing method from Subscription to Pay-as-you-go​
  • Changing operating system​
The compute resources are retained.​
The following features are unavailable:​
  • Changing instance type​
  • Change the billing method from Subscription to Pay-as-you-go​
  • Changing operating system​
  • Starting or restarting instance​
The resources will be forcibly released, and all associated configurations and data will be permanently deleted and cannot be recovered.​
Image​
The image is retained, with limited use.​
The image is retained, with limited use.​
The image is retained, with limited use.​
Local volume​
The local volume and the data in it are retained.​
The local volume and the data in it are retained.​
The resources will be forcibly released, and all associated configurations and data will be permanently deleted and cannot be recovered.​
Elastic Block Storage​
The system volume, data volume, and the data in them are retained.​
The system volume, data volume, and the data in them are retained.​
Subscription volume is released, all associated configurations and data will be permanently deleted and cannot be recovered.​
tip​
If you have manually mounted a Pay-as-you-go volume and set it to delete with the instance, this type of Pay-as-you-go volume will also be released. If not set to delete with the instance, it will be automatically disassociated.​
EIP​
(associated with the primary private IP address of the primary network interface of the instance)​
The EIP applied is retained.​
  • You can dissociate an EIP.​
  • You can associate an active EIP.​
The EIP applied is retained.​
You can dissociate the EIP, but the bandwidth will be limited to 1 Kbps.​
  • Subscription EIP: Forcibly disassociated.​
  • If yes, it will be released together with the instance.​
  • If no, it will be disassociated from the instance. You can still associate it with other instances.​
EIP​
(associated with the secondary private IP address of the primary network interface of the instance or associated with the secondary network interface of the instance)​
The EIP applied is retained.​
  • You can dissociate an EIP.​
  • You can associate an active EIP.​
The EIP applied is retained.​
You can dissociate the EIP, but the bandwidth will be limited to 1 Kbps.​
Forcibly disassociated.​
​
View expiration time​
You can view the expiration time of your Subscription instance by following these steps:​
  • On the Instances page, view the expiration time in the "Billing method" column.​
  • Click the instance name to enter the details page. In the Billing information section, find the expiration time.​
Renewal​
If a subscription instance 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 recovered. To ensure uninterrupted usage of ECS resources, renew them within the specified period (before the resources are forcefully reclaimed). When renewing, you need to pay the fees that are due from the expiration time to the renewal time. For more information, refer to Instructions on renewal.​
After a renewal succeeds, the status of the Subscription instances is as shown in the table below.​
tip​
  • Whether renewal is made before or after the expiration suspension (12 hours after expiration), the instance status after successful renewal is the same as that before the expiration.​
  • Upon service renewal and recovery, the new billing cycle starts from the expiration date of the previous cycle, rather than the recovery date. For example: If the instance expiration date is June 30, and you complete renewal and recovery for 1 month on July 5, the new cycle is June 30 to July 30, not July 5 to August 5.​
​
Billing method​
Before expiration​
Upon expiration​
Stopped upon expiration​
After renewal​
Subscription instances​
In service​
In service​
Normal Mode​
In service​
​
Normal Mode​
Normal Mode​
Normal Mode​
Normal Mode​
​
FAQ​
​
​
​
​
​
Last updated: 2026.07.07 11:28:28