Monte Carlo Data Outage History

Monte Carlo has resolved an issue that affected a subset of customers between 18:15 UTC on October 3 and 10:25 UTC on October 4. For affected customers, some monitor runs were incorrectly marked as "Timeout" and triggered failure notifications, even though in most cases the monitor queries had completed successfully. Those runs will continue to show as "Timeout" in run history, and the notifications can be dismissed; no action is needed from customers who did not see these errors.

The Snowflake incident has been resolved, and data collection and anomaly detection are back to normal on all affected accounts.

A fix was deployed on September 7 and integrations configured with a username and password reconnected automatically — data health updates to their Alation catalogs have resumed. The remaining affected integrations are configured with a refresh token only, which requires the customer to generate a new token in Alation and save it in Monte Carlo. Those customers have been notified directly with instructions, and their updates will resume as soon as the new token is saved. No Monte Carlo monitoring or alerting was affected at any point.

The app is now available at getmontecarlo.com as usual.

MS Teams notifications are working again.

Query log collection is normalized.

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.

Due to a Databricks outage on AWS, anomaly detection for legacy metric monitors (v1) was temporarily delayed. Data collection and all other monitoring capabilities were not affected. The underlying issue has been resolved by Databricks, and all affected processes have been re-run and completed successfully. Normal operation has fully resumed.