• Back to Google Cloud Terms Directory
• Current

Cloud SQL Service Level Agreement (SLA)

Last modified: October 14, 2019

This is not the current version of this document and is provided for archival purposes. View the current version

During the Term of the agreement under which Google has agreed to provide Google Cloud Platform to Customer (as applicable, the "Agreement"), the Covered Service will provide a Monthly Uptime Percentage to Customer of at least 99.95% (the "Service Level Objective" or "SLO").

If Google does not meet the SLO, and if Customer meets its obligations under this SLA, Customer will be eligible to receive the Financial Credits described below. This SLA states Customer's sole and exclusive remedy for any failure by Google to meet the SLO. Capitalized terms used in this SLA, but not defined in this SLA, have the meaning set forth in the Agreement. If the Agreement authorizes the resale or supply of Google Cloud Platform under a Google Cloud partner or reseller program, then all references to Customer in this SLA mean Partner or Reseller (as applicable), and any Financial Credit(s) will only apply for impacted Partner or Reseller order(s) under the Agreement.

Definitions

The following definitions apply to the SLA.

• "Covered Service" means Cloud SQL First Generation, Cloud SQL Second Generation for MySQL, Cloud SQL for SQL Server, and Cloud SQL for PostgreSQL.
• "Dedicated CPU Core Instances" have the minimum power of one virtual CPU from Google Compute Engine. A virtual CPU is implemented as a single hardware hyper-thread on a Compute Engine VM instance.
• "Downtime" means (i) with respect to Cloud SQL First Generation: more than a twenty percent Error Rate; Downtime is measured based on server side Error Rate; or (ii) with respect to Cloud SQL Second Generation for MySQL, Cloud SQL for SQL Server, and Cloud SQL for PostgreSQL: all connection requests to a Multi-zone Instance fail.
• "Downtime Period" means (i) with respect to Cloud SQL First Generation: a period of one consecutive minute of Downtime in which at least five connection attempts are made with no concurrently open connections; or (ii) with respect to Cloud SQL Second Generation for MySQL, Cloud SQL for SQL Server, and Cloud SQL for PostgreSQL: one consecutive minute of Downtime. Intermittent Downtime for a period of less than one minute will not be counted towards any Downtime Periods. Downtime as part of Scheduled Maintenance will not be counted towards any Downtime Period.
• "Error Rate" means the number of Valid Requests to open a connection that fail to open a connection, divided by the total number of Valid Requests during that period.
• "Financial Credit" means the following for the Covered Services (except as otherwise set forth below):

Monthly Uptime Percentage	Percentage of monthly bill for Covered Service which does not meet SLO that will be credited to future monthly bills of Customer
99.0% - < 99.95%	10%
95.0% - < 99.0%	25%
< 95.0%	50%

• "Monthly Uptime Percentage" means the total number of minutes in a month, minus the number of minutes of Downtime suffered from all Downtime Periods in a month, divided by the total number of minutes in a month.
• "Multi-zone Instance" means a Cloud SQL Second Generation for MySQL, Cloud SQL for SQL Server, and Cloud SQL for PostgreSQL Dedicated CPU Core Instance with a failover replica attached.
• "Scheduled Maintenance" is Downtime Period related to network, hardware, or software maintenance or upgrades. With respect to Cloud SQL First Generation: we will perform scheduled maintenance at our discretion. With respect to Cloud SQL Second Generation for MySQL, Cloud SQL for SQL Server, and Cloud SQL for PostgreSQL: we will perform scheduled maintenance only during a user-configurable maintenance window unless a user elects not to configure a maintenance window.
• "Valid Requests" are requests that conform to the Documentation, and that would normally result in a non-error response.

Customer Must Request Financial Credit

In order to receive any of the Financial Credits described above, Customer must notify Google technical support within thirty days from the time Customer becomes eligible to receive a Financial Credit. Failure to comply with this requirement will forfeit Customer’s right to receive a Financial Credit.

Maximum Financial Credit

The aggregate maximum number of Financial Credits to be issued by Google to Customer for any and all Downtime Periods that occur in a single billing month will not exceed 50% of the amount due by Customer for the applicable Covered Service for the applicable month. Financial Credits will be made in the form of a monetary credit applied to future use of the Service and will be applied within 60 days after the Financial Credit was requested.

SLA Exclusions

The SLA does not apply to any: (a) features or Services designated Alpha or Beta (unless otherwise set forth in the associated Documentation), (b) features or Services excluded from the SLA (in the associated Documentation), (c) features or Services that have been deprecated; or (d) errors: (i) caused by factors outside of Google’s reasonable control; (ii) that resulted from Customer’s software or hardware or third party software or hardware, or both; (iii) that resulted from abuses or other behaviors that violate the Agreement; (iv) that resulted from quotas listed in the Documentation; or (v) that resulted from Customer’s restart of an Instance.