Elevated errors and delays for Universal-3 Pro, Universal-3.5 Pro and Universal-3.6 Pro
minor- Started
- Nov 2, 4:42 PM EST
- Resolved
- Nov 2, 5:58 PM EST
- Duration
- 1h 16m
AssemblyAI's updates (5)
- identified · Nov 2, 4:42 PM EST
We've identified an issue causing a significant portion of pre-recorded transcription requests using Universal-3.5 Pro and Universal-3.6 Pro to fail or take longer than usual to complete, across all regions. Streaming is not affected. We've identified the cause and are rolling back a recent change, and we're beginning to see recovery.
- identified · Nov 2, 5:08 PM EST
Error rates are decreasing as our rollback progresses, and we're continuing to work on fully resolving the issue. Some requests may still fail or take longer than usual to complete.
- identified · Nov 2, 5:42 PM EST
We've applied a fix and error rates have dropped significantly. Some pre-recorded requests using Universal-3 Pro, Universal-3.5 Pro and Universal-3.6 Pro may still take longer than usual to complete while we work through the backlog.
- monitoring · Nov 2, 5:44 PM EST
Error rates and processing times have returned to normal. We're monitoring to make sure performance remains stable.
- resolved · Nov 2, 5:58 PM EST
We have continued to see good performance after the rollback, and error rates and processing times have remained in the normal ranges. We are now marking this issue as resolved. Any requests that returned an error during this incident can be safely resubmitted.
What our checks recorded
We checked AssemblyAI 15 times from AssemblyAI's start time to its resolution, once every five minutes. Every one of them reached AssemblyAI's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 171 ms, against 193 ms over the 24 hours before. AssemblyAI posted the incident at Nov 2, 4:42 PM EST.
Updates are AssemblyAI's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