If an ApsaraDB for Redis instance expires or has overdue payments, the instance may not be able to run normally. If you want to continue using the instance, you must renew the instance or enable auto-renewal for the instance.

Warning If an instance expires or has overdue payments, the system sends notifications to you. To prevent your service from being suspended, we recommend that you renew the instance or top up your account balance at the earliest opportunity.
When an ApsaraDB for Redis instance expires or has overdue payments, the instance is handled based on the time elapsed since the expiration date and the billing method of the instance. The following table describes how the instances are handled.
Table 1. Subscription instances
Time elapsed since the expiration date Description
Day 1 to day 15 The instance runs normally.
Day 16 to day 30 The instance is in the Disabled state and cannot be accessed. If you want to continue using the instance, you must renew the instance at the earliest opportunity. For more information, see Manually renew an instance.
Note
  • If the instance is in the Disabled state, the subscription duration starts from the time that you renew your instance. For example, if your instance expired on April 10, 2021 and you renewed the instance for one month on April 15, 2021, the instance expired on May 15, 2021.
  • If you do not renew an expired instance within a specified time period, the data stored on the instance may be lost. To prevent data loss, you can enable auto-renewal after you purchase the instance.
Day 31 to day 37

The instance is in the Released state. You are notified by text message or email. Data is retained for the next eight days. If you want to continue using the instance, you can restore the instance from the recycle bin. When you restore the instance from the recycle bin, ApsaraDB for Redis creates an instance by replicating the data of the original instance. For more information about the procedure, see Manage instances in the recycle bin.

Day 38
The instance is permanently deleted. The instance data is deleted and cannot be restored.
Warning To retain the instance data, you must renew the instance before it is deleted. Otherwise, the data cannot be restored.
Table 2. Pay-as-you-go instances
Time elapsed since the expiration date Description
Day 1 to day 15 The instance runs normally.
Day 16 to day 30 The instance is in the Disabled state and cannot be accessed. While the instance is in this state, billing of the instance is suspended.

If you want to continue using the instance, make sure that you have sufficient balance within your account. Billing is resumed after you top up your account and settle the overdue payments.

Day 31 to day 37

The instance is in the Released state. You are notified by text message or email. Data is retained for the next eight days. If you want to continue using the instance, you can restore the instance from the recycle bin. When you restore the instance from the recycle bin, ApsaraDB for Redis creates an instance by replicating the data of the original instance. For more information about the procedure, see Manage instances in the recycle bin.

Day 38
The instance is permanently deleted. The instance data is deleted and cannot be restored.
Warning To retain the instance data, you must renew the instance before it is deleted. Otherwise, the data cannot be restored.