Alation Cloud Service Outage History

Alation Cloud Service is up right now

Alation Cloud Service had 15 outages in the last 2 years totaling 68h 53m of downtime — averaging 0.6 incidents per month.

There were 15 Alation Cloud Service outages since October 20, 2025 totaling 68h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.alationcloud.com

Notice September 22, 2026

Third-party provider outage (AWS) US-East-1

Detected by Pingoru
Sep 22, 2026, 12:25 AM UTC
Resolved
Sep 22, 2026, 12:32 AM UTC
Duration
6m
Affected: Americas (US-east) - DevAmericas (US-east)PoV (Proof of Value)
Timeline · 3 updates
  1. identified Sep 22, 2026, 12:25 AM UTC

    AWS is reporting a service disruption in us-east-1 region, which is affecting one or more of their core services that Alation depends on. Our own systems are healthy, but AWS instability may possibly affect 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.

  2. monitoring Sep 22, 2026, 12:31 AM UTC

    AWS has reported the issues has been resolved. Our teams will continue to monitor the environment to ensure continued stability.

  3. resolved Sep 22, 2026, 12:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 10, 2026

Connectivity Issues: US-East-1 Cluster

Detected by Pingoru
Sep 10, 2026, 12:15 AM UTC
Resolved
Sep 10, 2026, 02:41 AM UTC
Duration
2h 25m
Affected: Americas (US-east)
Timeline · 3 updates
  1. investigating Sep 10, 2026, 01:29 AM UTC

    We are currently investigating connectivity issues affecting services hosted on our US-East-1 (use1) cluster. Some customers may experience delays, timeouts, or intermittent failures when accessing the affected services. Our engineering team is actively investigating the root cause and working to restore full connectivity as quickly as possible. We will post updates here as more information becomes available. If you are experiencing impact, we appreciate your patience while we work to resolve this issue.

  2. monitoring Sep 10, 2026, 01:53 AM UTC

    The connectivity issues affecting services hosted on our US-East-1 (use1) cluster. Alerts are now recovering and we are seeing signs of improvement across affected services. Our engineering team continues to monitor closely to confirm full recovery. We will post another update once systems are fully stable. We appreciate your patience while we complete this monitoring period

  3. resolved Sep 10, 2026, 02:41 AM UTC

    The connectivity issues affecting services hosted on our US-East-1 (use1) cluster have been resolved. All the services are operating normally. We will continue monitoring to ensure stability. If you continue to experience any issues, please reach out to support. Thank you for your patience throughout this incident.

Read the full incident report →

Critical August 20, 2026

Service Disruption – APAC(Sydney)

Detected by Pingoru
Aug 20, 2026, 10:08 PM UTC
Resolved
Aug 20, 2026, 10:27 PM UTC
Duration
18m
Affected: APAC (Sydney)
Timeline · 2 updates
  1. identified Aug 20, 2026, 10:08 PM UTC

    We are currently experiencing a service disruption affecting all customers in the APAC(Sydney) region. Our team has identified the root cause and is actively working on implementing a fix.

  2. resolved Aug 20, 2026, 10:27 PM UTC

    The service disruption has been resolved. All systems are operating normally. We apologize for the inconvenience and thank you for your patience.

Read the full incident report →

Major August 18, 2026

Degraded availability for a subset of customers

Detected by Pingoru
Aug 18, 2026, 04:35 PM UTC
Resolved
Aug 18, 2026, 05:31 PM UTC
Duration
55m
Affected: Americas (US-east)
Timeline · 3 updates
  1. identified Aug 18, 2026, 04:35 PM UTC

    We are currently investigating an issue affecting a limited number of customers. Our team is actively working on a resolution

  2. monitoring Aug 18, 2026, 04:44 PM UTC

    Fix has been implemented and we are actively monitoring the environment to ensure stability. Affected customers should see services restored.

  3. resolved Aug 18, 2026, 05:31 PM UTC

    The issue has been resolved and all affected customers are fully operational. Our team has confirmed stability across the environment.

