This topic describes the impacts of overdue payments that occur after ApsaraMQ for Kafka instances expire. To prevent business from being interrupted, we recommend you renew an instance before the instance expires.
Impacts of overdue payments
If the ApsaraMQ for Kafka instance that you purchased is a subscription instance, the instance enters the Expired state immediately after the instance expires. In this case, you can use the instance only after you renew it.
If the ApsaraMQ for Kafka instance that you purchased is a pay-as-you-go instance and the balance in your Alibaba Cloud account is insufficient to settle the outstanding payment, the instance expires when the grace period for overdue payments elapses. In this case, you can use the instance only after you add sufficient funds to your Alibaba Cloud account.
If you do not renew the ApsaraMQ for Kafka instance within 168 hours after the instance expires, the instance is released and data in the instance cannot be restored. If you want to release an ApsaraMQ for Kafka instance before the instance expires, you can forcibly delete the instance in the ApsaraMQ for Kafka console. For more information, see Manage the lifecycle of an instance.
To prevent business from being interrupted, we recommend that you renew an instance before the instance expires. For more information, see Instance renewal.
Notifications on imminent overdue payments and instance release
If an ApsaraMQ for Kafka instance is about to expire, Alibaba Cloud Message Center sends you a notification. For information about the notification mechanism, see Notification mechanism. For information about how to configure a notification policy for imminent overdue payments, see Set the notification policy for imminent overdue payments and instance release.
Table 1. Notification mechanism
Table 2. Notification mechanism
Billing method | Time when Message Center sends a notification on imminent overdue payments | Time when the instance is stopped | Time when Message Center sends a notification on imminent instance release | Time 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 |