Rules for overdue payments of pay-as-you-go ApsaraDB 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 become overdue. You can unlock or rebuild overdue pay-as-you-go RDS 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

If your Alibaba Cloud account has overdue payments, all pay-as-you-go RDS instances that belong to your account become overdue. If you have an overdue payment, you cannot release your RDS instance before you add sufficient funds to your Alibaba Cloud account.

Instance status	Operation
Day 1 to 15: The instances run as normal.	Check the balance of your Alibaba Cloud account and add funds to your account at the earliest opportunity.
Day 16 to 30: The instances are stopped and no longer billed.	Check the balance of your Alibaba Cloud account and add funds to your account at the earliest opportunity. The RDS instances immediately run as normal.
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, Use the recycle bin feature of an ApsaraDB RDS for SQL Server instance, Use the recycle bin feature of an ApsaraDB RDS for SQL Server instance, and Use the recycle bin feature of an ApsaraDB RDS for MariaDB 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, Use the cross-region backup feature of an ApsaraDB RDS for SQL Server instance, and Use the cross-region backup feature of an ApsaraDB RDS for PostgreSQL instance. Before the instance is released, a backup retention policy after instance release is configured. For more information, see Use the backup for deleted instances feature.	In this case, you cannot rebuild the instance and the data of the instance is permanently deleted after the instance backup files are deleted.