When a Cache for Redis instance expires or the account is overdue, you must recharge or renew promptly to unlock the instance. This topic describes the impact of instance expiration or overdue payments.

Arrears

If the available balance in your account (including account balance and vouchers) is less than the bill to be settled, your account will be considered overdue. You will then receive an SMS or email reminding you to top up promptly to settle the overdue bill; otherwise, you will not be able to use Cache for Redis resources normally.

When your account goes into arrears, this has a different impact on Redis instances with different billing methods.

Pay-as-you-go instances

Yearly or monthly subscription instances

tip

Bills for Pay-as-you-go instances are generated hourly, and payments are settled in real-time after the bill is issued. Regardless of whether instance resources are frozen or released, you must settle the fees for bills that have been issued.

After a Redis instance enters the Closed state due to overdue payments or expiration, its associated public IP address (EIP) will not be automatically disassociated by the system. Instead, it will be retained and follow the EIP's own lifecycle. The instance's public IP address will only be deleted when the EIP is released or manually disassociated by you. During this period, you can calmly complete renewal or temporary business recovery. The public IP address is typically retained for more than 24 hours.

Time in arrears	Impact
Within 2 hours	Overdue is displayed under Billing method. The instance status is Running, and the instance works normally.
Over 2 hours	Overdue is displayed under Billing method. The instance status is Closed and it cannot be used. You must go to the Billing center to recharge your account. When the outstanding bill is settled and the amount available in the account is above 0, the instance status will automatically revert to Running. tip Billing is suspended for instances whose status is Closed. If instance uses additional bandwidth, when the instance enters the Closed status, the additional bandwidth will be automatically released immediately. If you need to continue using additional bandwidth, you need to wait for the account recharge to be completed and the instance to be restored to Running before adding additional bandwidth again. For more details about additional bandwidth, refer to Modifying bandwidth.
168 hours (that is, 7 days) after shutdown	The instance is forcibly deleted. The system automatically selects the corresponding default backup policy based on the instance type, where: Primary-secondary instance: A final backup will be created by default before deleting the instance, and it will be retained for 7 days after successful creation. It is recommended to download and save it locally promptly. You can view or download backups of deleted instances on the Backups page and restore instances based on the backups. For more details, refer to Restoring deleted instance. Single node instance: Single node instances do not support persistence and backup functions. No backup will be created by default when deleting, and instance data will be completely cleared after deletion. Please proceed with caution. For more details about single-node instances, refer to Product architecture. tip If an instance is closed due to an overdue account, it will be forcefully deleted even if deletion protection is enabled. For more details, refer to Instance deletion protection.

Expiration

Pay-as-you-go instances

Yearly or monthly subscription instances

Only subscription instances will expire. There is no time limit for the pay-as-you-go instances. You only need to ensure that your account has sufficient balance.

Expiration time	Impact
Expiration to 12:00 the next day	Expired is displayed under Billing method, but the instance status is still Running. The instance can be used normally.
Within 168 hours (that is, 7 days) after expiration	Overdue is displayed under Billing method. The instance status is Closed and it cannot be used. You need to renew the instance, and the status of the instance will automatically revert to Running. For specific procedures of instance renewal methods, refer to Automatic and manual renewal. tip Billing is suspended for instances whose status is Closed. If instance uses additional bandwidth, when the instance enters the Closed status, the additional bandwidth will be retained but not billed. After you complete the renewal operation for instance and the instance is restored to Running, the additional bandwidth will also automatically become available again and billing will resume. For more details about additional bandwidth, refer to Modifying bandwidth.
168 hours (that is, 7 days) after shutdown	The instance is forcibly deleted. The system automatically selects the corresponding default backup policy based on the instance type, where: Primary-secondary instance: A final backup will be created by default before deleting the instance, and it will be retained for 7 days after successful creation. It is recommended to download and save it locally promptly. You can view or download backups of deleted instances on the Backups page and restore instances based on the backups. For more details, refer to Restoring deleted instance. Single node instance: Single node instances do not support persistence and backup functions. No backup will be created by default when deleting, and instance data will be completely cleared after deletion. Please proceed with caution. For more details about single-node instances, refer to Product architecture. tip When an instance is out of service due to its expiration, the instance is deleted even if deletion protection is enabled. For more details, refer to Instance deletion protection.