Skip to main content
AssemblyAI

Timeout on transcriptions using speaker labels

Partial outage Lasted 1h 11m · started · AssemblyAI's page

Level
confirmed
Worst impact
Partial outage
Components
Asynchronous API
Regions
eu, us
Down Index
47of 100

What to do

  • Check whether you use AssemblyAI Asynchronous API in eu, us. 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 1h 11m it lasted.

    Anything that failed between 2026-06-25 15:37 UTC and 2026-06-25 16:48 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 7

  1. investigating

    We are currently investigating an issue with async transcriptions on the US endpoint that use speaker labels. This is resulting in timeouts for all transcriptions with speaker labels enabled for files under 2 minutes long. This began at 15:00 UTC.

    provider

  2. identified

    The issue has been identified and a fix has been released.

    provider

  3. monitoring

    A fix has been implemented and our API is slowly beginning to recover normal processing.

    provider

  4. monitoring

    The root cause has been addressed and our system is slowly working through the transcript backlog, which is causing slower processing on our US async endpoint.

    provider

  5. monitoring

    Our API is continuing to recover and incoming transcriptions are returning to normal processing. We are continuing to monitor the situation.

    provider

  6. resolved

    This incident has been resolved.

    provider

  7. postmortem

    **What happened** An issue related to our speaker diarization service caused certain requests to hang until they timed out. This lead to a backlog of requests to our async API creating a processing queue across our US transcription pipeline, which slowed and timed out transcription requests more broadly, including requests that were not using speaker diarization. --- **When** Impact ran from approximately 15:00 to 16:25 UTC on June 25, 2026 \(about 1 hour 25 minutes\). The most severe disruption was in the first 45 minutes \(15:00–15:45 UTC\); remaining delays and timeouts cleared shortly after. Full recovery was confirmed by ≈16:40 UTC. --- **What services were affected** On our US async API endpoint transcription requests during this window saw processing delays and timeouts. Our EU async API endpoint was not affected and operated normally throughout.

    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-c021796af4

Is AssemblyAI still down?

No, this incident was resolved 2026-06-25 16:48 UTC. For AssemblyAI's live state, see https://down.guide/assemblyai.

How long did it last?

1h 11m, from 2026-06-25 15:37 UTC to 2026-06-25 16:48 UTC, by the times AssemblyAI posted.

What was affected?

AssemblyAI named Asynchronous API in eu, us.

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.