AssemblyAI: Delayed processing of transcripts on Slam

Impact: majorStatus: resolvedStarted 2025-11-20 08:21 UTCResolved 2025-11-20 09:41 UTC (1.3 h)4 updatesSource: stspg.io

Summary

AssemblyAI reported a major degradation affecting Slam-1 in us-west-2: transcripts queued or errored; Universal was unaffected. The incident record started at 2025-11-20 08:21 UTC, though the vendor said delays began at 5:43 UTC. A fix restored normal processing at 08:47 UTC; resolution was confirmed at 09:41 UTC, with a recorded duration of 1 h 20 min.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: APIs - Asynchronous APIAsynchronous API

Timeline of updates

investigating2025-11-20 08:21 UTC
We are currently investigating an issue where there has been delayed processing of transcripts on Slam-1, specifically in our us-west-2 region. This began at 5:43 UTC. Customers will experience queueing or erroring of transcripts when using our Slam-1 model. Our Universal model is not affected by this incident.
identified2025-11-20 08:26 UTC
The issue has been identified and a fix is being implemented.
monitoring2025-11-20 08:47 UTC
A fix has been implemented and our team is monitoring the results. Slam-1 has resumed normal processing.
resolved2025-11-20 09:41 UTC
This incident has been resolved.

Rewindex changes for this incident

Major incident: Delayed processing of transcripts on Slam 2025-11-20 08:21 UTC

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). AssemblyAI profile · Recent AssemblyAI incidents · Markdown · JSON