Iot Service Level Agreement
„Serious incidents“ are incidents that also strongly affect customer service, but the urgency is less than for critical errors, as it has a less direct or direct impact on system performance, customer and customer operation. Examples: During the term of the agreement in which Google has agreed to make the Google Cloud Platform available to the Customer (if applicable the „Agreement“), the Covered Service makes available to the Customer a monthly availability percentage as follows (the „Service Level Objective“ or „SLO“): „Critical Incidents“ are incidents that provide customer service (in particular capacity, B.B.B invoicing, invoicing, invoicing, maintenance) on a production system and require immediate corrective action. 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; (iv) resulting from quotas applied by the system or listed in the Admin Console; or (v) resulting from Customer`s use of the Covered Service in a manner that does not conform to the documentation, including invalid requirement fields, unauthorized users, or inaccessible data. This AWS Core Service Level Agreement („SLA“) is a policy that governs the use of AWS IoT Core and applies separately to each account used by AWS IoT Core. In the event of any conflict between the terms of this SLA and the terms of the AWS Customer Agreement or any other agreement with us that governs your use of our services (the „Agreement“), the terms of this SLA apply, but only to the extent of such conflict. . . .