Databricks Azure experienced a minor incident on September 18, 2026 affecting Agent Bricks and Unity Catalog (Central India) and 1 more component, lasting 59m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Sep 18, 2026, 02:13 AM UTC
Impact Summary Between 00:19 UTC and 00:29 UTC on September 18, 2026, customers using Azure Databricks may have experienced degraded availability with Lakebase. Affected customers may have been unable to create, access, or operate Lakebase databases and related workloads during this window. Symptoms • Connection failures when attempting to reach Lakebase databases • Queries and administrative operations timing out or failing to complete • Errors returned by applications backed by Lakebase Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- monitoring Sep 18, 2026, 02:13 AM UTC
Impact Summary Between 00:19 UTC and 00:29 UTC on September 18, 2026, customers using Azure Databricks may have experienced degraded availability with Lakebase. Affected customers may have been unable to create, access, or operate Lakebase databases and related workloads during this window. Symptoms • Connection failures when attempting to reach Lakebase databases • Queries and administrative operations timing out or failing to complete • Errors returned by applications backed by Lakebase Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- resolved Sep 18, 2026, 03:13 AM UTC
Impact Summary Between 00:19 UTC and 00:29 UTC on September 18, 2026, customers using Azure Databricks may have experienced degraded availability with Lakebase. Affected customers may have been unable to create, access, or operate Lakebase databases and related workloads during this window. Symptoms • Connection failures when attempting to reach Lakebase databases • Queries and administrative operations timing out or failing to complete • Errors returned by applications backed by Lakebase Next Update This is the final update for this incident. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription