This topic describes how overdue payments impact ECS resources, how to settle them, and how to prevent service disruptions.
An overdue payment may suspend your services. You will receive reminders and notifications, but to avoid service interruptions, settle overdue bills promptly.
Impacts of overdue payments
Subscription ECS resources
Subscription ECS resources have an expiration date. For more information about the impacts of resource expiration, see Subscription.
While you can continue to use your subscription ECS resources after a payment becomes overdue, the following limitations apply:
You cannot perform operations that incur fees, such as purchasing, upgrading, or renewing an instance.
If a subscription instance has an attached pay-as-you-go disk or uses pay-by-traffic for public bandwidth, an overdue payment makes both the disk and the public bandwidth service unavailable. For more information, see Pay-as-you-go ECS resources.
Depending on how the disk is used, the detachment may fail. If detachment fails, billing for the disk stops, but you risk data loss. We recommend that you stop using these disks.
Pay-as-you-go ECS resources
Pay-as-you-go bills have three deduction attempts: on the settlement date (T), T+7, and T+14.
Within 15 days of an overdue payment: No service suspension
If the initial deduction on the settlement date (T) fails, the payment is considered overdue. For the next 15 days, your services remain active, but you cannot purchase new resources, upgrade instance configurations, or enable auto-renewals. The system attempts to deduct the fees again on T+7 and T+14.
ImportantInstances in economical mode have their computing resources (vCPUs and memory) reclaimed when stopped. If your account has an overdue payment, such an instance will fail to start. What is economical mode?
More than 15 days after an overdue payment: Instance is stopped
If all three deduction attempts fail, the instance is stopped and billing ceases on T+15. After the instance has been stopped for 15 days, the system begins to release or unbind the pay-as-you-go ECS resources.
The following table describes how ECS resources are handled after an instance is stopped due to an overdue payment.
Resource type
Stopped: Within 15 days
Stopped: After 15 days
Computing resources (vCPUs, GPUs, and memory)
The computing resources (vCPUs, GPUs, and memory) are retained, but the instance stops providing services.
When an instance stops providing services, you cannot remotely connect to it or access websites deployed on it. Business operations may also be disrupted.
The computing resources (vCPUs, GPUs, and memory) are released.
NoteIf computing resources (vCPUs, GPUs, and memory) are released due to an overdue payment, the system sends an email notification.
block storage
Disks and their data are retained, but the disks stop providing services.
Local disks and their data are retained, but the local disks stop providing services.
NoteAfter a disk stops providing services, it cannot process I/O read and write requests. This affects the instances to which the disks are attached. For example, the read and write performance of applications may decline, some operations may time out, and instances that run specific operating system versions may fail to shut down or restart.
Disks are released, and their data cannot be recovered.
NotePay-as-you-go data disks created with instances and pay-as-you-go data disks created independently on the disk page are released, regardless of whether they are attached to an instance.
Local disks are released, and their data cannot be recovered.
public IP
The static public IP address is retained.
The lifecycle of an EIP is independent of its associated ECS instance. For information about how an overdue payment affects an EIP, see Overdue payments for EIPs.
The static public IP address is released.
The lifecycle of an EIP is independent of its associated ECS instance. For information about how an overdue payment affects an EIP, see Overdue payments for EIPs.
snapshot
All snapshots and custom images are retained. However, automatic snapshot creation stops, and you cannot create manual snapshots. You also cannot create new custom images from the instance, as this action requires creating a snapshot.
When you settle the overdue amount, the automatic snapshot policy resumes.
All your snapshot resources, including snapshots, snapshot-consistent groups, and snapshots associated with custom images, are deleted. This data cannot be recovered.
If a snapshot is associated with a custom image, that custom image is also deleted and cannot be recovered.
When you settle the overdue amount, the automatic snapshot policy resumes.
ImportantDeleting a custom image does not affect running subscription instances created from it. However, you cannot re-initialize their system disks.
-
If the image was shared, other users can no longer view it, create instances from it, or re-initialize system disks of instances created from it.
-
If the image was published as a community image, the community image is also deleted. It can no longer be used to create instances, and system disks of instances created from it cannot be re-initialized.
Settle an overdue bill
An overdue payment can cause your pay-as-you-go ECS instances to be stopped. To avoid service interruptions, settle overdue bills promptly. Log on to the Expenses and Costs console. In the notification bar at the top of the Account Overview page, click Pay Now and follow the on-screen instructions to settle the overdue bill.
After settling an overdue bill, the system automatically restarts any instances that were stopped. If an instance fails to restart automatically, you can start it manually. For more information, see Start an instance.
Prevent service suspension
Release unused resources
If you no longer need an ECS resource, back up its data and release the resource promptly to prevent further charges.
Set a credit alert
Log on to the Expenses and Costs console and set a credit alert on the Account Overview page. When your available account credit is lower than the alert threshold, the system automatically sends a notification.
Set an automatic release time
Enable the automatic release feature for pay-as-you-go instances to prevent unexpected charges from instances that run longer than intended. For more information, see Release an instance.