This topic describes the impacts on your business when your ApsaraMQ for Kafka instance expires or when an overdue payment occurs. We recommend that you renew an instance before it expires to avoid service interruption.
Impacts of overdue payments
If the ApsaraMQ for Kafka instance that you purchased is billed to your account based on the subscription billing method, the ApsaraMQ for Kafka instance is stopped immediately when it expires. You cannot use the instance until you renew it.
If the instance that you purchased is billed to your account based on the pay-as-you-go billing method, the ApsaraMQ for Kafka instance is set to the Overdue Payments state when your account balance is insufficient. When the grace period ends, the instance is stopped. You cannot use the ApsaraMQ for Kafka instance until you add sufficient funds to your account.
If an overdue payment still occurs on your account within 168 hours after your ApsaraMQ for Kafka instance is stopped, the instance is released and the data cannot be recovered. In this case, you can no longer renew and use the ApsaraMQ for Kafka instance. If you want to release an instance before it expires, you can forcibly delete it in the console. For more information, see Manage the lifecycle of an instance.
We recommend that you renew your instance before it expires to ensure service availability. For more information, see Instance renewal.
Notifications on overdue payments and instance release
If an instance is about to expire or an overdue payment occurs on your Alibaba Cloud account, the system sends you a notification. You can view these notifications in Message Center. For more information, see Notification mechanism. For more information about how to configure a notification policy, see Set the notification policy for imminent overdue payments and instance release.
Billing method | When the system sends a notification | When the instance is stopped | When the system sends a notification | When the instance is released |
Subscription | 24 hours before the instance expires | Immediately after the instance expires | 24 hours before the instance is released | 168 hours after the instance is stopped |
72 hours before the instance expires | ||||
168 hours before the instance expires | ||||
Pay-as-you-go | 12 hours after an overdue payment occurs | 96 hours after an overdue payment occurs | 144 hours before the instance is released | 168 hours after the instance is stopped |
23 hours after an overdue payment occurs |