Alation Cloud Service Status Page

May 20, 2026 · resolved May 20

This incident has been resolved. Data Products and Alation AI are operating normally. A detailed RCA will be shared shortly.

Apr 24, 2026 · resolved Apr 25

This issue has now been fully resolved. We identified that the root cause was related to an expired token that was not being renewed as expected. To address this, we implemented a code fix that ensures tokens are automatically refreshed before they expire. This enhancement prevents similar disruptions from occurring in the future and improves the overall reliability of the system.

Apr 23, 2026 · resolved Apr 23

We discovered an issue where Rich Text Editor fields across the Catalog are not displaying content correctly. The issue has been resolved by rolling back the problematic deployment.

Mar 11, 2026 · resolved Mar 12

We have not seen the error reoccur in the last few hours; we are marking the incident as resolved.

Feb 19, 2026 · resolved Feb 19

Our investigation determined that the incident was driven by IOPS saturation on a few compute nodes in one of the node groups in the us-east-1 region. This condition impacted a subset of our infrastructure and contributed to intermittent downstream service errors for a handful of customers in this region. As part of remediation, we will be increasing the provisioned IOPS capacity for the impacted node group to provide additional IO headroom and improve overall resilience. We are also working closely with AWS to analyse the underlying increase in disk usage further and validate long-term corrective measures. Services are currently stable. We are continuing to monitor closely to ensure sustained reliability. We apologise for the inconvenience and will follow up with a detailed root cause analysis.