Is Alation Cloud Service down?

A few customers might not have been able to access the platform due to a brief service interruption on the Alation instance in the US-East 1 cluster. Due to an infrastructure problem on our end, your Alation instance was momentarily unavailable on June 10, 2026, between roughly 4:04 PM and 4:38 PM IST (10:34–11:08 UTC). Errors may have occurred when users tried to access the platform during this window. By 4:38 PM IST (11:08 UTC), every system had fully recovered.

We are investigating elevated latency and intermittent errors affecting the Data Products and Alation AI. Other Alation functionality is unaffected. Mitigations are in progress and our team is actively working to identify the root cause.

We have identified the root cause of the elevated latency affecting Data Products and Alation AI. The team is working on mitigation.

The underlying issue has been mitigated. Data Products and Alation AI are returning to normal operation. We are continuing to monitor service health to confirm full recovery.

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

We recently experienced a service disruption that caused agent interactions to fail. The issue was traced to an expired token, which prevented a backend service from writing query results to storage. We have applied a temporary mitigation by recycling the affected tenant, which has restored normal functionality. Our team is actively working on a permanent fix to prevent this issue from recurring. Impact: This issue affected agent interactions only. All other platform functionality remained unaffected

We have applied a temporary mitigation by recycling the affected tenant, which has restored normal functionality. Our team is actively working on a permanent fix to prevent this issue from recurring.

The issue causing agent interaction failures has been resolved, and the agent system is now fully functional. We are actively monitoring system health to ensure continued stability.

This incident has been resolved.

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.