Tencent Cloud Notices > Notice Details
[TencentDB for MySQL] Announcement on Billing for Exceeding Storage Space
2026-07-17 15:43:06
Dear Tencent Cloud user,
Thank you for your long-standing trust and support of Tencent Cloud. To ensure the stability of TencentDB for MySQL services, prevent resource security risks caused by prolonged over-utilization of storage space on local disk instances, and maintain fairness in resource usage, Tencent Cloud will begin charging for excess storage usage on TencentDB for MySQL local disk instances, effective 00:00:00 (Beijing Time) on August 1, 2026. Excess storage usage incurred prior to this effective date will not be retroactively charged.
This billing policy applies to the portion of total storage space used that exceeds the purchased storage capacity on TencentDB for MySQL local disk instances. You can view your purchased storage capacity, current total storage usage, and any excess usage via the TencentDB for MySQL Console. We recommend that you proactively scale up your storage capacity or clean up redundant data before the effective date to avoid incurring additional costs.
For instances that incur new excess usage after the effective date, a disk pre-lock event will be triggered according to product rules. During the pre-lock phase, the instance remains readable and writable; if the excess usage persists for 24 hours without capacity expansion or data cleanup, a lock event will be triggered, restricting the instance to read-only operations.
For existing local disk instances already exceeding their purchased capacity prior to the effective date, Tencent Cloud will continue to allow read-write operations. However, starting from 00:00:00 (Beijing Time) on August 1, 2026, any storage usage exceeding the purchased capacity will be billed according to the rules. Please note that if such existing over-utilized instances reach the host storage risk threshold, a disk pre-lock event will also be triggered; if the issue remains unresolved 24 hours after pre-locking, a lock event will be triggered, restricting the instance to read-only operations.
Once an instance enters a pre-locked or locked state, you can mitigate the risk by scaling up storage capacity or cleaning up redundant data; specific methods for resolution, recovery timelines, and notification procedures are subject to console prompts and official product documentation.
Excess storage fees are calculated based on the difference between the total storage space used and the purchased storage capacity. For details regarding billing objects, formulas, unit prices for excess usage, billing cycles, and final charges, please refer to the Billing Instructions for Excess Storage Usage. All final charges are subject to the information displayed in the console and your bills in the Billing Center.
