In addition to the definitions found in the Terms of Use, the following definitions apply to this SLA:
"Customer Data" means:
"Covered Services" means either Instances in Multiple Regions or A Single Instance.
"Downtime" means:
"Downtime Period" means a period of one or more consecutive minutes of Downtime. Partial minutes or intermittent Downtime for a period of less than one minute will not be counted towards any Downtime Periods.
"Financial Credit" means the following for a “Tiered Services”: if the monthly uptime did not meet the SLO, Customer will obtain a prorated credit for the downtime which will be credited to future monthly bills of the customer. Financial Credits will not be issued for an Order Form which requests “Non-Tiered Services” which provides no guarantees for uptime.
"Instances in Multiple Regions" means container instances hosted as part of the BUZZ HPC Services where instances are placed across two or more Regions.
"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 described in the BUZZ HPC Services documentation provided to Customer, denoted by physical location, such as NJ1, NY1 as may be updated by BUZZ HPC from time to time.
"Single Instance" means a single container instance hosted as part of the BUZZ HPC Services
"Tiered Services" means customer set out in its Order Form that it is selecting a tiered Services rather than a basic Services without redundancy or uptime guarantees.
BUZZ provides the HPC Cloud Services to the Customer at the following services level objectives (the "Services Level Objective" or "SLO")
Services Level
Tiered - Instances in Multiple Regions >=99.5% Monthly Uptime Percentage
Tiered - Instances in a Single Regions >=99% Monthly Uptime Percentage
Non-Tiered - Basic Compute - N/A Monthly Uptime Percentage
If BUZZ HPC does not meet the SLO, and if Customer is otherwise in good standing and meeting its obligations, Customer will be eligble to receive the Financial Credits described below. This SLA sets out and states Customer's sole and exclusive remedy for any failure by BUZZ HPC to meet the SLO.
A. Requesting Financial Credits
In order to receive any of the Financial Credits described above, Customer must notify BUZZ HPC technical support within ten (10) days from the time Customer becomes eligible to receive a Financial Credit. Customer must also provide BUZZ HPC with server log files showing loss of external connectivity errors and the date and time those errors occurred. If Customer does not comply with these requirements, Customer will forfeit its right to receive a Financial Credit. If a dispute arises with respect to this SLA, BUZZ HPC will make a determination in good faith based on its system logs, monitoring reports, configuration records, and other available information, which BUZZ HPC will make available for auditing by Customer at Customer’s request.
B. Maximum Financial Credit
The aggregate maximum number of Financial Credits to be issued by BUZZ HPC to Customer for any and all Downtime Periods that occur in a single billing month will not exceed 40% of the amount due from Customer for the Covered Services for the applicable month. Financial Credits will be made in the form of a monetary credit applied to future use of the Covered Services and will be applied within sixty (60) days after the Financial Credit was requested. Customer acknowledges and agrees that any Financial Credits for loss or interruption of compute power, constituting a Downtime Period, shall be ratably calculated based on the Term of an Order Form and granted in accordance with the SLA.
C. Exclusions
The Financial Credits do not apply to any: (a) features designated pre-general availability (unless otherwise set forth in the associated Documentation), (b) features excluded from the SLA (in the associated documentation), or (c) errors: (i) caused by factors outside of BUZZ HPC’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 behaviours that violate the BUZZ’s policies in place; or (iv) that resulted from quotas applied by the system, or (d) downtime caused by in-advance communicated maintenance. As applicable, Customer will only be entitled to Financial Credit for Downtime of a particular instance as either a Single Instance or Instances in Multiple Regions, but not both.
