An ApsaraMQ for Kafka instance enters the Expired state when its payment becomes overdue. An expired instance is unavailable. Renew subscription instances before they expire, or maintain enough balance for pay-as-you-go and serverless instances to avoid service interruption.
What triggers the Expired state
The trigger depends on your billing method:
Subscription instances
A subscription instance enters the Expired state immediately when it expires. The instance remains unavailable until you renew it.
Pay-as-you-go and serverless instances
A pay-as-you-go or serverless instance enters the Expired state when your Alibaba Cloud account balance is insufficient to settle the outstanding payment. The instance remains unavailable until you add enough funds to your account.
If your account balance is insufficient to pay the bill for your pay-as-you-go or Serverless instance, the status of your ApsaraMQ for Kafka service changes to Expired. You can no longer use the ApsaraMQ for Kafka service.
Expiry timeline
| Timeline | What happens |
|---|---|
| Immediately | The instance enters the Expired state and becomes unavailable. |
| Within 168 hours (7 days) | Renew the instance or add funds to restore service. |
| After 168 hours (7 days) | The instance, including all its topics and groups, is released and cannot be restored. |
If you do not renew within 168 hours after expiry, the instance and all associated resources are permanently released. This action is irreversible.
Restore an expired instance
Take action based on your billing method:
Subscription: Renew the instance. For details, see Instance renewal.
Pay-as-you-go or serverless: Add enough funds to your Alibaba Cloud account to settle the outstanding balance.
Release an instance before expiry
To release an ApsaraMQ for Kafka instance before it expires, forcibly delete the instance in the ApsaraMQ for Kafka console. For details, see Manage the lifecycle of an instance.