The Splunk Observability Cloud services will be available 99.9% of the time, as measured by Splunk over each calendar month of the Subscription Term, and subject to the exclusions set forth below (the “Service Level Commitment”).
A Splunk Observability Cloud service is considered available if Customers are able to login to the service interface and access monitoring data.
If Splunk fails to achieve the above Service Level Commitment for one of the Splunk Observability Cloud services, Customer may claim a service credit for such Splunk Observability Cloud service that is equal to the amount of time the service was deemed not available.
Credits may not be redeemed for a reimbursement.
A Customer will not be entitled to a service credit if it is in breach of its Agreement with Splunk, including payment obligations or usage exceeding the purchased Capacity. The Service Level Commitment does not apply to any downtime, suspension or termination of the applicable Splunk Observability Cloud service that results from:
No Service Level Commitment is provided for free, proof-of-concept or unpaid trial services.
To receive a service credit, a Customer must file a claim for such credit within five (5) days following the end of the calendar quarter in which the Service Level Commitment was not met for an applicable Splunk Observability Cloud service, by contacting Splunk at firstname.lastname@example.org with a complete description of the downtime, how the Customer was adversely affected, and for how long. Splunk reserves the right to deny the service credit if the Customer does not qualify.
The service credit remedy set forth in this Service Level Commitment is the Customer's sole and exclusive remedy for the unavailability of any applicable Splunk Observability Cloud service. Credit is only applicable to the specific impacted service for the given time period.
*All capitalized terms not otherwise defined are as set forth in the Splunk General Terms.