Last Updated: July 10, 2018 | Previous versions
1. Service Commitment
Firebase will use commercially reasonable efforts to make Firebase available with a Monthly Uptime Percentage (defined below) of at least 99.95%, in each case during any monthly billing cycle (the "Service Commitment").
The following capitalized terms shall be given the meaning set forth below:
"Monthly Uptime Percentage" is calculated by subtracting from 100% the percentage of continuous 5 minute periods of Downtime during the month. Percentage measurements exclude downtime resulting directly or indirectly from any Firebase SLA Exclusion (defined below).
"Downtime" means more than a five percent Error Rate, or complete lack of external connectivity to the service. Downtime is measured based on server side Error Rate.
"Error Rate" means the number of Valid Requests that result in a response with HTTP Status 500 and Code "Internal 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.
"Back-off Requirements" means, when an error occurs, the 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.
A "Service Credit" is a dollar credit, calculated as set forth below, that we may credit back to an eligible account.
3. Service Commitments and Service Credits
Service Credits are calculated as a percentage of the total charges paid by you (excluding one-time payments such as upfront payments) for a Firebase service for the monthly billing cycle in which the Downtime occurred in accordance with the schedule below.
|Monthly Uptime Percentage||Service Credit Percentage|
|Less than 99.95% but equal to or greater than 99.0%||10%|
|Less than 99.0%||30%|
We will apply any Service Credits only against future Firebase payments otherwise due from you. At our discretion, we may issue the Service Credit to the credit card you used to pay for the billing cycle in which the Downtime occurred. Service Credits will not entitle you to any refund or other payment from Firebase. A Service Credit will be applicable and issued only if the credit amount for the applicable monthly billing cycle is greater than one dollar ($1 USD). Service Credits may not be transferred or applied to any other account. Unless otherwise provided in the Terms of Service, your sole and exclusive remedy for any unavailability, non-performance, or other failure by us to provide Firebase Services is the receipt of a Service Credit (if eligible) in accordance with the terms of this SLA.
4. Credit Request and Payment Procedures
To receive a Service Credit, you must submit a claim by submitting a support request through the SLA request form. To be eligible, the credit request must be received by us by the end of the second billing cycle after which the incident occurred and must include:
i. the issue category set to "Account Service";
ii. the issue component set to "Billing";
iii. the words "SLA Credit Request" as the issue summary;
iv. the dates and times of each Downtime incident that you are claiming;
v. the affected Firebase service urls; and
vi. your request logs that document the errors and corroborate your claimed outage (any confidential or sensitive information in these logs should be removed or replaced with asterisks).
If the Monthly Uptime Percentage of such request is confirmed by us and is less than the Service Commitment, then we will issue the Service Credit to you within one billing cycle following the month in which your request is confirmed by us. Your failure to provide the request and other information as required above will disqualify you from receiving a Service Credit.
5. Firebase SLA Exclusions
The Service Commitment does not apply to any unavailability, suspension or termination of Firebase Services, or any other Firebase or Firebase Services performance issues: (i) caused by factors outside of our reasonable control, including, without limitation, any force majeure event or Internet access or related problems beyond the demarcation point of Firebase Services; (ii) that result from any actions or inactions of you or any third party; (iii) that result from your equipment, software or other technology and/or third party equipment, software or other technology (other than third party equipment within our direct control); or (iv) arising from our suspension and termination of your right to use Firebase Services in connection with any breach by you of the Terms of Service or otherwise in accordance with the Terms of Service (collectively, the "Firebase SLA Exclusions"). If availability is impacted by factors other than those used in our Monthly Uptime Percentage calculation, then we may issue a Service Credit considering such factors at our discretion.