Shape the future of software delivery and make your voice heard by taking the 2021 State of DevOps survey.

Cloud Build Service Level Agreement (SLA)

Last modified: December 15, 2020

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:

  • "Back-off Requirements" means, when an error occurs, the Customer Application is responsible for waiting for a period of time before issuing another request. This means that after the first error, there is a minimum back-off interval of 1 second and for each consecutive error, the back-off interval increases exponentially up to 32 seconds.
  • "Covered Service" means Cloud Build operations for a specific project.
  • "Downtime" means more than a ten percent Error Rate.
  • "Downtime Period" means a period of five or more consecutive minutes of Downtime. Partial minutes or intermittent Downtime for a period of less than five minutes will not be counted towards any Downtime Periods.
  • "Error Rate" means the number of Valid Requests that fail due to internal failure (500 error) or service unavailable (503 error) divided by the total number of Valid Requests during that period. Repeated identical requests do not count towards the Error Rate unless they conform to the Back-off Requirements.
  • "Financial Credit" means the following:

    Monthly Uptime Percentage Percentage of monthly bill for the respective Covered Service that does not meet SLO that will be credited to future monthly bills of Customer
    99.00% - < 99.95% 10%
    95.0% - < 99.0% 25%
    < 95.0% 50%
  • "Monthly Uptime Percentage" means 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.

  • "Valid Requests" are build invocation requests for the applicable Covered Service either directly to the Cloud Build API or via a supported event trigger source 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 30 days from the time Customer becomes eligible to receive a Financial Credit. If Customer does not comply with these requirements, Customer will forfeit its right to receive a Financial Credit.

Maximum Financial Credit

The maximum aggregate number of Financial Credits issued by Google to Customer for all Downtime Periods in a single billing month will not exceed 50% of the amount due from Customer for the Covered Service for the applicable month. Financial Credits will be 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 pre-general availability (unless otherwise set forth in the associated Documentation); (b) features or services excluded from the SLA (in the associated Documentation); or (c) 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; or (iv) that resulted from quotas applied by the system or listed in the Admin Console.