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 as follows (each, a "Service Level Objective" or "SLO"):
Covered Service
Monthly Uptime Percentage
BigQuery
>= 99.99%
Additionally, BigQuery Data Transfer Service will include a Data Delivery Service Level
Objective as follows:
Covered Service
Data Delivery
BigQuery Data Transfer Service
Less than or equal to 24 hours
The Data Delivery SLO applies only to automatically scheduled runs.
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. Monthly Uptime
Percentage and Financial Credit are determined on a calendar month basis per Project. 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 meanings given to them
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 BigQuery or BigQuery Data Transfer Service.
"Data Delivery" means the time from when data is received by the BigQuery Data
Transfer Service to when data is delivered to Customer's BigQuery Project.
"Downtime" means more than a ten percent Error Rate. Downtime is measured
based on server side Error Rate.
"Downtime Period" means a period of one or more consecutive minutes of
Downtime. Partial minutes will not be counted towards any Downtime Periods.
"Error Rate" means the number of Valid Requests that result in a response with
an HTTP Status in the 500 range divided by the total number of Valid Requests
during that period, subject to a minimum of 20 Valid Requests in the measurement period. Repeated
identical requests do not count towards the Error Rate unless they conform to the Back-off
Requirements.
"Financial Credit" means the following for the Covered Service (except
as otherwise stated below):
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.0% – < 99.99%
10%
95.0% – < 99.0%
25%
< 95.0%
50%
Data Delivery
Amount in charges that will be credited to future monthly bills of Customer
Greater than 24 hours
Charges incurred for each impacted BigQuery Data Transfer Service configuration on the day on which the late data transfer began.
"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 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 30 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 pre-general availability
(unless otherwise stated 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 listed in
the Documentation or Admin Console.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["\u003cp\u003eBigQuery guarantees a Monthly Uptime Percentage of ≥ 99.99%.\u003c/p\u003e\n"],["\u003cp\u003eBigQuery Data Transfer Service aims for Data Delivery within ≤ 24 hours for automatically scheduled runs.\u003c/p\u003e\n"],["\u003cp\u003eIf service levels are not met, customers may be eligible for Financial Credits, calculated based on the Monthly Uptime Percentage and/or Data Delivery times.\u003c/p\u003e\n"],["\u003cp\u003eTo receive Financial Credits, customers must notify Google technical support within 30 days of becoming eligible, with a maximum credit cap of 50% of the monthly charges.\u003c/p\u003e\n"],["\u003cp\u003eThe SLA excludes errors outside of Google's control, those caused by the customer, or those from pre-general availability features and services.\u003c/p\u003e\n"]]],[],null,["# BigQuery Service Level Agreement (SLA)\n\nLast modified: July 01, 2021 \\| [Previous Versions](#previous_versions)\n\n\nDuring 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 as follows (each, a \"Service Level Objective \" or \"SLO\"):\n\nAdditionally, BigQuery Data Transfer Service will include a Data Delivery Service Level\nObjective as follows:\n\n\u003cbr /\u003e\n\nThe Data Delivery SLO applies only to automatically scheduled runs.\n\n\nIf Google does not meet the SLO, and if Customer meets its obligations under this SLA,\nCustomer will be eligible to receive the Financial Credits described below. Monthly Uptime\nPercentage and Financial Credit are determined on a calendar month basis per Project. This SLA\nstates Customer's sole and exclusive remedy for any failure by Google to meet the SLO.\nCapitalized terms used in this SLA, but not defined in this SLA, have the meanings given to them\nin the Agreement. If the Agreement authorizes the resale or supply of Google Cloud Platform under\na Google Cloud partner or reseller program, then all references to Customer in this SLA mean\nPartner or Reseller (as applicable), and any Financial Credit(s) will only apply for impacted\nPartner or Reseller order(s) under the Agreement.\n\n#### Definitions\n\nThe following definitions apply to the SLA:\n\n- **\"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.\n- **\"Covered Service\"** means BigQuery or BigQuery Data Transfer Service.\n- **\"Data Delivery\"** means the time from when data is received by the BigQuery Data Transfer Service to when data is delivered to Customer's BigQuery Project.\n- **\"Downtime\"** means more than a ten percent Error Rate. Downtime is measured based on server side Error Rate.\n- **\"Downtime Period\"** means a period of one or more consecutive minutes of Downtime. Partial minutes will not be counted towards any Downtime Periods.\n- **\"Error Rate\"** means the number of Valid Requests that result in a response with an HTTP Status in the 500 range divided by the total number of Valid Requests during that period, subject to a minimum of 20 Valid Requests in the measurement period. Repeated identical requests do not count towards the Error Rate unless they conform to the Back-off Requirements.\n- **\"Financial Credit\"** means the following for the Covered Service (except as otherwise stated below): \n\n \u003cbr /\u003e\n\n- **\"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.\n- **\"Valid Requests\"** are requests that conform to the Documentation, and that would normally result in a non-error response.\n\n#### Customer Must Request Financial Credit\n\nIn order to receive any of the Financial Credits described above, Customer must\n[notify Google\ntechnical support](https://support.google.com/cloud/contact/cloud_platform_sla) within 30 days from the time Customer becomes eligible\nto receive a Financial Credit. Failure to comply with this requirement will forfeit\nCustomer's right to receive a Financial Credit.\n\n#### Maximum Financial Credit\n\nThe aggregate maximum number of Financial Credits to be issued by Google to Customer for\nany and all Downtime Periods that occur in a single billing month will not exceed 50%\nof the amount due by Customer for the applicable Covered Service for the applicable month.\nFinancial Credits will be made in the form of a monetary credit applied to future use of\nthe Service and will be applied within 60 days after the Financial Credit was requested.\n\n#### SLA Exclusions\n\nThe SLA does not apply to any (a) features or Services designated pre-general availability\n(unless otherwise stated in the associated Documentation); (b) features or Services\nexcluded from the SLA (in the associated Documentation); or (c) errors (i) caused by factors\noutside of Google's reasonable control; (ii) that resulted from Customer's software or\nhardware or third party software or hardware, or both; (iii) that resulted from abuses or\nother behaviors that violate the Agreement; or (iv) that resulted from quotas listed in\nthe Documentation or Admin Console.\n\n**Previous Versions**\n\n- [June 25, 2020](/bigquery/sla-20200625)\n- [September 17, 2019](/bigquery/sla-20190917)\n- [November 16, 2017](/bigquery/sla-20171116)\n- [October 19, 2016](/bigquery/sla-20161019)\n- [July 21, 2016](/bigquery/sla-20160721)"]]