Skip to main content
AssemblyAI

Degraded performance for requests using Slam-1

Degraded Lasted 6h 45m · started · AssemblyAI's page

Level
confirmed
Worst impact
Degraded
Components
Asynchronous API
Down Index
34of 100

What to do

  • Check whether you use AssemblyAI Asynchronous API. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 6h 45m it lasted.

    Anything that failed between 2025-10-30 19:36 UTC and 2025-10-31 02:21 UTC may need a replay.
  • Subscribe to AssemblyAI's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=assemblyai works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from AssemblyAI 8

  1. investigating

    We are currently investigating an issue that is leading to longer-than-usual processing times for pre-recorded audio transcriptions using the Slam-1 model. Requests using the Universal model, which is enabled by default, are not affected by this issue.

    provider

  2. identified

    Our team has identified the issue causing the delay in processing requests using Slam-1 and is actively working to resolve the issue.

    provider

  3. identified

    We are currently seeing some Slam-1 requests fail with a server error as we are restarting services while working to address this issue. We suggest holding off on retries for the time being or retrying those requests using Universal until normal processing has been restored. We will release another update here as soon as we are seeing an increase in success rates.

    provider

  4. identified

    We are starting to see success rates return to the normal range, but we are still working to ensure that the issue has been fully resolved.

    provider

  5. monitoring

    We are continuing to see success rates in the normal range and no longer than usual processing times but we will continue to monitor traffic to ensure continued good performance.

    provider

  6. identified

    We are once again seeing occasional issues where some requests using the Slam-1 model are taking longer than normal to process or failing with a server error. Retries are typically successful and requests using the Universal model are unaffected.

    provider

  7. monitoring

    Success rates and processing times have returned to the normal range, but we are monitoring traffic to ensure continued good performance.

    provider

  8. resolved

    We have continued to see good performance and success rates for Slam-1 and are now marking this issue as resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-ab1f8136f8

Is AssemblyAI still down?

No, this incident was resolved 2025-10-31 02:21 UTC. For AssemblyAI's live state, see https://down.guide/assemblyai.

How long did it last?

6h 45m, from 2025-10-30 19:36 UTC to 2025-10-31 02:21 UTC, by the times AssemblyAI posted.

What was affected?

AssemblyAI named Asynchronous API.

What caused it?

AssemblyAI hasn't published a root cause. If it does, it shows here.

Where does this come from?

AssemblyAI's official status page, https://status.assemblyai.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.