Alation Cloud Service incident

Degraded Service - Alation.

Minor Resolved View vendor source →

Alation Cloud Service experienced a minor incident on February 2, 2026 affecting Americas (US-east), lasting 3h 49m. The incident has been resolved; the full update timeline is below.

Started
Feb 02, 2026, 01:01 PM UTC
Resolved
Feb 02, 2026, 04:51 PM UTC
Duration
3h 49m
Detected by Pingoru
Feb 02, 2026, 01:01 PM UTC

Affected components

Americas (US-east)

Update timeline

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