Elevated processing times for Universal-3 Pro and Universal-3.5 Pro async transcription
This incident has been resolved. Processing times for pre-recorded transcription requests using Universal-3 Pro and Universal-3.5 Pro have returned to normal ranges and the backlog has cleared.
The latest update from AssemblyAI.
State
Resolved
Started
75 d ago
2026-08-18 19:34 UTC
Lasted
38 min
until 2026-08-18 20:12 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
13 min 33%
Identified
8 min 21%
Monitoring
18 min 46%
Updates
Times in UTCAs posted by AssemblyAI
This incident has been resolved. Processing times for pre-recorded transcription requests using Universal-3 Pro and Universal-3.5 Pro have returned to normal ranges and the backlog has cleared.
Processing times for pre-recorded transcription requests using Universal-3 Pro and Universal-3.5 Pro are returning to normal ranges and the backlog has largely cleared. We are continuing to monitor to ensure stability.
We have identified the cause of the elevated processing times affecting pre-recorded transcription requests using Universal-3 Pro and Universal-3.5 Pro. Our engineering team has addressed a capacity constraint and is working to restore full capacity. Processing times will remain elevated while the backlog clears, and some customers may see requests queued or throttled. We will continue to provide updates as more information becomes available.
We're currently seeing longer than usual processing times for asynchronous transcription requests using Universal-3 Pro and Universal-3.5 Pro. Requests are being accepted and are completing, but time to completion is elevated while our queues work through a backlog.
Affected components
2AssemblyAI in the last 90 days
Full historyIncidents in 90 days
13
Days with an incident
10
Median duration
31 min
This incident
1.2× the median
Other AssemblyAI incidents
All incidentsAssemblyAI·Real-time STT: 502 errors related to change to temporary tokens
We have continued to see good performance after the rollback and are now marking this issue as resolved.
AssemblyAI·Increased Processing Times and Errors on EU Endpoint for Universal-3 Pro Async model
This incident has been resolved. Between approximately 15:05 and 15:45 UTC, async transcription requests using Universal-3 Pro on our EU endpoint took longer than usual to complete, and some requests failed. Processing times have returned to normal ranges and any requests that failed during this window can be safely resubmitted.
AssemblyAI·Increased Processing Times and Errors on US Endpoint for Universal-3.5 Pro Async model
This incident has been resolved. Between approximately 1:35p and 2:20p UTC, async transcription requests using Universal-3.5 Pro on our US endpoint took longer than usual to complete, and some requests failed. Processing times have returned to normal ranges and any requests that failed during this window can be safely resubmitted.
AssemblyAI·Rejected Sessions on US Endpoint for Universal-3.6 Pro Realtime Model
From 10:30a - 12:30a UTC users experienced rejected connections when connecting to our Realtime Universal-3.6 Pro model on our US endpoint. Users received a 3005 Session Cancelled error message on connection. This issue has been resolved and the Realtime US endpoint for Universal-3.6 Pro is functioning normally. The EU Realtime endpoint was not affected.
AssemblyAI·Increased processing times and errors for Universal-3.5 Pro on the EU async endpoint
This incident has been resolved. Between approximately 08:20 and 10:45 UTC, asynchronous transcription requests using Universal-3 Pro and Universal-3.5 Pro on our EU endpoint took longer than usual to complete, and some requests failed. Processing times have returned to normal ranges. Any requests that failed during this window can be safely resubmitted.
Follow AssemblyAI
Your coding agent knows when AssemblyAI is down, and tells you when a failure is theirs, not yours. You can also get AssemblyAI incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "assemblyai" and tell me if AssemblyAI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=assemblyai/feed subscribe https://outages.cc/feed.xml?providers=assemblyaiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane