This Databricks Lakebase Service Level Agreement (“Lakebase SLA”) governs the availability of Lakebase Postgres (as described in the Documentation) on Databricks Platform Services. Capitalized terms used but not otherwise defined in this Lakebase SLA are defined in the Databricks Master Cloud Services Agreement (“MCSA”). Databricks reserves the right to change the terms of this Lakebase SLA.

1. Service Availability and Service Credits.

   1. Calculation. In the event any Lakebase Endpoint has a Monthly Uptime Percentage in the applicable ranges specified in the table below (an “SLA Event”), Customer will be eligible to receive Service Credits. Service Credits are calculated as a percentage of the compute Fees for the Lakebase Endpoint (excluding taxes and any related Fees for Advisory Services and Support Services) that experienced an SLA Event during the calendar month in which the SLA Event occurred. The applicable percentage is specified in the “Service Credit Percentage” column of the table below:

      Monthly Uptime Percentage	Service Credit Percentage
      	Single Compute	High Availability
      Less than 99.99% but greater than or equal to 99.9%	N/A	5%
      Less than 99.9% but greater than or equal to 99.0%	10%	10%
      Less than 99.0% but greater than or equal to 95.0%	25%	25%
      Less than 95.0%	50%	50%

   2. Service Credit Requests and Payment Procedures. Customer must notify Databricks in writing of each SLA Event by the end of the calendar month following the calendar month in which the SLA Event occurred by contacting help@databricks.com and providing Databricks with all Verification Information. Databricks will issue Customer a Service Credit within 45 days of Databricks' determination that an SLA Event occurred. This Lakebase SLA sets forth Customer’s sole and exclusive remedies, and Databricks’ sole and exclusive obligations, for an SLA Event.
2. Definitions.
   1. “Covered Connection String” means any Lakebase Endpoint connection string, excluding connection strings to secondary compute instances within a high availability endpoint (as described in the Documentation).
   2. “SLA Exclusions” means that a Lakebase Endpoint has no successful connectivity within a one-minute interval for the following reasons or under the following conditions:
      1. as a result of force majeure events (as described in the MCSA);
      2. Customer’s noncompliance with the Agreement or recommendations, if any, made by Databricks in the provision of Support Services;
      3. Customer’s or Authorized User’s acts or omissions, including failure to adhere to best practices as described in the Documentation (e.g. overloading the database) and failure to respond to resource health concerns;
      4. as a result of Customer’s equipment, software, or other technology; or
      5. use of a Lakebase Endpoint in conjunction with a Beta Service.
   3. “Lakebase Endpoint” means a Lakebase endpoint as described in the Documentation.
   4. “Monthly Uptime Percentage” is calculated by subtracting from 100% the percentage of minutes during a calendar month in which a Lakebase Endpoint was in the state of Unavailability.
   5. “Service Credits” means credits that are calculated as set forth above and, once awarded, are applied to the USD value of Customer’s usage of the Platform Services until such credits are completely drawn down upon, provided that such usage does not contribute toward satisfying Customer’s usage commitments to Databricks, if any.
   6. “Unavailability” means the Covered Connection String of a Lakebase Endpoint in an active state has no successful connectivity, excluding SLA Exclusions, for a one-minute interval, as determined by Databricks. A Lakebase Endpoint is considered as having no successful connectivity for a one-minute interval if all of Customer’s continuous attempts to establish a connection to a Lakebase Endpoint via the Covered Connection String within the minute fail.
   7. “Verification Information” means
      1. a detailed description of the events resulting in Unavailability, including Customer’s Workspace ID, Lakebase Endpoint ID, request logs that document the errors and corroborate Customer's claimed unavailability (with any confidential or sensitive information in the logs removed or replaced with asterisks);
      2. information regarding the date, time, and duration of the Unavailability;
      3. the number and location(s) of affected users (if applicable); and
      4. descriptions of Customer’s attempts to resolve the Unavailability at the time of occurrence.