Read the full incident report →

Major August 10, 2026

Service Disruption: eu-west-1

Detected by Pingoru
Aug 10, 2026, 09:15 PM UTC
Resolved
Aug 10, 2026, 10:20 PM UTC
Duration
1h 5m
Affected: EMEA (Ireland)
Timeline · 5 updates
  1. investigating Aug 10, 2026, 09:15 PM UTC

    We're aware that our eu-west-1 region is currently unavailable, and our team is already on it. We know how important reliable access is, and restoring service is our top priority right now. We'll keep you updated as we make progress — thank you for bearing with us.

  2. investigating Aug 10, 2026, 09:16 PM UTC

    We are continuing to investigate this issue.

  3. identified Aug 10, 2026, 10:04 PM UTC

    We've identified the cause of the issue affecting our eu-west-1 region and are working on a fix. We'll share another update shortly. Thank you for your patience.

  4. monitoring Aug 10, 2026, 10:15 PM UTC

    A fix has been implemented and eu-west-1 is now operating normally. We're monitoring closely to confirm full stability. Thank you for your patience.

  5. resolved Aug 10, 2026, 10:20 PM UTC

    The issue affecting our eu-west-1 region has been fully resolved and all services are operating normally. Thank you for your patience throughout, and we apologize for any inconvenience caused.

Read the full incident report →

Notice June 10, 2026

Service Disruption — Alation Cloud

Detected by Pingoru
Jun 10, 2026, 10:30 AM UTC
Resolved
Jun 10, 2026, 10:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 10, 2026, 03:47 PM UTC

    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.

Read the full incident report →

Minor May 20, 2026

Data Products Service — Elevated Latency and Errors

Detected by Pingoru
May 20, 2026, 03:38 PM UTC
Resolved
May 20, 2026, 07:04 PM UTC
Duration
3h 26m
Affected: Americas (US-east) - DevAmericas (US-east)
Timeline · 4 updates
  1. investigating May 20, 2026, 03:38 PM UTC

    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.

  2. identified May 20, 2026, 04:07 PM UTC

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

  3. monitoring May 20, 2026, 05:25 PM UTC

    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.

  4. resolved May 20, 2026, 07:04 PM UTC

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

Read the full incident report →

Minor April 24, 2026

Service Disruption Affecting Agent Interactions

Detected by Pingoru
Apr 24, 2026, 01:00 AM UTC
Resolved
Apr 25, 2026, 06:52 AM UTC
Duration
1d 5h
Affected: Americas (US-east)Americas (US-west)Canada (Montreal)EMEA (Ireland)EMEA (Frankfurt)APAC (Sydney)APAC (Singapore)APAC (Tokyo)APAC (Mumbai)
Timeline · 4 updates
  1. investigating Apr 24, 2026, 02:38 PM UTC

    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

  2. identified Apr 24, 2026, 02:39 PM UTC

    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.

  3. monitoring Apr 24, 2026, 05:47 PM UTC

    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.

  4. resolved Apr 25, 2026, 06:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 23, 2026

Alation Service Degradation - Catalog editor

Detected by Pingoru
Apr 23, 2026, 03:57 PM UTC
Resolved
Apr 23, 2026, 03:57 PM UTC
Duration
—
Affected: Americas (US-east) - DevAmericas (US-east)Americas (US-west)Americas (US-west) - DevCanada (Montreal)Canada (Montreal) - DevEMEA (Ireland)EMEA (Ireland) - DevEMEA (Frankfurt) - DevEMEA (Frankfurt)APAC (Sydney)APAC (Sydney) - DevAPAC (Singapore) - DevAPAC (Singapore)APAC (Tokyo)APAC (Tokyo) - DevAPAC (Mumbai)APAC (Mumbai) - DevPoV (Proof of Value)
Timeline · 1 update
  1. resolved Apr 23, 2026, 03:57 PM UTC

    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.

