Gcp Service Level Agreement

The SLA does not apply to: (a) functions or services called alpha or beta (unless otherwise specified in the corresponding documentation), (b) functions or services excluded from the SLA (in the corresponding documentation), or (c) error: i) caused by factors that are not subject to Google`s proper control; (ii) resulting from Customer`s software or hardware, third-party software or hardware, or both; (iii) resulting from abuse or other conduct contrary to the Agreement; or (iv) resulting from quotas applied by the system and/or listed in the Admin Console. downtime does not include loss of external connectivity due to (i) the Google-operated VPN service, which does not provide traffic to VPN tunnels as part of that service; This type of downtime is handled exclusively in the vpn SLA cloud. or (ii) networked services, the standard tier does not allow traffic management. To obtain a service credit, you must create a claim by submitting an account support/billing request. To be justified, the credit request must have been received before the end of the second billing period after which the incident occurred and include: “downtime” means an error rate of more than 5% or the total absence of external connectivity with the service. Downtime is measured based on the error rate on the server side. Service credits are based on a percentage of the total monthly service fee you paid for the relevant Firebase service in the month the downtime occurred, calculated as shown in the schedule below. The monthly service fee does not include one-time payments, such as advances and advances, and excludes professional service and/or technical assistance or maintenance fees. During the term of the agreement by which Google has agreed to make the Google Cloud Platform available to Customer (if applicable, the “Agreement”), the Covered Service makes available to Customer a monthly availability percentage as follows (“Service Level Objective” or “SLO”): “Covered Service”, the following authentication services provided for a Customer Application as part of the Identity Platform: (i) email and password requests and (ii) updating an existing authentication JSON web token (“JWT”) .