Monte Carlo Data incident

Data health updates to Alation catalogs not being sent

Minor Resolved

Monte Carlo Data experienced a minor incident on August 29, 2026, lasting 9d 19h. The incident has been resolved; the full update timeline is below.

Started
Aug 29, 2026, 12:45 AM UTC
Resolved
Sep 07, 2026, 08:00 PM UTC
Duration
9d 19h
Detected by Pingoru
Aug 29, 2026, 12:45 AM UTC

Update timeline

  1. monitoring Jul 29, 2026, 12:45 AM UTC

    Since August 29, some Alation integrations have stopped receiving data health updates from Monte Carlo after their stored credentials stopped being accepted. Monitoring and alerting inside Monte Carlo were not affected. A fix is now live. Integrations configured with a username and password have reconnected automatically. Integrations using a refresh token need a new token generated in Alation and saved in Monte Carlo will need to update their refresh token.

  2. resolved Sep 08, 2026, 01:00 PM UTC

    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.