Anam incident

Session start failures in the US region

Minor Resolved View vendor source →

Anam experienced a minor incident on August 28, 2026 affecting Persona sessions, lasting 31m. The incident has been resolved; the full update timeline is below.

Started
Aug 28, 2026, 07:31 PM UTC
Resolved
Aug 28, 2026, 08:02 PM UTC
Duration
31m
Detected by Pingoru
Aug 28, 2026, 07:31 PM UTC

Affected components

Persona sessions

Update timeline

  1. monitoring Aug 28, 2026, 07:31 PM UTC

    Status: Monitoring Between 18:29 and 19:05 UTC, session-start requests in the US region returned 503 Service Unavailable with a "No available engines" error. Session token creation was not affected, and sessions in the European region were unaffected throughout. The cause is an ongoing storage outage at our cloud provider in the US region, which our provider has confirmed and is actively working on. To reduce customer impact, we have temporarily redirected US traffic to our European region. Session starts have been succeeding since 19:05 UTC; customers in the US may notice slightly higher connection latency while the redirect is in place. We are monitoring closely and will restore US-region routing once our provider confirms the outage is resolved. Affected components Persona sessions (Partial outage)

  2. monitoring Aug 28, 2026, 07:36 PM UTC

    Status: Monitoring Session starts have been succeeding since 19:05 UTC; customers in the US may notice slightly higher connection latency while the redirect is in place Affected components Persona sessions (Degraded performance)

  3. resolved Aug 28, 2026, 08:02 PM UTC

    Status: Resolved Our cloud provider has confirmed the storage outage in the US region is resolved. We restored US-region routing at 19:58 UTC, and session starts in the US have been succeeding with normal connection latency since then. Affected components Persona sessions (Operational)