Secure Source Manager Service Level Agreement (SLA)

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 per Region. 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, Customer 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:
• API Requests: Handling of API requests to the Secure Source Manager service via the global endpoint (securesourcemanager.googleapis.com) or regional endpoints (securesourcemanager.[location].rep.googleapis.com), but excludes requests directed to data plane or instance-specific endpoints.
• Git Requests: Processing of standard Git protocol read and write operations.
• Event Notifications: The successful emission of the event from Secure Source Manager of standard webhooks, Cloud Build triggers, and Developer Connect integration events to their configured target endpoints, but excludes delivery to, and processing by, any receiving service or endpoint.
• "Downtime" means more than a 5% Error Rate and is measured based on server side Error Rate.
• "Downtime Period" means a period of 5 or more consecutive minutes of Downtime. Partial minutes or intermittent Downtime for a period of less than 5 minutes will not count towards any Downtime Periods.
• "Error Rate" means:
• For API Requests and Git Requests: The number of Valid Requests that result in a response with HTTP Status 500 or Code "Internal Error", divided by the total number of Valid Requests during that period, subject to a minimum of 2000 Valid Requests in the measurement period. Repeated identical requests do not count towards the Error Rate unless they conform to the Back-off Requirements.
• For Event Notifications: The number of Valid Requests (dispatch attempts) that fail to be emitted due to internal Secure Source Manager infrastructure or system errors, divided by the total number of Valid Requests during that period, subject to a minimum of 2000 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:

• "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.
• "Region" means the applicable region identified at https://cloud.google.com/about/locations.
• "Valid Requests" are requests
• received by the Secure Source Manager control plane.
• for Git protocol transactions (e.g., a single git push or git fetch).
• for dispatch attempts of a webhook, Cloud Build pipeline trigger, or Developer Connect integration event. (For example, a single customer Git action triggering 5 distinct events will count as 5 Valid Requests for this Covered Service).

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. Customer must also provide Google with log files showing Downtime Periods and the date and time they occurred. 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 in the Project and Region that did not meet SLO for the applicable month. Financial Credits will be in the form of a monetary credit applied to future use of the Covered 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) configurations, 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 Documentation or Admin Console, or (v) arising from the delivery, receipt, or subsequent processing of Event Notifications after they have been successfully dispatched from Secure Source Manager. This exclusion applies regardless of the nature of the target endpoint, including but not limited to customer-managed systems (such as self-managed Jenkins), other Google Cloud services (such as Cloud Build and Developer Connect), or external third-party services. Factors beyond Secure Source Manager's control include, without limitation, network latency or outages, and the availability, configuration, or performance of the receiving service or endpoint.