Skip to main content
AssemblyAI

Longer than usual processing times for transcription of pre-recorded audio

Degraded Lasted 0m · started · AssemblyAI's page

Level
confirmed
Worst impact
Degraded
Components
Asynchronous API
Down Index
20of 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 0m it lasted.

    Anything that failed between 2026-03-06 19:04 UTC and 2026-03-06 19:04 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 1

  1. resolved

    From approximately 10:10am to 10:28am PT we experienced longer-than-usual processing times for transcription of pre-recorded audio. The root cause of this slowdown has been identified and resolved, and response times are back within normal ranges. Our team will continue to monitor traffic to ensure continued good performance.

    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-15894cbe9e

Is AssemblyAI still down?

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

How long did it last?

0m, from 2026-03-06 19:04 UTC to 2026-03-06 19:04 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.