Answers to common questions about ApsaraDB RDS billing, cost control, instance expiration, and overdue payments.
Cost saving
Why am I charged extra fees on a subscription instance?
A subscription fee covers only the instance type and storage capacity you select at purchase. Additional charges are generated by:
-
Backup storage — storage that exceeds the free quota
-
Database proxy — the feature that enables automatic read/write splitting
-
Read-only instances and cloned instances — when billed on pay-as-you-go instead of subscription
-
SQL Audit — when the feature is enabled
-
Performance monitoring — when using frequencies shorter than 60 seconds
For the full list of billable items and pricing, see Billable items.
To reduce these costs:
-
Backup storage: Reduce backup frequency and keep backup size within the free quota.
-
Database proxy: Disable the feature if read/write splitting is not required. See What are database proxies?
-
Read-only and cloned instances: Switch these instances to subscription billing.
-
Performance monitoring: Use the 60-second or 300-second monitoring frequency, both of which are free.
How much does changing the specifications of a subscription instance cost?
How do I release an instance I no longer need?
How do I find when a feature was enabled?
Instance purchase and billing methods
I submitted a purchase order but the instance is not appearing in the Creating state. Why?
Two common causes:
-
Wrong region selected: The console may be showing a different region than where you placed the order. Select the correct region in the top navigation bar.

-
Insufficient resources in the zone: Resources are dynamically allocated. If the selected zone cannot fulfill the order, the instance fails to create. Select a different zone and try again. If the instance is not created, you receive a full refund. View the refund status on the Order page.
Instance expiration and overdue payments
What are the causes and impacts of instance expiration or overdue payments?
See Overdue payments and Renewal policy.
Are fees charged when an instance is locked due to overdue payments?
Can I restore data after it is deleted on day 16?
No. Data is permanently deleted on day 16 after expiration and cannot be recovered. To continue using the database, purchase a new instance and redeploy your data.
Which instances are affected by overdue payments?
I'm seeing the error "The MySQL server is running with the LOCK_WRITE option so it cannot execute this statement." What do I do?
I rebuilt an instance from the recycle bin. Is the data the same as before expiration?
Yes, the data is the same as when the instance was released. The endpoint and instance ID, however, are changed.


