**Azure Databricks – Model Serving Degradation (June 26, 2026)** Starting at approximately 06:46 UTC, a subset of Azure Databricks customers experienced errors, timeouts, and degraded availability when accessing Model Serving endpoints, specifically around served model build logs and related served-entity operations. The incident lasted approximately 2 hours, with engineering teams actively engaged throughout. As of the latest update, the investigation was still ongoing with no customer action required.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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 6:46 UTC on June 26, 2026, a subset of customers using Azure Databricks may be experiencing errors or failures when using Model Serving, specifically when accessing served model build logs and related endpoints.
Symptoms
• Errors or timeouts when attempting to retrieve build logs for served model entities in Model Serving
• Requests to Model Serving endpoints failing or taking an extended time before returning an error
• Degraded availability of Model Serving served-entity operations
Recommendations
No customer action is required at this time.
Current Status
We are actively investigating an issue causing errors and timeouts for a subset of customers using Model Serving, and our engineering teams are engaged.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 6:46 UTC on June 26, 2026, a subset of customers using Azure Databricks may be experiencing errors or failures when using Model Serving, specifically when accessing served model build logs and related endpoints.
Symptoms
• Errors or timeouts when attempting to retrieve build logs for served model entities in Model Serving
• Requests to Model Serving endpoints failing or taking an extended time before returning an error
• Degraded availability of Model Serving served-entity operations
Recommendations
No customer action is required at this time.
Current Status
We are actively investigating an issue causing errors and timeouts for a subset of customers using Model Serving, and our engineering teams are engaged.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with