Session start failures in the US region

Summary

Session start failures in the US region

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.

• Started

  Aug 28, 2026 · 7:31 PM

• Resolved

  Aug 28, 2026 · 8:02 PM

• Duration

  31m

• Severity

  Major

• ◉

  Monitoring

  Aug 28 · 7:31 PM Anam

  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.

• ◉

  Monitoring

  Aug 28 · 7:36 PM Anam

  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

• ✓

  Resolved

  Aug 28 · 8:02 PM Anam

  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.