Note:
This Agreement shall take effect on July 21, 2026.
In order to use the Tencent Cloud Distributed Database TDSQL Boundless service (hereinafter referred to as "this Service"), you shall read and comply with the TDSQL Boundless Service Level Agreement (hereinafter referred to as "this Agreement" or "SLA"), as well as the Tencent Cloud Service Agreement. This Agreement contains the terms and definitions of this Service, service availability/success rate metrics, compensation plans, disclaimer clauses, and other related content. To use this Service, you must carefully read and fully understand all terms. Key terms, such as limitations, disclaimers, or other clauses concerning your significant rights and interests, are highlighted in bold and/or underlined to call your special attention. If you have any questions about this Agreement, you may consult Tencent Cloud by submitting a ticket.
Do not purchase or use this Service unless you have fully read, understood, and accepted all terms of this Agreement. By checking the box, clicking to confirm/agree, purchasing, using this Service in any manner, or otherwise indicating your acceptance of this Agreement explicitly or implicitly, you are deemed to have read, understood, and agreed to be bound by this Agreement. This Agreement thereby becomes legally effective between you and Tencent Cloud, constituting a legally binding document for both parties.
1. TERMS AND DEFINITIONS
The TDSQL Boundless distributed database service provided by Tencent Cloud refers to a high-performance, enterprise-grade database service that is highly compatible with MySQL, built by Tencent Cloud based on its self-developed database engine to meet the diverse needs of your various websites, applications, and other scenarios. This Agreement applies only to TDSQL Boundless Cluster Edition, Basic Edition instances, and the read-only analysis engine. The specific scope is subject to the service you purchase and the service content provided by Tencent Cloud.
1.2 Service Unavailability
If, within any given minute, all your consecutive attempts to establish a connection to or perform read/write operations on a specified TDSQL Boundless instance fail, and this state persists for more than one minute, the service of that TDSQL Boundless instance is considered unavailable for that minute.
1.3 Single Instance Service Unavailability Minutes
Single-instance unavailable minutes = Instance unavailability resolution time - Instance unavailability start time. Unavailability time is calculated in minutes. For any unavailability duration exceeding a full minute, any remaining fractional minute is counted as one full minute. For example, if the unavailability duration is 1 minute and 1 second, it is counted as 2 minutes. If the service fault recovery time is less than 1 minute (that is, the instance is unavailable for less than 1 minute), the unavailability minutes are not counted.
1.4 Single Instance Monthly Service Unavailability Minutes
The individual unavailability time periods within a Service Month are summed to obtain the total unavailability minutes for that Service Month.
1.5 Total Service Minutes per Instance in a Service Month
It is calculated based on the number of days in the Service Month * 24 (hours) * 60 (minutes).
1.6 Monthly Service Fee
The total service fees you pay for a single TDSQL Boundless instance within a Service Month do not include any portion that has been purchased but not yet consumed. If you pay for multiple months of service in a single payment, the monthly service fee will be calculated by prorating the total payment over the number of months purchased.
1.7 Service Month
A Service Month refers to each calendar month within the service period for which you have purchased this Service. For example, if you purchase the Service for three months and the Service activation date is March 17, it includes 4 Service Months, of which the first Service Month refers to March 17 to March 31, the second Service Month refers to April 1 to April 30, the third Service Month refers to May 1 to May 31, and the fourth Service Month refers to June 1 to June 16. Service availability is calculated separately on a monthly basis.
2. Service Availability/Service Success Rate
2.1 Service Availability / Service Success Rate Calculation
Service availability is calculated on a per-instance basis as follows: Service availability = (1 - Monthly unavailable minutes of single-instance service / Total monthly service minutes of single-instance service) * 100%.
2.2 Service Availability/Service Metrics Standard
The Service Availability provided by Tencent Cloud is as follows:
For instances deployed in a multi-AZ architecture running Cluster Edition, the Service Availability provided by this Service is not less than 99.99%.
For instances deployed in a single-AZ architecture running Cluster Edition and for the read-only analysis engine, the Service Availability provided by this Service is not less than 99.95%.
For Basic Edition instances, the Service Availability provided by this Service is not less than 99%.
If the above Service Availability standards are not met (except for circumstances covered by the exemption clauses), you may claim compensation in accordance with the provisions of Article 3 of this Agreement.
3. Compensation Plan
For this Service, if the Service Availability falls below the standard, you are entitled to claim compensation in accordance with the following terms:
3.1 Compensation Standard
(1) Compensation is provided by Tencent Cloud in the form of issuing vouchers. This compensation constitutes the full and sole remedy provided to you for Service Availability falling below the standard. You must comply with the voucher usage rules (including the validity period, and so on, subject to the voucher-related rules published on the Tencent Cloud official website). The issued vouchers cannot be cashed out, and no invoice will be issued for them. They can only be used by you through your Tencent Cloud account when this Service is purchased and cannot be used to purchase other Tencent Cloud services. You may not transfer, gift, or otherwise assign the vouchers.
(2) If the Service Availability for a Service Month fails to meet the TDSQL Boundless service availability standard, the compensation amount is calculated separately for that non-compliant Service Month. The total compensation amount does not exceed the total monthly service fee you paid for this Service during that non-compliant Service Month.
For instances running Cluster Edition and deployed in a multi-AZ architecture, the compensation plan for this Service is as follows:
|
Below 99.99% but equal to or above 99% | 15% of the monthly service fee |
Below 99% but equal to or above 95% | 30% of the monthly service fee |
Below 95% | 100% of the monthly service fee |
For instances deployed in a single-AZ architecture with Cluster Edition, and for the read-only analysis engine, the compensation plan for this Service is as follows:
|
Below 99.95% but equal to or above 99% | 15% of the monthly service fee |
Below 99% but equal to or above 95% | 30% of the monthly service fee |
Below 95% | 100% of the monthly service fee |
For Basic Edition instances, the compensation plan for this Service is as follows:
|
Below 99% but equal to or above 95% | 15% of the monthly service fee |
Below 95% but equal to or above 90% | 30% of the monthly service fee |
Below 90% | 100% of the monthly service fee |
3.2 Compensation Claim Time Limit
(1) If the TDSQL Boundless service availability standard is not met in a Service Month, you may submit a compensation claim only through the ticket system of the account you used for this Service and for which the availability standard was not met, after the fifth (5th) business day of the month following the end of the non-compliant Service Month. After you submit the compensation claim, Tencent Cloud will conduct a corresponding verification and reasonably assess whether to provide compensation to you in accordance with this Agreement. Regarding the calculation of Service Availability for a Service Month, if any dispute arises between the parties, both parties agree that Tencent Cloud's backend logs shall prevail as the final authority.
(2) The deadline for you to submit a compensation claim must not exceed sixty (60) calendar days after the end of the non-compliant Service Month. If you do not submit a compensation claim within sixty (60) days after the end of the non-compliant Service Month, or if you submit a compensation claim after sixty (60) days have passed since the end of the non-compliant Service Month, or if you submit a claim in a manner not stipulated in this Agreement, it will be deemed that you have automatically waived your right to claim compensation and your right to assert any other rights against Tencent Cloud. Tencent Cloud has the right to reject your compensation claim and will not provide you with any compensation or remedy.
3.3 Compensation Claim Materials
If you believe that this Service fails to meet the Service Availability standard, you can submit a compensation claim within the timeframe stipulated in this Service Level Agreement. Your compensation claim must be submitted along with at least the following information:
(1) The instance ID for which the service was unavailable.
(2) The duration of service unavailability and other relevant evidence.
4. Exceptions to SLA Applicability
If you use this Service through public beta, private beta, invitation test, or free of charge or within the free quota, although Tencent Cloud will provide the Service according to the functions described in the Service documentation, Tencent Cloud makes no warranties or representations regarding Service availability and Service success rate, and the Service availability standards and compensation standards of this SLA do not apply to the abovementioned scenarios.
5. Disclaimers
For service unavailability caused by the following reasons, the corresponding service unavailability duration is not included in the calculation of service unavailability or in Tencent Cloud's compensation scope. Tencent Cloud is not liable to you for such unavailability:
5.1 Service unavailability caused by network, device, system, or communication line failures, or configuration adjustments, involving equipment or facilities not belonging to Tencent Cloud.
5.2 Service unavailability caused by your application being attacked by hackers.
5.3 Service unavailability caused by the loss or leakage of data, passwords, credentials, or similar items due to your improper maintenance or inadequate security measures.
5.4 Service unavailability caused by your negligence or actions authorized by the customer.
5.5 Service unavailability caused by your failure to comply with the Tencent Cloud Agreement, this Service's usage documentation, or usage recommendations.
5.6 Service unavailability or failure to meet service standards caused by software you have installed, or by third-party software or configurations not directly operated by Tencent Cloud.
5.7 Service unavailability caused by force majeure. Force majeure refers to circumstances that the parties to the agreement cannot foresee, and whose occurrence and consequences are insurmountable and unavoidable. This includes, but is not limited to: natural disasters such as floods, hail, tsunamis, typhoons, droughts, and fires; government actions such as policies, laws, regulations, and new measures enacted, adjusted, or changed by government authorities that prevent the agreement from being performed; abnormal social events such as riots, epidemics, wars, and strikes (excluding internal labor disputes of the parties); and other events that cannot be foreseen, overcome, or avoided and have a significant impact on one or more parties.
5.8 Service unavailability caused by service anomalies resulting from the following circumstances:
(1) Changes to basic telecommunications resources. This includes, but is not limited to, technical adjustments by telecommunications departments, installation, modification, or maintenance of telecommunications networks/power resources by telecommunications/power departments, and damage to telecommunications/power lines.
(2) Control actions by government regulatory authorities or operators.
(3) Blockage of public networks, degradation of operational efficiency, or hacker activities.
(4) Other circumstances not attributable to Tencent Cloud's fault, which Tencent Cloud cannot control or reasonably foresee.
5.9 Service suspension or termination resulting from your failure to purchase or pay for the service as agreed.
5.11 Temporary service interruption or suspension caused by Tencent Cloud performing "routine maintenance" on the distributed database TDSQL Boundless service, as described in the Tencent Cloud Service Agreement. 5.12 Service unavailability or failure to meet service standards not attributable to Tencent Cloud.
5.13 This clause covers circumstances where Tencent Cloud is exempt from or relieved of liability, as described in relevant laws and regulations, relevant agreements (including the Tencent Cloud Service Agreement and other agreements referenced herein), relevant rules (including descriptions of service content, pricing, and other service matters on the official website pages, as well as page terms, usage documentation, and other rules you have confirmed and agreed to when purchasing and using this Service), or relevant rules and statements separately issued by Tencent Cloud that are applicable to this Service. 5.14 You shall promptly respond to emergency service upgrade or version upgrade notifications issued for this Service. If you fail to perform the upgrade within six months after being notified due to your own inaction, you are solely responsible for any resulting losses and consequences, such as business interruption or data loss.
6. Miscellaneous
6.1 Both parties hereby acknowledge and agree that: Under any circumstances, if you incur losses due to Tencent Cloud's breach of contract while using this Service, the total amount of Tencent Cloud's liability for breach of contract shall not exceed the total service fees you have paid for the corresponding non-compliant service. If you have used this Service for more than 12 months, the total amount of Tencent Cloud's liability for breach of contract shall not exceed the total service fees you have paid for the service in the 12 months preceding the occurrence of the damage.
6.2 Based on the timeliness, complexity, and efficiency of network services, as well as the need to comply with regulatory requirements and policies, you agree that Tencent Cloud may modify the terms of this Agreement, and you may review the relevant terms on the latest version of the Tencent Cloud official website. If you do not agree with the modifications made by Tencent Cloud to this Agreement, you have the right to stop using this Service. If you continue to use this Service, it indicates that you have fully read, understood, and accepted the modified content, and you will comply with the revised content.
6.3 The descriptions of service content, pricing, and other service matters for this Service on the relevant Tencent Cloud official website pages, as well as the page terms, usage documentation, and other materials you have confirmed and agreed to when purchasing and using this Service, constitute an integral part of this Agreement. As a supplementary agreement to the Tencent Cloud Service Agreement, this Agreement has the same legal effect as the Tencent Cloud Service Agreement. For matters not stipulated in this Agreement, you must comply with the relevant provisions of the Tencent Cloud Service Agreement. In the event of any conflict or inconsistency between the terms of this Agreement and those of the Tencent Cloud Service Agreement, the terms of this Agreement shall prevail, but only to the extent of such conflict or inconsistency. (End)