Rules for overdue payments of pay-as-you-go RDS instances - ApsaraDB RDS

If your Alibaba Cloud account has overdue payments, all pay-as-you-go ApsaraDB RDS instances that belong to your account will be affected. You can unlock or rebuild these instances within a specific period of time. Subscription RDS instances are not affected by overdue payments.

Warning

If your Alibaba Cloud account has overdue payments, your RDS instances may be suspended. The system sends you a notification of the issue. To prevent service interruptions, we recommend that you add funds to your account at the earliest opportunity.

Overdue instance status

You cannot manually release instances during the period when your Alibaba Cloud account has overdue payments.

Instance status	Operation
Days 1 to 15 after payment becomes overdue: The instances run normally with the status Running.	Go to the Account Overview page to view the overdue payment details, and click Pay Now to go to the Payment Method Management page to bind a payment method (supporting bank cards, PayPal, etc.). Ensure that the bound payment method can cover the current overdue amount and subsequent pay-as-you-go billing items that may be generated by the instances to ensure normal use of your Alibaba Cloud account. After the overdue payment is cleared, locked instances will immediately return to normal operation.
Days 16 to 30 after payment becomes overdue: The instances are stopped and billing ceases. The instances enter the Locked state.
From Day 31: The instances are released and are moved to the recycle bin for eight days. The backup files of the instances are retained for eight days.	After an instance is released, you can rebuild the instance from the recycle bin within the 8-day retention period to restore the instance to a new instance. For more information, see Use the recycle bin feature of an ApsaraDB RDS for MySQL instance. Important Specific instances are not moved to the recycle bin. For more information, see Use the recycle bin feature.
Day 9 after instances are released: The backup files of the instances are no longer retained, and the instances are deleted from the recycle bin. The following section describes the scenarios in which the backups of the instances are still retained. Note After an instance that meets the following conditions is released, the backup files of the instance are retained based on the configured backup policies: The cross-region backup feature is enabled for the instance and the cross-region backup retention period does not elapse. For more information, see Use the cross-region backup feature of an ApsaraDB RDS for MySQL instance. Before the instance is released, a backup retention policy after instance release is configured. For more information, see Configure the backup retention policy after instance release.	In this case, you cannot rebuild the instance and the data of the instance is permanently deleted after the instance backup files are deleted.