AssemblyAI is up and running. AssemblyAI provides speech-to-text and audio intelligence APIs.
Worked out from the incidents AssemblyAI reported, so it is an estimate and not a measurement.
Last incident: “Increased Processing Times and Errors on EU Endpoint for Universal-3 Pro Async model”, 17 days ago.
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.
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 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.
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.
Processing times have continued to be in the normal range, so we are now marking this issue as resolved.
AssemblyAI’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident AssemblyAI reported was “Increased Processing Times and Errors on EU Endpoint for Universal-3 Pro Async model”, 17 days ago (2026-10-06 15:44 UTC). None of its incidents in the last 90 days were a full outage.
AssemblyAI reports 16 components on its status page, including Asynchronous API, Transcription Queue, Container Registry, Website, Streaming API. Each is checked again whenever this page refreshes.
Retry with exponential backoff, fall back to another model or provider if your product allows it, and avoid hammering the API while it recovers.
AssemblyAI lists the Streaming API, the Asynchronous API and the Transcription Queue as separate components — realtime can fail while queued jobs still complete.
Not necessarily — LLM Gateway is its own component separate from the transcription pipeline. Check its row specifically.
If the status above is operational but AssemblyAI still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.