Tencent Cloud Notices > Notice Details
[TencentDB for MySQL] Announcement on Service Level Agreement Updates
2026-08-14 10:05:55
Dear Tencent Cloud user,
The Service Level Agreement (SLA) for TencentDB for MySQL was updated on August 14, 2026. Please see the details below.
Effective Date
August 14, 2026 (Friday), Beijing Time.
Update Details
In Definitions, Section 1.6: "Monthly Service Fee" has been updated:
Previous | Updated |
The total amount of Service fees that you pay for a single TencentDB for MySQL instance in a service month, excluding the portion that has been purchased but not consumed. If you pay for more than one month at once, the monthly Service fee will be amortized based on the number of months purchased. | Monthly Service Fee refers to the total service fees you actually pay for a single instance within a service month, excluding vouchers, credits, discount deductions, complimentary allowances, and any prepaid but unconsumed portions. If you pay for multiple months of service fees in one lump sum, the Monthly Service Fee is calculated by prorating the total payment based on the number of months purchased. |
In Limitation of Liability, Section 5.11 has been updated:
Previous | Updated |
temporary interruption or suspension of the Service due to the "routine maintenance" described in the service documentation for TencentDB for MySQL. | Service unavailability time does not include brief service interruptions or suspensions caused by Tencent Cloud performing "routine maintenance" (including but not limited to system maintenance, version upgrades, hardware replacement, data center migration, disaster recovery switchover drills, and simulated failure drills) as defined in the Tencent Cloud Terms of Service on TencentDB for MySQL, provided that advance notice is given or the maintenance is performed within the agreed maintenance window. |
In Limitation of Liability, Sections 5.15, 5.16, and 5.17 have been added:
5.15 To ensure data security, you are responsible for backing up your data. Tencent Cloud products or services may provide you with tools that feature daily data backup. However, backups may fail due to factors such as DDL operation conflicts during backup, insufficient disk space, lock acquisition failures caused by large transactions without primary keys, encryption keys being disabled/deleted, and improper unique_checks parameter settings. As these factors involve customer business operations, Tencent Cloud cannot address them without authorization and therefore cannot guarantee successful backups under all circumstances. Since the backup tools are currently provided free of charge, Tencent Cloud also cannot assume responsibility for the process or outcome of user data backups.
5.16 Tencent Cloud does not consider service unavailability or assume liability for compensation in cases where backup or rollback failures, backup data loss, or unavailability are caused by the following user-side reasons, including but not limited to:
(1) Executing blocking operations such as DDL statements or large transactions during the backup window, which causes lock conflicts or timeouts for the backup process;
(2) Insufficient disk space or the instance being in a read-only/locked state, which prevents full or incremental backups from being written;
(3) Non-standard table structures (such as tables without primary keys) combined with long-running/large transactions, which cause the backup process to fail to obtain a consistent lock point within the agreed time window;
(4) After a user enables backup encryption, if the bound KMS key is disabled, deleted, expired, or has its permissions revoked, which causes backup encryption or decryption to fail;
(5) Other backup anomalies caused by user-controllable factors such as business operations, resource planning, table design, or key management;
5.17 Service unavailability time does not include performance degradation or brief unavailability caused by the instance's own load reaching resource bottlenecks, such as slow response, hang, connection exhaustion, resource overutilization (CPU, memory, IOPS, disk, bandwidth), primary-replica replication latency or interruption, or performance issues during large transactions/DDL operations/log replay.
For the new TencentDB for MySQL Service Level Agreement, see TencentDB for MySQL Service Level Agreement.
