DataStax commits to service levels as provided in this Service Level Agreement (&ldquo;SLA&rdquo;) . In the event DataStax does not meet the Service Availability, the Customer may be eligible to receive a Service Credit as described below. This SLA applies only to paid use of DataStax Astra if the DataStax Astra Database has been up for a minimum of 24 hours, and does not apply to any other products offered by DataStax.
<h3>Definitions</h3>
Month &ndash; shall be the calendar month
Emergency Maintenance &ndash; Should DataStax be required to conduct unscheduled systems maintenance, it will be announced no less than 48 hours in advance and not exceed one hour of planned downtime per calendar quarter. Maintenance due to critical security or system stability concerns may be performed without announcement or prior warning.
Scheduled Maintenance - Maintenance is scheduled to occur without any impact to the Database traffic.
Single Region / Single Availability Zone Service Availability​ &ndash; Is calculated per DataStax Astra Database on a monthly basis and is calculated:
= (the total minutes in a month - the total number of minutes of simultaneous Service Outage of all of the nodes in the region)/ total minutes in the calendar month and rounding to the nearest 10th of one percent. Any portion of the month for which the DataStax Astra Database is Suspended or which Customer was not utilizing the Cloud Services shall be considered to have a 100% Service Availability.
Example: Based on one hour of Service Outage within a month:
43200 &ndash; 60 (43,140) / 43200 = 99.86% Availability within the month.
Single Region / Multi Availability Zone Service Availability​ &ndash; Is calculated per DataStax Astra Database on a monthly basis and is calculated:
= (the total minutes in a month - the total number of minutes of simultaneous Service Outage of all of the nodes in all of the availability zones in the region)/ total minutes in the calendar month and rounding to the nearest 10th of one percent. Any portion of the month for which the DataStax Astra Database is Suspended or which Customer was not utilizing the Cloud Services shall be considered to have a 100% Service Availability.
Example: Based on one hour of Service Outage within a month:
43200 &ndash; 60 (43,140) / 43200 = 99.86% Availability within the month.
Multi-Region Service Availability​ &ndash; Is calculated based on the overall availability of the DataStax Astra Databases across multiple regions on a monthly basis. Availability is calculated:
= (the total minutes in a month - the total number of minutes of simultaneous Service Outage of all regions) / total minutes in the calendar month and rounding to the nearest 10th of one percent. Any portion of the month for which the DataStax Astra Database is Suspended or which Customer was not utilizing the Cloud Services shall be considered to have a 100% Service Availability.
Example: Based on one hour of Service Outage within a month:
43200 &ndash; 60 (43,140) / 43200 = 99.86% Availability within the month.
Service Outage &ndash; Is calculated per DataStax Astra Database on a monthly basis and is the total number of minutes during the month that the entire DataStax Astra Database was unavailable. A minute is considered unavailable if all of your continuous attempts to establish a connection to your DataStax Astra Database within the minute fail, unless such failure is due to an SLA exclusion set forth below.
Validated Service Credit &ndash; a credit due to Customer based on a missed Service Availability as further set forth below.
<h3>Service Availability</h3>
If the Service Availability is less than the percentages indicated in the DataStax Astra Availability chart below, for the product the Customer has deployed, and if Customer has fulfilled all of its obligations under the Agreement and this SLA, DataStax will provide Customer a Service Credit for the month in which the failure to meet this SLA has occurred. The Service Credit is calculated as the percentage of the monthly Fees for the applicable DataStax Astra Database that is credited&nbsp; to Customer for a validated claim for a failure to meet the SLA during that month, in accordance with the table below. SLA verification will be conducted by Datastax.
<h3>DataStax Astra Availability Per Calendar Month</h3>
<table style="border-collapse: collapse; width: 100%; border-color: #7e8c8d; border-style: hidden;">
<tbody>
<tr>
<td style="width: 54.9091%;">&nbsp;</td>
<td style="width: 15.2727%;">
Single Region Single AZ
</td>
<td style="width: 15.2727%;">
Single Region Multi AZ
</td>
<td style="width: 14.5455%;">
Multi Region
</td>
</tr>
<tr>
<td style="width: 54.9091%;">
Equal to or greater than 99.99% but less than 99.999% (Multi Region Only)
</td>
<td style="width: 15.2727%;">
N/A
</td>
<td style="width: 15.2727%;">
N/A
</td>
<td style="width: 14.5455%;">
10%
</td>
</tr>
<tr>
<td style="width: 54.9091%;">
Equal to or greater than 99.9% but less than 99.99%
</td>
<td style="width: 15.2727%;">
N/A
</td>
<td style="width: 15.2727%;">
10%
</td>
<td style="width: 14.5455%;">
10%
</td>
</tr>
<tr>
<td style="width: 54.9091%;">
Less than 99.9%
</td>
<td style="width: 15.2727%;">
10%
</td>
<td style="width: 15.2727%;">
10%
</td>
<td style="width: 14.5455%;">
15%
</td>
</tr>
</tbody>
</table>
&nbsp;
A Validated Service Credit shall be credited and applied to future invoices for the applicable DataStax Astra Database. Unless otherwise provided in your agreement with DataStax covering the use of DataStax Astra, your sole and exclusive remedy for any unavailability, non-performance, or other failure by us to provide DataStax Astra is the receipt of a Service Credit (if eligible) in accordance with the terms of this SLA. Validated Service Credits do not entitle the Customer to any cash refund or other payment from DataStax. If Customer has not configured their applications to fail over to a second region, Customer will only be entitled to a Validated Service Credit for 99.9% availability.
<h3>Customer Obligations</h3>
To be eligible for a Service Credit:
<ul>
<li style="font-weight: 400;" aria-level="1">Customer must log a support ticket with DataStax Astra in accordance with the DataStax Astra Support Policy immediately upon becoming aware of an event that impacts service availability.</li>
<li style="font-weight: 400;" aria-level="1">Customer must submit a claim to DataStax via email at servicecredits@datastax.com within five (5) calendar days of the month end that the incident occurred to receive a Service Credit under this SLA.</li>
<li style="font-weight: 400;" aria-level="1">Customer should include all information necessary for DataStax to validate the claim, including: (i) a detailed description of the events resulting in Service Outage, including your request logs that document the errors and corroborate your claimed outage (with any confidential or sensitive information in the logs removed or replaced with asterisks); (ii) information regarding the time and duration of the Service Outage; (iii) the number and location(s) ; and (iv) descriptions of your attempts to resolve the Service Outage at the time of occurrence (v) For 99.999% availability claims, proof that the applications were configured for multi-regions at the time of the incident.</li>
<li style="font-weight: 400;" aria-level="1">Customer must reasonably assist DataStax in investigating the cause of the Service Outage and processing the claim.</li>
<li style="font-weight: 400;" aria-level="1">Customer must comply with your applicable DataStax Astra service agreement, applicable DataStax Astra documentation and any reasonable advice from our support or engineering teams.</li>
</ul>
<h3>Exclusions And Exceptions:</h3>
The Service Availability, Service Outage, and Customer&rsquo;s entitlements to Service Credits under this SLA do not apply under the following circumstances:
<ol>
<li style="font-weight: 400;" aria-level="1">caused by factors outside of DataStax&rsquo;s reasonable control, including any force majeure event or Internet access failure or related problems beyond the demarcation point of DataStax Astra</li>
<li style="font-weight: 400;" aria-level="1">that result from any actions or inactions of Customer or any third party, including unauthorized modifications to the Cloud Services;</li>
<li style="font-weight: 400;" aria-level="1">that result from any third party services, equipment, software or other technology (including from the Cloud Provider) other than third party equipment within DataStax&rsquo;s direct control;</li>
<li style="font-weight: 400;" aria-level="1">that arise from DataStax&rsquo;s suspension or termination of Customer&rsquo;s right to use the Cloud Services in accordance with the Agreement</li>
<li style="font-weight: 400;" aria-level="1">that result from a denial of service or similar malicious attack; or</li>
<li style="font-weight: 400;" aria-level="1">Emergency Maintenance</li>
</ol>
If using BYOK causes availability issues due to availability from the hosting provider, user configuration issues or delays in DataStax providing support due to the use of BYOK.&nbsp; &ldquo;BYOK&rdquo; means the Bring Your Own Key feature, allowing a Customer to manage the encryption and in extension the key that controls encryption/decryption of Customer data in a given database Cluster.

Build and scale cloud native apps

Discover the benefits of DBaaS and why your apps deserve an upgrade.

Learn about NoSQL Databases

Learn about NoSQL databases with Apache Cassandra and Astra DB.

2022 Recap: A Year for Customers, Community, and Real-Time Data

Highlights from 2022 and a glimpse into the year ahead.

Astra Service Level Agreement

Last Updated Date:
April 20, 2023

Astra Service Level Agreement

Last Updated Date: April 20, 2023

Last Updated Date:
April 20, 2023