Anam Outage History
Anam is up right nowPingoru has recorded 3 incidents for Anam: 3 in the last 12 months and 3 in the last 90 days.
Incidents, newest first
Minor September 23, 2026 WebRTC sessions are failing to start 13m Persona sessions
Started Sep 23, 2026, 02:27 PM UTC· resolved Sep 23, 2026, 02:40 PM UTC
- investigating Sep 23, 2026, 02:27 PM UTC
We're investigating the size of the impact and the RC.
- identified Sep 23, 2026, 02:35 PM UTC
Sessions in EU and US currently failing to start. A fix is being deployed.
- monitoring Sep 23, 2026, 02:38 PM UTC
Fix has rolled out, EU and US sessions appear to be starting without issues again. We'll continue to monitor before sharing a post-mortem.
- resolved Sep 23, 2026, 02:40 PM UTC
Service is fully restored and new WebRTC sessions are succeeding. The cause was a misconfiguration in our traffic-routing layer that was inadvertently rolled out to our production and staging environments at the same time, disrupting request routing. Once we traced it to that change, we reverted it and confirmed recovery across the affected regions. To prevent a recurrence, we're strengthening our infrastructure rollout process so changes must be validated in staging before they can reach production.
- resolved Sep 23, 2026, 02:40 PM UTC
Service is fully restored and new WebRTC sessions are succeeding. The cause was a misconfiguration in our traffic-routing layer that was inadvertently rolled out to our production and staging environments at the same time, disrupting request routing. Once we traced it to that change, we reverted it and confirmed recovery across the affected regions. To prevent a recurrence, we're strengthening our infrastructure rollout process so changes must be validated in staging before they can reach production.
Minor September 23, 2026 Session failures in the US region 20m Persona sessions
Started Sep 23, 2026, 08:27 AM UTC· resolved Sep 23, 2026, 08:47 AM UTC
- investigating Sep 23, 2026, 08:27 AM UTC
We are investigating failures to start new sessions in our US region. Other regions are not affected.
- resolved Sep 23, 2026, 08:47 AM UTC
Service in the US region is restored and new sessions are succeeding. The cause was a misconfiguration of the high-availability mechanism of our US traffic-routing layer, which allowed both of its redundant instances to be taken offline at the same time during an automatic capacity scale-up. We corrected the configuration so the routing layer can no longer be displaced by scale-ups and applied the fix across all production regions.
- resolved Sep 23, 2026, 08:47 AM UTC
Service in the US region is restored and new sessions are succeeding. The cause was a misconfiguration of the high-availability mechanism of our US traffic-routing layer, which allowed both of its redundant instances to be taken offline at the same time during an automatic capacity scale-up. We corrected the configuration so the routing layer can no longer be displaced by scale-ups and applied the fix across all production regions.
Minor August 28, 2026 Session start failures in the US region 31m Persona sessions
Started Aug 28, 2026, 07:31 PM UTC· resolved Aug 28, 2026, 08:02 PM UTC
- monitoring Aug 28, 2026, 07:31 PM UTC
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, 2026, 07:36 PM UTC
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, 2026, 08:02 PM UTC
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.
- resolved Aug 28, 2026, 08:02 PM UTC
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.