Docs

Load Balancer

Billing

Arrears description

When your account balance falls below zero, the account enters an overdue state. You can refer to the Account overview to view overdue details. Once an account becomes overdue, it may lead to the shutdown and eventual reclamation of Application Load Balancer (ALB) instances, affecting their operation and configuration management.

Overdue Impact

After an account becomes overdue, the impacts and operational restrictions on ALB resources over different periods are outlined in the table below.

Arrears Duration	Within 2 hours	Between 2 Hours and (2 Hours + 15 Days)	After (2 hours + 15 days)
Instance state	The instance is functioning properly. If you recharge your account and settle all overdue payments. Your services will remain unaffected.	The system shuts down the instance but retains the instance resource for a limited period. Service Status: ALB service stops. If you recharge your account and settle all overdue payments during this period, services can resume normal operations, and billing will restart.	The system reclaims the instance and the EIP(s) associated with public ALB instances. The system permanently deletes all instance-related data and configurations, which cannot be recovered.
Billing	normal billing	Billing stops	Billing stops
Limitations	Creating new instances and modifying public network configurations are not supported.	The following operations are not supported: Instance-related operations: Including creating instances, binding EIPs, and modifying public network configurations. Listener-related operations: Including adding listeners and modifying listener information. Server group operations (for groups already associated with an instance): Including deleting server groups and editing server groups. Editing encompasses adding/removing backend servers, modifying server weights, and adjusting health check settings. Monitoring-related operations: Configured monitoring and alerting services are suspended. Only data recorded up until the moment of instance shutdown is retained. Log-related operations: Including access logs and health check logs. Configured access log and health check log services are suspended. Only data recorded up until the moment of instance shutdown is retained. Custom configuration operations (for configurations already associated with an instance): Including deleting custom configurations and modifying configuration parameters. tip Health check log information can be viewed, and log topics can be unbound within the first 24 hours of overdue status. After 24 hours, health check log information becomes unavailable for viewing.	The following operations are supported: Operations on server groups NOT associated with any instance: Including creating, deleting, and editing server groups. Editing encompasses adding/removing backend servers, modifying server weights, and adjusting health check settings. Certificate operations: Including uploading, querying, and deleting certificates. Access Control List operations: Including creating, querying, modifying, deleting policy groups, and adding/removing IP entries to/from them. Health Check Template operations: Including creating, querying, deleting health check templates, and modifying their parameters.

Last updated: 2026.06.17 14:18:55