Elastic Compute Service:Overdue payments

Causes

If the credits in your Alibaba Cloud account, including the account balance and vouchers, are insufficient to cover the required payments, your account has overdue payments.

Impacts of overdue payments

Pay-as-you-go ECS resources

The system attempts to deduct the fees for pay-as-you-go resources three times: on the due date (T), day T+7, and day T+14.

• Within 15 days after a payment becomes overdue

  If the fees for a pay-as-you-go instance fail to be deducted on day T, the payment for the instance becomes overdue. Within 15 days after the payment becomes overdue, the instance continues running. You can continue using existing resources, but cannot purchase resources, renew resources, or upgrade instance configurations. The system attempts to deduct the fees on day T+7 and day T+14.

• More than 15 days after a payment becomes overdue

  If all attempts to deduct the fees for the pay-as-you-go instance fail, the instance is stopped on the 15th day after the due date (day T+15) and billing for the instance also stops. More than 15 days after the instance is stopped, the system releases, detaches, or disassociates the resources of the instance.

  The following table describes whether resources of an ECS pay-as-you-go instance are retained or released within and more than 15 days after the instance is stopped.

  Resource	Within 15 days after the instance is stopped	More than 15 days after the instance is stopped
  Computing resources (vCPUs and memory)	The computing resources (vCPUs and memory) of the instance are retained, but the instance stops providing services. After an instance is stopped, you cannot connect to the instance or access the websites that are deployed on the instance. Service errors may also occur.	The computing resources (vCPUs and memory) are released. Note If your computing resources (vCPUs and memory) are released due to overdue payments, the system sends you an email notification.
  Block storage devices	Cloud disks and data that is stored on the cloud disks are retained, but the cloud disks become unavailable. Local disks and data that is stored on the local disks are retained, but the local disks become unavailable. Note After cloud disks or local disks become unavailable, they cannot properly process read/write requests. This affects the operation of the instances to which the disks are attached. For example, the read/write performance of applications may significantly degrade, an extended period of time may be required to perform specific operations, or instances may be unexpectedly shut down or cannot restart if the instances use specific operating systems.	Cloud disks are released and data that is stored on the cloud disks cannot be recovered. Note Data disks that are created together with pay-as-you-go instances and pay-as-you-go data disks that are separately created on the Disks page in the ECS console are released. Local disks are released and data that is stored on the local disks cannot be recovered.
  IP addresses	If the instance is located in the classic network, the public IP address of the instance is retained. If the instance is located in a virtual private cloud (VPC), the following rules apply: The public IP address is retained. Important If the economical mode is enabled before the instance is stopped, the public IP address of the instance may be recycled after the instance is stopped due to an overdue payment. The public IP address may change when the instance is started again. The elastic IP address (EIP) that is associated with the instance remains unchanged.	If the instance is located in the classic network, the public IP address of the instance is released. If the instance is located in a VPC, the following rules apply: The public IP address is released. The EIP is disassociated from the instance.
  Snapshots	All snapshots are retained, but automatic snapshots cannot be created.	All snapshots are deleted, except for snapshots that were used to create cloud disks or custom images.