ES-1948471

We are actively investigating an issue with the Databricks service.

Next Update

We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 00:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances.

Symptoms
• Pipeline runs are failing or terminating unexpectedly with errors
• Lakebase queries and connections are failing with connectivity errors
• Synced table pipelines are unable to complete successfully

Recommendations
No customer action is required at this time.

Current Status
We are actively investigating an issue causing failures and errors with Declarative Pipelines and Lakebase, and our engineering teams are working to resolve the disruption.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 00:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances.

Symptoms
• Pipeline runs are failing or terminating unexpectedly with errors
• Lakebase queries and connections are failing with connectivity errors
• Synced table pipelines are unable to complete successfully

Recommendations
If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting.

Current Status
We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 00:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances.

Symptoms
• Pipeline runs are failing or terminating unexpectedly with errors
• Lakebase queries and connections are failing with connectivity errors
• Synced table pipelines are unable to complete successfully

Recommendations
If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting.

Current Status
We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 00:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances.

Symptoms
• Pipeline runs are failing or terminating unexpectedly with errors
• Lakebase queries and connections are failing with connectivity errors
• Synced table pipelines are unable to complete successfully

Recommendations
If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting.

Current Status
We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 00:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances.

Symptoms
• Pipeline runs are failing or terminating unexpectedly with errors
• Lakebase queries and connections are failing with connectivity errors
• Synced table pipelines are unable to complete successfully

Recommendations
If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting.

Current Status
We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 00:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances.

Symptoms
• Pipeline runs are failing or terminating unexpectedly with errors
• Lakebase queries and connections are failing with connectivity errors
• Synced table pipelines are unable to complete successfully

Recommendations
If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting.

Current Status
We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.