Is AssemblyAI down?

We have identified an issue with a recent change to temporary tokens that is causing some Real-time STT sessions that use temp tokens to fail with a 502 error. Our team is actively working to roll back this change.

We have completed the rollback and are now seeing a reduction of 502 errors. We will continue to monitor traffic to ensure that error rates continue to return to the normal range.

We have continued to see good performance after the rollback and are now marking this issue as resolved.

We have identified an issue affecting asynchronous transcription requests using Universal-3 Pro on our EU endpoint. Beginning at 15:05 UTC, requests have increased processing time and some are resulting in errors. Our team is working to restore normal processing. Our US endpoint is not affected. Our team is actively investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented. We are seeing processing times return to the normal ranges and are continuing to monitor the results.

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.

We have identified an issue affecting asynchronous transcription requests using Universal-3.5 Pro on our US endpoint. Beginning at 1:35p UTC requests have increased processing time and some are resulting in errors. Our team is working to restore normal processing. Our EU endpoint is not affected. We will continue to provide updates as more information becomes available.

We have identified the issue and a fix has been released. We will provide further updates as soon as we can.

A fix has been implemented. We are seeing processing times return to the normal ranges and are continuing to monitor the results.

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.

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

We have identified an issue affecting asynchronous transcription requests using Universal-3.5 Pro on our EU endpoint. Most of these requests are currently significantly delayed, and some have failed. Our team is working to restore normal processing. Our US endpoint and real-time services are not affected. We will continue to provide updates as more information becomes available.

We have identified the issue causing longer-than-usual processing times and some failed requests for asynchronous transcription using our Universal-3 Pro and Universal-3.5 Pro models on the EU endpoint. We are working to resolve this as quickly as possible and will provide further updates as soon as we can.

We have continued to work to resolve this issue and are now seeing processing times return to the normal ranges, but we are continuing to monitor to ensure good performance.

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.