Read the full incident report →

Notice March 11, 2026

Alation service degradation - Alation agent

Detected by Pingoru
Mar 11, 2026, 11:47 PM UTC
Resolved
Mar 12, 2026, 06:23 AM UTC
Duration
6h 35m
Affected: Americas (US-east)Americas (US-west)
Timeline · 2 updates
  1. monitoring Mar 11, 2026, 11:47 PM UTC

    A service interruption to Alation agent was encountered by some customers in the US-East-1 and US-West-2 regions. The service interruption has been remediated, and we are monitoring the status.

  2. resolved Mar 12, 2026, 06:23 AM UTC

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

Read the full incident report →

Minor February 2, 2026

Degraded Service - Alation.

Detected by Pingoru
Feb 02, 2026, 01:01 PM UTC
Resolved
Feb 02, 2026, 04:51 PM UTC
Duration
3h 49m
Affected: Americas (US-east)
Timeline · 5 updates
  1. investigating Feb 02, 2026, 02:01 PM UTC

    Alation service has recovered for most tenants and is operating normally. However, a limited number of tenants are still experiencing service disruption (login failures, timeouts, or degraded performance). Our engineering team is actively working with priority to restore service for the remaining affected tenants.

  2. identified Feb 02, 2026, 02:18 PM UTC

    Service has been restored for the majority of tenants. We have identified an issue affecting a small subset of tenants that are still experiencing errors and/or degraded performance. Targeted remediation is in progress to recover the remaining impacted tenants.

  3. identified Feb 02, 2026, 03:01 PM UTC

    Most tenants have recovered. A small subset of tenants still remains impacted; we’re continuing targeted remediation

  4. monitoring Feb 02, 2026, 03:24 PM UTC

    Service has been restored for the tenants that experienced failures. We are actively monitoring the infrastructure and application to validate expected behaviour.

  5. resolved Feb 02, 2026, 04:51 PM UTC

    Incident resolved. We’ll continue routine monitoring and will follow up if anything changes.”

Read the full incident report →

Notice October 21, 2025

Metadata extraction / QLI failures with BAD REQUEST HTTP response headers

Detected by Pingoru
Oct 21, 2025, 05:26 PM UTC
Resolved
Oct 21, 2025, 09:04 PM UTC
Duration
3h 38m
Affected: Americas (US-east) - DevAmericas (US-east)
Timeline · 3 updates
  1. investigating Oct 21, 2025, 05:26 PM UTC

    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.

  2. identified Oct 21, 2025, 06:35 PM UTC

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

  3. resolved Oct 21, 2025, 09:04 PM UTC

    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).

Read the full incident report →

Minor October 20, 2025

Service Degradation for EU Customers

Detected by Pingoru
Oct 20, 2025, 09:45 AM UTC
Resolved
Oct 20, 2025, 02:25 PM UTC
Duration
4h 39m
Affected: EMEA (Ireland)
Timeline · 3 updates
  1. identified Oct 20, 2025, 02:18 PM UTC

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

  2. identified Oct 20, 2025, 02:20 PM UTC

    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

  3. resolved Oct 20, 2025, 02:25 PM UTC

    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.

Read the full incident report →

Critical October 20, 2025

Third-party provider outage (AWS)

Detected by Pingoru
Oct 20, 2025, 07:40 AM UTC
Resolved
Oct 20, 2025, 10:00 AM UTC
Duration
2h 19m
Affected: Americas (US-east) - DevAmericas (US-east)
Timeline · 4 updates
  1. identified Oct 20, 2025, 08:07 AM UTC

    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.

  2. identified Oct 20, 2025, 09:52 AM UTC

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

  3. monitoring Oct 20, 2025, 09:54 AM UTC

    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.

  4. resolved Oct 20, 2025, 10:00 AM UTC

    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.

Read the full incident report →