Alation Cloud Service Status

Resolved: The underlying AWS service has recovered, and all Alation services have returned to normal operation for affected customers. Our teams will continue to monitor the environment to ensure continued stability.

Monitoring: AWS further reports “significant signs of recovery”: most requests should now be succeeding, though some services still have latency and backlog to clear. We see early signs of Alation service recovery; we will keep you updated.

Identified: AWS states that they are still working on finding the root cause and actively working on the issue.

Identified: We have detected elevated error rates and degraded performance across parts of the Alation platform. This is caused by a service disruption at AWS, which is affecting one or more of their core services that Alation depends on. Our own systems are healthy, but upstream instability is affecting service delivery for our users.

Impact: Some users may experience slower response times, timeouts, or failures when using certain features (for example: data catalog search, ingestion jobs, API calls or dashboard refreshes).

Data integrity is not impacted; no data loss or corruption has been detected. Queued operations will retry automatically once upstream services recover.

Resolved: Fix has been implemented and confirmed to successfully resolve the issue. Root cause was result of AWS US-East-1 outage from previous day (Monday, October 20).

Identified: Cause has been identified and fix implemented. Working on resolution.

Investigating: We are currently investigating an issue with the MDE Pipeline service, which is preventing data extraction and causing errors. The error is related to a timeout connection to the pipeline service. Our team is working to resolve the issue as quickly as possible.

We will keep you posted with the progress as it becomes available.

Resolved: The issue that was impacting customers in the EU region has been resolved, system performance is showing normal performance, and the services are now operating normally.

Identified: A subset of EU customers may experience: Slower load times or timeouts when accessing the Alation application. Delays in query execution, search indexing, and accessing catalog services

Identified: We are investigating reports of degraded performance impacting customers in the EU region.

Resolved: The underlying AWS service has recovered, and all Alation services have returned to normal operation for affected customers. Our teams will continue to monitor the environment to ensure continued stability.

Monitoring: AWS further reports “significant signs of recovery”: most requests should now be succeeding, though some services still have latency and backlog to clear. We see early signs of Alation service recovery; we will keep you updated.

Identified: AWS states that they are still working on finding the root cause and actively working on the issue.

Identified: We have detected elevated error rates and degraded performance across parts of the Alation platform. This is caused by a service disruption at AWS, which is affecting one or more of their core services that Alation depends on. Our own systems are healthy, but upstream instability is affecting service delivery for our users.

Impact: Some users may experience slower response times, timeouts, or failures when using certain features (for example: data catalog search, ingestion jobs, API calls or dashboard refreshes).

Data integrity is not impacted; no data loss or corruption has been detected. Queued operations will retry automatically once upstream services recover.

Resolved: Fix has been implemented and confirmed to successfully resolve the issue. Root cause was result of AWS US-East-1 outage from previous day (Monday, October 20).

Identified: Cause has been identified and fix implemented. Working on resolution.

Investigating: We are currently investigating an issue with the MDE Pipeline service, which is preventing data extraction and causing errors. The error is related to a timeout connection to the pipeline service. Our team is working to resolve the issue as quickly as possible.

We will keep you posted with the progress as it becomes available.