- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Asynchronous API
- Down Index
- 44of 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 7h 10m it lasted.
Anything that failed between 2025-08-05 16:05 UTC and 2025-08-05 23:15 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
- investigating
We are currently investigating an issue with Slam-1 that is preventing the successful completion of transcription requests using the model. We will share additional information as it becomes available. Please note this issue is only affecting requests using Slam-1 as the `speech_model`. Universal is unaffected.
provider
- investigating
We are continuing to investigate the issues affecting Slam-1. Currently, all requests using Slam-1 as the `speech_model` are failing with a "Server error, developers have been alerted" error. Our team is working to resolve this issue as quickly as possible. Note: This issue is only affecting requests using Slam-1 as the `speech_model`. Changing the `speech_model` to Universal will allow requests to complete successfully. See this section of our documentation for more information on specifying a speech model: https://www.assemblyai.com/docs/speech-to-text/pre-recorded-audio/select-the-speech-model
provider
- monitoring
We have resolved the issue that was affecting Slam-1 and are now seeing requests being processed successfully. We will continue to monitor traffic to ensure good performance, but everything is working as expected at the moment.
provider
- identified
We are once again experiencing issues with Slam-1 where requests are failing with a "Server error, developers have been alerted" error. Note: This issue is only affecting requests using Slam-1 as the `speech_model`. Changing the `speech_model` to Universal will allow requests to complete successfully. See this section of our documentation for more information on specifying a speech model: https://www.assemblyai.com/docs/speech-to-text/pre-recorded-audio/select-the-speech-model
provider
- identified
We are seeing Slam-1 requests complete successfully once again, but we are still working to fully resolve the root cause of this issue.
provider
- identified
We are still seeing good performance with the Slam model and requests completing as expected, but we are still working to fully resolve the root cause to prevent issues in the future.
provider
- monitoring
We have continued to see good performance with no instances of increased errors over the last couple of hours ,but are continuing to monitor to ensure there are no further issues.
provider
- resolved
We have continued to see good performance for the last ~6 hours so we are marking this issue as resolved. To prevent future issues, we have made some improvements to allow Slam-1 to scale more effectively.
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-04a0dd1c94
Is AssemblyAI still down?
No, this incident was resolved 2025-08-05 23:15 UTC. For AssemblyAI's live state, see https://down.guide/assemblyai.
How long did it last?
7h 10m, from 2025-08-05 16:05 UTC to 2025-08-05 23:15 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.