Relational Database Service (MySQL)

Expiration and Arrears

2024-06-19 02:42:55

Service expiration and arrears may affect the use of your instance.

Service Expiration

• For Payment by Volume instances, you do not need to worry about the expiration of the service.

• After expiration, the Annual/Monthly Package instance will be suspended, and related operations cannot be performed on the instance in the Database Console during this period. In addition, related interfaces cannot be called, and monitoring or alarms are also stopped. Failure to renew during the suspension period will result in the termination of service for that instance, leading to permanent deletion of the data stored within the system. To avoid data loss, we strongly recommend that you renew your subscription in time during the suspension period, or back up your data in advance and save it properly separately.

• For instances suspended upon expiration, you can access the Recycle Bin within seven days. Then, you can renew the relevant instances to resume service usage.

Arrears

• For Payment by Volume instances, you do not need to worry about the arrears of the service.

• The Payment by Volume instance is charged on an hourly basis. If the balance is insufficient to cover the charge for the previous hour, the instance will be in arrears and its service will be suspended. You can renew the suspended instance and continue using it as usual. Please note that the renewal during the suspension period is based on the original expiration time. You will need to pay the service fee from the beginning of the suspension period until the time of renewal.

• For instances suspended upon expiration, you can access the Recycle Bin within seven days after recharging. Then, you can renew the relevant instances to resume service usage.


edvjsx2xnI3a