outages.live
Live

AssemblyAI

AssemblyAI is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

12

Days with an incident

10

Median duration

28 min

Longest incident

1 h 18 min

Components

16

APIs

Asynchronous API Operational
90 days ago7 days with an incidentToday
Streaming API Operational
90 days ago3 days with an incidentToday
LLM Gateway Operational
90 days agoNo incidentsToday

AWS Cloud

Transcription Queue Operational
90 days agoNo incidentsToday
Container Registry Operational
90 days agoNo incidentsToday
Compute Instances Operational
90 days agoNo incidentsToday
Container Control Plane Operational
90 days agoNo incidentsToday
Load Balancers Operational
90 days agoNo incidentsToday
Database Operational
90 days agoNo incidentsToday
Usage Statistics Database Operational
90 days agoNo incidentsToday
Object Storage Operational
90 days agoNo incidentsToday
Usage Statistics Bus Operational
90 days agoNo incidentsToday

Web

Website Operational
90 days agoNo incidentsToday
Playground Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days agoNo incidentsToday
Billing Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 28, 2026

Duration42 min18:11 to 18:53Real-time STT: 502 errors related to change to temporary tokensDegraded

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

Oct 6, 2026

Duration19 min15:44 to 16:03Increased Processing Times and Errors on EU Endpoint for Universal-3 Pro Async modelDegraded

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.

Duration25 min14:00 to 14:25Increased Processing Times and Errors on US Endpoint for Universal-3.5 Pro Async modelPartial outage

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.

Duration1 min10:30 to 10:30Rejected Sessions on US Endpoint for Universal-3.6 Pro Realtime ModelDegraded

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.

Oct 5, 2026

Duration1 h 18 min10:21 to 11:39Increased processing times and errors for Universal-3.5 Pro on the EU async endpointPartial outage

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.

Sep 28, 2026

Duration31 min17:27 to 17:58Increased turnaround times for Async Universal-3 modelDegraded

Processing times have continued to be in the normal range, so we are now marking this issue as resolved.

Sep 16, 2026

Duration1 h 15 min20:22 to 21:37Outage on US Async EndpointMajor outage

**Summary** On September 16, 2026, between 20:04 and 21:08 UTC, our US Async API returned elevated server errors. At peak, roughly 50% of async transcription requests on the US endpoint failed, and a portion of the requests that did succeed took longer than usual to complete. Our EU endpoint and real-time/streaming services were not affected. **Root cause** The failure originated in AWS SQS, the managed queuing service our transcription pipeline uses to distribute work. Specifically, the Fair Queues feature began rejecting valid messages with an `InvalidParameterValue` error on a parameter our services had been sending successfully for months. There was no deploy or infrastructure change on our side that triggered this; AWS confirmed it as a service-side issue and rolled back the change on their end later that evening. Because the affected queues sit in the path between our API and our transcription workers, requests that could not be queued failed outright, and a portion of the work t

Aug 25, 2026

Duration6 min14:55 to 15:01Increased latency for Universal 3.5 Pro Realtime modelDegraded

This incident has been resolved. From 14:15-14:45 UTC customers experienced increased latency when using our Universal 3.5 Pro Realtime model on the US endpoint. The EU endpoint was not affected. Sessions continued to function during this time without any errors.

Aug 20, 2026

Duration49 min14:21 to 15:10Async Transcription Service IssuesDegraded

This incident has been resolved. Between approximately 13:40 and 14:40 UTC, asynchronous transcription requests on our US endpoint experienced elevated latency and errors. Processing times and error rates have returned to normal ranges and the backlog has cleared.

Aug 19, 2026

Duration7 min13:17 to 13:24EU endpoint session failures on Universal 3.5 Pro RealtimePartial outage

This incident has been resolved. From 13:00–13:12 UTC, users creating new streaming sessions using the EU endpoint were receiving a 3005 close code.

Aug 18, 2026

Duration38 min19:34 to 20:12Elevated processing times for Universal-3 Pro and Universal-3.5 Pro async transcriptionDegraded

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.

Aug 14, 2026

Duration20 min14:49 to 15:09Delayed Webhook Delivery on Async EU EndpointDegraded

This incident has been resolved. The affected webhook events remained queued and were delivered after service recovered; no events were lost. The queue is now clear, and no customer action is required.

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=assemblyai
Slack
/feed subscribe https://outages.live/feed.xml?providers=assemblyai

Go from tracking outages to fixing production issues with Polylane.

Try Polylane