Skip to content

Lakebase Postgres SLADatabricks · Databases · Databricks · Databases

DatabasesChecked 18h ago

Promise vs reality

The Databricks status page has no public incident history feed. How this is measured
All incidents, weighted: 100% · Downtime
Promised
99.99%
Observed, 365d
n/a
Major incident time
n/a
Credit on first breach
5%

Commitments and credits

  • High Availability endpointLakebase endpoints with high availability (secondary compute instances' connection strings excluded)99.99%

    Monthly uptime below, credit of the bill

    1. Below 99.99%5%
    2. Below 99.9%10%
    3. Below 99%25%
    4. Below 95%50%
  • Single Compute endpointLakebase endpoints on a single compute instance99.9%

    Monthly uptime below, credit of the bill

    1. Below 99.9%10%
    2. Below 99%25%
    3. Below 95%50%

Terms

Measured
Monthly Uptime Percentage per Lakebase Endpoint; a minute is unavailable if all continuous connection attempts via the Covered Connection String fail
Credit cap
50% of the endpoint's monthly compute Fees (highest band)
Claim window
By the end of the calendar month following the month in which the SLA Event occurred
How to claim
Notify Databricks in writing at help@databricks.com with Verification Information (workspace ID, endpoint ID, request logs)

Not covered

  • Force majeure
  • Customer noncompliance with the Agreement or Databricks support recommendations
  • Customer acts or omissions incl. overloading the database, ignoring resource health concerns
  • Customer equipment, software or other technology
  • Use with a Beta Service
Less than 99.99% but greater than or equal to 99.9% | N/A | 5% ... Less than 95.0% | 50% | 50%
Databricks, SLA. Read the SLA

The page prints no version date. The Single Compute column reads 'N/A' for the 99.9-99.99% band, so the committed level for single compute is 99.9% (inferred from the first credit band). Credits are a % of the endpoint's compute Fees, applied to future Platform Services usage and not counting toward usage commitments.

Evidence: incidents, last 365 days

The Databricks status page has no public incident history feed.

Other databases SLAs

Promised in the SLAObserved on the vendor's status pagePartial historyShortfall

Summaries of published SLAs; the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.

Weekly: SLA changes from cloud, data and AI vendors, Fridays.