This topic describes the impact of overdue payments when you are billed for a ApsaraMQ for Kafka instance based on the pay-as-you-go billing method. We recommend that you add enough funds to your account to prevent service interruption.
Impact of overdue payments
When your account balance is insufficient to pay for the bill and your ApsaraMQ for Kafka service has been in arrears for more than 96 hours, your instance is stopped and you cannot use the ApsaraMQ for Kafka service any longer.
If the service is still in arrears 168 hours after the ApsaraMQ for Kafka instance is stopped, the instance is released and cannot be recovered. This means that you can no longer use the ApsaraMQ for Kafka instance.
To prevent service interruption, we recommend that you complete overdue payments within 96 hours after the service is in arrears.
Notifications on imminent overdue payments and instance release
If an instance is about to be in arrears, the system sends you a notification. You can view such notifications in Message Center. For more information about when the system sends a notification, see Notification rules. For more information about how to set the notification policy, see Set the notification policy for imminent overdue payments and instance release.
Table 1. Notification rules
Billing method | When the system sends a notification on an imminent overdue payment | When the instance is stopped | When the system sends a notification on imminent instance release | When the instance is released |
Pay-as-you-go | 12 hours after payments are overdue | 96 hours after payments are overdue | 144 hours before the instance is released | 168 hours after the instance is stopped |
23 hours after payments are overdue |