Is AssemblyAI down right now?
No, it is up
Operational · All Systems Operational
Components
- APIs · Asynchronous APIOperational
- AWS Cloud · Transcription QueueOperational
- AWS Cloud · Container RegistryOperational
- Web · WebsiteOperational
- APIs · Streaming APIOperational
- AWS Cloud · Compute InstancesOperational
- Web · PlaygroundOperational
- BillingOperational
- AWS Cloud · Container Control PlaneOperational
- Web · DashboardOperational
- APIs · LLM GatewayOperational
- AWS Cloud · Load BalancersOperational
- AWS Cloud · DatabaseOperational
- AWS Cloud · Usage Statistics DatabaseOperational
- AWS Cloud · Object StorageOperational
- AWS Cloud · Usage Statistics BusOperational
User reports
Having trouble with AssemblyAI? Reports are anonymous and only counted, no cookies.
AssemblyAI uptime, last 90 days
Each bar is one UTC day, coloured by the worst state we saw on the official status page.
Recent AssemblyAI incidents
Elevated errors and delays for Universal-3 Pro, Universal-3.5 Pro and Universal-3.6 Pro · 2 Nov 2026, 21:42 UTC · 1 h 16 min · minor
resolved · 2 Nov 2026, 22:58 UTC
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.
monitoring · 2 Nov 2026, 22:44 UTC
Error rates and processing times have returned to normal. We're monitoring to make sure performance remains stable.
identified · 2 Nov 2026, 22:42 UTC
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.
identified · 2 Nov 2026, 22:08 UTC
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 · 2 Nov 2026, 21:42 UTC
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.
Real-time STT: 502 errors related to change to temporary tokens · 28 Oct 2026, 18:11 UTC · 42 min · minor
resolved · 28 Oct 2026, 18:53 UTC
We have continued to see good performance after the rollback and are now marking this issue as resolved.
monitoring · 28 Oct 2026, 18:21 UTC
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.
identified · 28 Oct 2026, 18:11 UTC
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.
Increased Processing Times and Errors on EU Endpoint for Universal-3 Pro Async model · 6 Oct 2026, 15:44 UTC · 19 min · minor
resolved · 6 Oct 2026, 16:03 UTC
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.
monitoring · 6 Oct 2026, 15:46 UTC
A fix has been implemented. We are seeing processing times return to the normal ranges and are continuing to monitor the results.
identified · 6 Oct 2026, 15:44 UTC
The issue has been identified and a fix is being implemented.
investigating · 6 Oct 2026, 15:44 UTC
We are experiencing 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.
Increased Processing Times and Errors on US Endpoint for Universal-3.5 Pro Async model · 6 Oct 2026, 14:00 UTC · 25 min · major
resolved · 6 Oct 2026, 14:25 UTC
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.
monitoring · 6 Oct 2026, 14:13 UTC
A fix has been implemented. We are seeing processing times return to the normal ranges and are continuing to monitor the results.
identified · 6 Oct 2026, 14:10 UTC
We have identified the issue and a fix has been released. We will provide further updates as soon as we can.
investigating · 6 Oct 2026, 14:00 UTC
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.
Rejected Sessions on US Endpoint for Universal-3.6 Pro Realtime Model · 6 Oct 2026, 10:30 UTC · minor
resolved · 6 Oct 2026, 10:30 UTC
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.
Increased processing times and errors for Universal-3.5 Pro on the EU async endpoint · 5 Oct 2026, 10:21 UTC · 1 h 18 min · major
resolved · 5 Oct 2026, 11:39 UTC
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.
monitoring · 5 Oct 2026, 10:43 UTC
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.
identified · 5 Oct 2026, 10:38 UTC
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.
investigating · 5 Oct 2026, 10:21 UTC
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.
Increased turnaround times for Async Universal-3 model · 28 Sept 2026, 17:27 UTC · 31 min · minor
resolved · 28 Sept 2026, 17:58 UTC
Processing times have continued to be in the normal range, so we are now marking this issue as resolved.
monitoring · 28 Sept 2026, 17:44 UTC
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.
identified · 28 Sept 2026, 17:38 UTC
We are still working to fully resolve the issue, but we are seeing improvement in turnaround times for the Universal-3 Pro models.
identified · 28 Sept 2026, 17:27 UTC
We are currently experiencing issues that are resulting in longer-than-usual processing times for Async STT requests using our Universal-3 models. We are working to resolve this issue as quickly as possible and will provide further updates as soon as we can.
Outage on US Async Endpoint · 16 Sept 2026, 20:22 UTC · 1 h 15 min · critical
postmortem · 21 Sept 2026, 20:38 UTC
**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…
resolved · 16 Sept 2026, 21:37 UTC
The issue, which was the result of an AWS service issue, has been resolved and we have continue to see good performance since implementing a fix so we are now closing this issue.
monitoring · 16 Sept 2026, 21:12 UTC
We have mitigated the issue and our Async API service is recovering.
identified · 16 Sept 2026, 21:10 UTC
We are seeing a reduction in the number of errors, but we are still working to fully resolve the issue.
identified · 16 Sept 2026, 20:57 UTC
We are continuing to investigate these elevated errors. We will provide an update as soon as possible.
identified · 16 Sept 2026, 20:24 UTC
The issue has been identified. This is affecting approximately 50% of all async transcriptions on the US endpoint.
investigating · 16 Sept 2026, 20:22 UTC
We are currently investigating an issue that is affecting all customers using our Async API on our US endpoint. Users will be receiving a server error. We will update with more information as we learn more. This began at 8pm UTC.
Elevated turnaround times for async transcription · 14 Sept 2026, 01:27 UTC
resolved · 13 Sept 2026, 23:30 UTC
Resolved: Between 23:30 and 23:37 UTC on September 13, 2026, async transcription requests experienced elevated turnaround times due to an unexpected spike in processing load. We scaled out additional capacity and turnaround times returned to normal levels. Requests submitted during this window were processed, with some taking longer than usual to complete.
Increased latency for Universal 3.5 Pro Realtime model · 25 Aug 2026, 14:55 UTC · 6 min · minor
resolved · 25 Aug 2026, 15:01 UTC
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.
monitoring · 25 Aug 2026, 14:57 UTC
The fix has been implemented and latency has recovered as of 14:45 UTC. The team is continuing to monitor the situation.
identified · 25 Aug 2026, 14:57 UTC
The issue has been identified and our team is working on a fix.
investigating · 25 Aug 2026, 14:55 UTC
We are currently investigating an issue where there is increased latency for our Universal 3.5 Pro Realtime model on the US endpoint. This began at 14:15 UTC.
Async Transcription Service Issues · 20 Aug 2026, 14:21 UTC · 49 min · minor
resolved · 20 Aug 2026, 15:10 UTC
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.
monitoring · 20 Aug 2026, 14:39 UTC
A fix has been implemented and we are monitoring recovery.
identified · 20 Aug 2026, 14:25 UTC
We have identified the cause of the elevated error rates affecting asynchronous transcription requests. Our engineering team is actively restoring capacity, and error rates should improve as this completes. We will continue to provide updates as more information becomes available.
investigating · 20 Aug 2026, 14:21 UTC
We’re seeing elevated latency and errors on async transcription submissions, and our on-call team is actively investigating. Capacity is scaling out now, and we’re monitoring recovery.
EU endpoint session failures on Universal 3.5 Pro Realtime · 19 Aug 2026, 13:17 UTC · 7 min · major
resolved · 19 Aug 2026, 13:24 UTC
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.
monitoring · 19 Aug 2026, 13:20 UTC
We are continuing to monitor for any further issues.
monitoring · 19 Aug 2026, 13:18 UTC
A fix has been implemented and our team is monitoring the results. Users can now create new realtime sessions successfully.
identified · 19 Aug 2026, 13:17 UTC
The issue has been identified and a fix is being implemented.
investigating · 19 Aug 2026, 13:17 UTC
We're currently investigating an issue affecting users on our Universal 3.5 Pro Realtime model, where new streaming sessions could not be created on our EU endpoint. This occurred from 13:00–13:12 UTC. Affected users are seeing a 3005 close code. Users on the US endpoint are unaffected.
Elevated processing times for Universal-3 Pro and Universal-3.5 Pro async transcription · 18 Aug 2026, 19:34 UTC · 38 min · minor
resolved · 18 Aug 2026, 20:12 UTC
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.
monitoring · 18 Aug 2026, 19:55 UTC
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.
identified · 18 Aug 2026, 19:46 UTC
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.
investigating · 18 Aug 2026, 19:34 UTC
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.
Delayed Webhook Delivery on Async EU Endpoint · 14 Aug 2026, 14:49 UTC · 20 min · minor
resolved · 14 Aug 2026, 15:09 UTC
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.
monitoring · 14 Aug 2026, 15:03 UTC
A fix has been implemented and we are monitoring the results.
identified · 14 Aug 2026, 14:59 UTC
The issue has been identified and a fix is being implemented.
investigating · 14 Aug 2026, 14:49 UTC
We are currently investigating an issue that is affecting webhook delivery on our Async EU Endpoint. This began at 2:30p UTC. Customers are receiving delayed webhook deliveries on the EU endpoint. This does not affect customers using webhooks on our US endpoint.
AssemblyAI is listed under Model makers. Status data comes from the official status page and is checked every 5 minutes.All AI service statuses