This SLA covers Baseten Dedicated Inference where Baseten is the Hosting Party
The Service Level Agreement applies to the Baseten Products & Services known as Dedicated Inference, but only where Baseten is the Hosting Party. The document calls that service the "SLA Service", and its promises and remedies are written around it.
Supporting quotations
Applies to the Baseten Products & Services known as Dedicated Inference for which Baseten is the Hosting Party (the “SLA Service”)
This Service Level Agreement applies to the Baseten Products & Services known as Dedicated Inference for which Baseten is the Hosting Party (the “SLA Service”)
Qualifications & exceptions
Only Dedicated Inference where Baseten is the Hosting Party is the "SLA Service".
Not stated here
This document does not define "Hosting Party", "Customer" or "Term", and does not say whether other Baseten products are covered.
Legal Rights & Agreement Rules · Company commitment
Baseten commits to undertake commercially reasonable measures to ensure that System Availability equals or exceeds 99.9% during each calendar month. The document calls that level the "Service Standard". Availability is calculated each month from the records of Baseten's third-party service provider that monitors System Availability. Section 4.1 ties service credits to the SLA Service failing to meet the Service Standard in a month; the remedy cards cover that.
Supporting quotations
Baseten will undertake commercially reasonable measures to ensure that System Availability of Baseten Products & Services for which Baseten is the Hosting Party equals or exceeds ninety-nine point nine percent (99.9%) during each calendar month (the “Service Standard”)
All measurements of System Availability will be calculated on a monthly basis for each calendar month during the Term based on the records of Baseten’s third party service provider responsible for monitoring System Availability
In the event the SLA Service fails to meet the Service Standard in a given month
Qualifications & exceptions
The promise is stated as "commercially reasonable measures", not as a guarantee of 99.9%.
Measured by the records of Baseten's third-party monitoring provider.
This section refers to "Baseten Products & Services for which Baseten is the Hosting Party", while the scope paragraph and the credit section refer to the "SLA Service" (Dedicated Inference).
Not stated here
The document does not name the monitoring provider, say whether the Customer can see or check its records, or define "Term".
It does not say whether the "commercially reasonable measures" wording limits the credit entitlement when availability falls below 99.9%; section 4.1 conditions the credit on failing to meet the Service Standard.
Monthly availability is uptime measured against the month minus planned maintenance
System Availability for a calendar month is the Total Monthly Time minus Unscheduled Downtime, divided by the Total Monthly Time. Total Monthly Time is the minutes in the calendar month less Scheduled Downtime, so planned maintenance is taken out of the measuring period as well as out of the downtime.
Supporting quotations
“System Availability” means, with respect to any particular calendar month, the ratio obtained by subtracting Unscheduled Downtime during such month from the Total Monthly Time, and thereafter dividing the difference so obtained by the Total Monthly Time
System Availability = (Total Monthly Time – Unscheduled Downtime) / (Total Monthly Time)
“Total Monthly Time” means the total minutes in the relevant calendar month less Scheduled Downtime
A partial first month is measured against the whole calendar month
If the Customer subscribes to the SLA Service for only part of a calendar month, availability for that month is still calculated on the entire calendar month, not only on the portion for which the Customer subscribed.
Supporting quotations
For any partial calendar month during which Customer subscribes to the SLA Service, availability will be calculated based on the entire calendar month, not just the portion for which Customer subscribed.
Qualifications & exceptions
Applies to a partial calendar month in which the Customer subscribes.
Not stated here
The document does not say how a service credit is worked out for a month the Customer subscribed for only part of.
Legal Rights & Agreement Rules · Restriction or exception
Planned maintenance by Baseten is Scheduled Downtime with reasonable prior notice
Scheduled Downtime is the time in a calendar month, measured in minutes, during which the Customer cannot access the SLA Service because of planned system maintenance performed by Baseten. Baseten says it will give the Customer reasonable prior notice of such Scheduled Downtime. Scheduled Downtime is excluded from Total Monthly Time and from Unscheduled Downtime, so it does not count against the availability figure.
Supporting quotations
“Scheduled Downtime” means the total amount of time during any calendar month, measured in minutes, during which Customer is not able to access the SLA Service due to planned system maintenance performed by Baseten
Baseten will provide Customer with reasonable prior notice of such Scheduled Downtime
Qualifications & exceptions
Only planned system maintenance performed by Baseten.
Baseten promises "reasonable prior notice".
Not stated here
The document sets no limit on the amount or frequency of Scheduled Downtime, and does not define "reasonable prior notice" or say how notice is given.
Legal Rights & Agreement Rules · Context
Unscheduled Downtime is loss of access from a cause within Baseten's control
Unscheduled Downtime is the time in a calendar month, in minutes, during which the Customer cannot access the features and functions of the SLA Service as a result of a cause within Baseten's control, other than Scheduled Downtime. Only this time counts against System Availability.
Supporting quotations
“Unscheduled Downtime” means the total amount of time during any calendar month, measured in minutes, during which the Customer is not able to access the features and functions of the SLA Service as a result of a cause within Baseten’s control, other than Scheduled Downtime
Qualifications & exceptions
Only causes within Baseten's control; the exclusions listed in the same definition are covered in the next cards.
Not stated here
The document does not say whether degraded or partial functioning counts as not being "able to access the features and functions", or who decides whether a cause is "within Baseten's control".
Legal Rights & Agreement Rules · Restriction or exception
Customer-side problems and Customer-ignored advice are not counted as downtime
The definition of Unscheduled Downtime says it does not include periods when the SLA Service is unavailable because of the Customer's side: non-compliance with this SLA; incompatibility of the Customer's equipment or software; the Customer's use after Baseten advised it to modify its use, if it did not; acts or omissions of the Customer's employees, agents, contractors or vendors, or of anyone using the Customer's passwords or equipment; the performance of the Customer's systems or the Internet; and network unavailability or the Customer's bandwidth limitations.
Supporting quotations
(i) non-compliance by Customer with any provision of this SLA; (ii) incompatibility of Customer’s equipment or software with the SLA Service
(iv) Customer’s use of the SLA Service after Baseten has advised Customer to modify its use of the SLA Service, if Customer did not modify its use as advised; (v) acts or omissions of Customer or Customer’s employees, agents, contractors, or vendors, or anyone gaining access to the SLA Service by means of Customer’s passwords or equipment; (vi) performance of Customer’s systems or the Internet
(viii) network unavailability or Customer’s bandwidth limitations
Qualifications & exceptions
The list is introduced as "without limiting the foregoing" and says Unscheduled Downtime "shall not include" these periods.
Not stated here
"Performance of Customer's systems or the Internet" and "network unavailability" are not defined or limited in the document.
Legal Rights & Agreement Rules · Restriction or exception
Third-party failures, Internet failures and Force Majeure are not counted as downtime
The definition of Unscheduled Downtime also excludes periods of unavailability caused by actions or inactions of the Customer or third parties, any systemic Internet failures, failures of Baseten's third-party hosting or other third-party providers, and a Force Majeure. Because it covers failures of Baseten's own third-party hosting and other providers, an outage that originates there is not counted against System Availability.
Supporting quotations
(iii) actions or inactions of Customer or third parties
(vii) any systemic Internet failures
(ix) failures of Baseten’s third-party hosting or other third-party providers; (x) a Force Majeure
(xi) Scheduled Downtime.
Qualifications & exceptions
Part of the list of periods that Unscheduled Downtime "shall not include".
Not stated here
The document does not name which providers are "third-party hosting or other third-party providers", and states no condition on this exclusion tied to whether Baseten selected the provider or could have avoided the failure.
Legal Rights & Agreement Rules · Restriction or exception
Errors from unreserved or exceeded capacity are not counted as downtime
Unscheduled Downtime does not include errors, failed or rejected requests, throttling, rate-limiting, queuing or reduced throughput that result from capacity that is not reserved (the document gives on-demand capacity as an example) or from the Customer reaching or exceeding its reserved capacity for any SLA Service. The text adds that System Availability measures whether an SLA Service is reachable and operational and does not measure the Customer's ability to scale beyond its provisioned or committed capacity.
Supporting quotations
(xii) any error, failed or rejected request, throttling, rate-limiting, queuing, or reduced throughput resulting from capacity that is not reserved (eg on-demand capacity) or Customer reaching or exceeding its reserved capacity for any SLA Service
For clarity, System Availability measures whether an SLA Service is reachable and operational; it does not measure Customer's ability to scale beyond its provisioned or committed capacity.
Qualifications & exceptions
Applies to capacity that is not reserved, or reserved capacity the Customer reaches or exceeds.
Not stated here
The document does not define "reserved capacity" or "provisioned or committed capacity" or say how capacity is reserved. In the source text, item (xii) runs into the "For clarity" sentence without separating punctuation; the sentence is quoted as written.
Force Majeure is an open-ended list that includes supplier and upstream-provider problems
The document defines Force Majeure as any act, event or occurrence beyond Baseten's reasonable control, "including, without limitation" bugs or other problems in the software, firmware or hardware of Baseten's suppliers and outages or issues with upstream providers or network carriers, along with natural events, governmental acts or inaction, war, civil strife, sabotage, explosions, labor strikes and work stoppages, and acts of terror. Time lost to a Force Majeure is not Unscheduled Downtime.
Supporting quotations
“Force Majeure” means any act, event, or occurrence beyond Baseten’s reasonable control, including, without limitation, issues arising from bugs or other problems in the software, firmware or hardware of Baseten’s suppliers, outages or issues with upstream providers or network carriers
governmental acts or inaction, orders or injunctions, war, insurrection or civil strife, sabotage, explosions, labor strikes, work stoppages, and acts of terror
Qualifications & exceptions
The list is not closed ("including, without limitation").
Not stated here
The document does not say who decides whether an event is "beyond Baseten's reasonable control".
Legal Rights & Agreement Rules · Restriction or exception
The Customer maintains its own systems and configures them as Baseten instructs
The Customer is responsible for maintaining and managing its computer networks, servers and software, and any related equipment or services. It is also responsible for configuring its systems correctly according to any instructions Baseten provides, as may be necessary for access to the features and functions of the SLA Service. Under the downtime definition, unavailability from the Customer's non-compliance with this SLA is not counted.
Supporting quotations
Customer is responsible for maintenance and management of its computer network(s), servers, and software, and any equipment or services related to maintenance and management of the foregoing
Customer is responsible for correctly configuring its systems in accordance with any instructions provided by Baseten, as may be necessary for provision of access to the features and functions of the SLA Service
Qualifications & exceptions
Configuration duty applies to instructions "as may be necessary" for access to the SLA Service.
Not stated here
The document does not say how or where Baseten provides its configuration instructions.
Charges & Financial Obligations · User right or choice
Missing the monthly Service Standard entitles the Customer to a credit on future use
If the SLA Service fails to meet the Service Standard (99.9% System Availability) in a given month, the Customer is entitled to a service credit under the table in section 4.1. The credit is a monetary credit applied to future use of the SLA Service, and the table describes it as credited to future monthly bills. For a month in which the Customer subscribed for only part of it, availability is still calculated on the whole calendar month.
Supporting quotations
In the event the SLA Service fails to meet the Service Standard in a given month, Customer will be entitled to a service credit as set forth in the table below (“Service Credit”)
Service Credits will be made in the form of a monetary credit applied to future use of the SLA Service.
equals or exceeds ninety-nine point nine percent (99.9%) during each calendar month (the “Service Standard”)
“System Availability” means, with respect to any particular calendar month, the ratio obtained by subtracting Unscheduled Downtime during such month from the Total Monthly Time
For any partial calendar month during which Customer subscribes to the SLA Service, availability will be calculated based on the entire calendar month, not just the portion for which Customer subscribed.
Qualifications & exceptions
Applies to the SLA Service (Dedicated Inference) and to a month in which it fails the Service Standard.
Paid as a credit toward future use, not described as a payment.
Subject to the request requirement in section 4.3 and the cap in section 4.2.
Not stated here
The document does not say what happens to an unused credit if the Customer stops using the SLA Service, or whether a credit can be paid out.
It does not say how a credit is worked out for a month the Customer subscribed for only part of.
The credit table sets the percentage of the monthly bill for the respective SLA Service that will be credited to the Customer's future monthly bills, by Monthly System Availability. Availability below 99.9% but at least 99.5% earns 10.0%; below 99.5% but at least 99.0% earns 15.0%; below 99.0% earns 30.0%. The table lists no credit for availability at or above 99.9%, which meets the Service Standard.
Supporting quotations
Monthly System Availability Percentage of monthly bill for the respective SLA Service that does not meet the Service Standard that will be credited to future monthly bills of Customer
Less than 99.9% but greater than or equal to 99.5% 10.0%
Less than 99.5% but greater than or equal to 99.0% 15.0%
Less than 99.0% 30.0%
Qualifications & exceptions
Percentage of the monthly bill for the respective SLA Service (the table header says "that does not meet the Service Standard"), credited to future monthly bills.
Each tier is read by Monthly System Availability for the calendar month.
Not stated here
The table header's wording, "monthly bill for the respective SLA Service that does not meet the Service Standard", is not further explained; the document does not say whether other charges on the Customer's bill are in the base.
Charges & Financial Obligations · Restriction or exception
Credits for Unscheduled Downtime are capped at 40% of the month's amount due
The most Baseten will issue to the Customer as Service Credits for Unscheduled Downtime in a single calendar month is 40% of the amount due by the Customer for the applicable SLA Service for the applicable month. Only downtime from a cause within Baseten's control, other than Scheduled Downtime, counts as Unscheduled Downtime, as defined in section 1.4.
Supporting quotations
The maximum amount of Service Credits that Baseten will issue to Customer for Unscheduled Downtime in a single calendar month will not exceed forty percent (40%) of the amount due by Customer for the applicable SLA Service for the applicable month.
as a result of a cause within Baseten’s control, other than Scheduled Downtime
Qualifications & exceptions
Per calendar month and per applicable SLA Service.
Not stated here
The table's highest tier is 30%, below this 40% cap; the document does not say how the cap interacts with the table or when the cap would apply.
The Customer must email a credit request within 24 hours or Baseten owes no credit
To get a Service Credit, the Customer must send an email to billing@baseten.co identifying the date and time of the Unscheduled Downtime and giving sufficient evidence, including a description of the incident and its duration, within twenty-four hours following that Unscheduled Downtime. If the Customer does not request a credit to which it is entitled under section 4.3, Baseten has no obligation to issue it.
Supporting quotations
Customer must request such Service Credits by sending an e-mail identifying the date and time of the Unscheduled Downtime for which Customer is requesting Service Credits, with sufficient evidence (including description of the incident and duration of the incident) to billing@baseten.co within twenty four hours following such Unscheduled Downtime.
If Customer fails to request any Service Credits to which Customer is entitled in accordance with this Section 4.3, Baseten will have no obligation to issue such Service Credits to Customer.
Qualifications & exceptions
The request must be by email to billing@baseten.co, within twenty-four hours following the Unscheduled Downtime.
The request must identify the date and time and include evidence of the incident and its duration.
Not stated here
The document does not say whether the 24 hours run from the start or the end of the downtime, how Baseten judges whether evidence is "sufficient", or when the month's System Availability figure, which is calculated monthly, becomes available to the Customer relative to this 24-hour window.