Monte Carlo Data incident
Databricks SQL outage impacting Databricks integration (AWS us-east-1)
Resolved after 1 day 2 hours, on May 8, 2026.
As of May 9, 2026 02:32 UTC, Databricks has marked the incident as Resolved. Databricks SQL warehouses and Unity Catalog access have stabilized, and metadata collection and monitor evaluations are operating normally for all customers using the Databricks integration.
Other major vendors with incidents that started within 30 minutes of this one
Update timeline
- monitoring May 08, 2026, 12:00 AM UTC
A Databricks incident (~7 May 2026, 23:00 UTC) affected Databricks SQL warehouses and Unity Catalog, causing metadata collection delays and monitor evaluation failures or timeouts for a subset of customers using the Databricks integration. The upstream incident is now resolved on Databricks' side, but some customer warehouses are still working through query backlog accumulated during the incident, so individual customers may continue to see elevated runtimes or sporadic timeouts until their warehouse capacity returns to baseline.
- resolved May 09, 2026, 04:22 PM UTC
As of May 9, 2026 02:32 UTC, Databricks has marked the incident as Resolved. Databricks SQL warehouses and Unity Catalog access have stabilized, and metadata collection and monitor evaluations are operating normally for all customers using the Databricks integration.
Your product runs on more than Monte Carlo Data
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services