AssemblyAI Outage History
AssemblyAI is up right nowPingoru has recorded 51 incidents for AssemblyAI: 40 in the last 12 months and 14 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 3 | 3 of 720 (0%) |
| May 2026 | 4 | 9 of 744 (1%) |
| June 2026 | 2 | 3 of 720 (0%) |
| July 2026 | 3 | 3 of 744 (0%) |
| August 2026 | 6 | 4 of 744 (1%) |
| September 2026 | 3 | 2 of 720 (0%) |
| October 2026 | 4 | 2 of 536 (0%) |
Incidents, newest first
Minor October 6, 2026 Increased Processing Times and Errors on EU Endpoint for Universal-3 Pro Async model 19m Asynchronous API
Started Oct 06, 2026, 03:44 PM UTC· resolved Oct 06, 2026, 04:03 PM UTC
- investigating Oct 06, 2026, 03:44 PM UTC
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.
- identified Oct 06, 2026, 03:44 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 06, 2026, 03:46 PM UTC
A fix has been implemented. We are seeing processing times return to the normal ranges and are continuing to monitor the results.
- resolved Oct 06, 2026, 04:03 PM 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.
Major October 6, 2026 Increased Processing Times and Errors on US Endpoint for Universal-3.5 Pro Async model 25m Asynchronous API
Started Oct 06, 2026, 02:00 PM UTC· resolved Oct 06, 2026, 02:25 PM UTC
- investigating Oct 06, 2026, 02:00 PM 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.
- identified Oct 06, 2026, 02:10 PM UTC
We have identified the issue and a fix has been released. We will provide further updates as soon as we can.
- monitoring Oct 06, 2026, 02:13 PM UTC
A fix has been implemented. We are seeing processing times return to the normal ranges and are continuing to monitor the results.
- resolved Oct 06, 2026, 02:25 PM 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.
Minor October 6, 2026 Rejected Sessions on US Endpoint for Universal-3.6 Pro Realtime Model –
Started Oct 06, 2026, 10:30 AM UTC· resolved Oct 06, 2026, 10:30 AM UTC
- resolved Oct 06, 2026, 01:04 PM 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. 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.
Major October 5, 2026 Increased processing times and errors for Universal-3.5 Pro on the EU async endpoint 1h 18m Asynchronous API
Started Oct 05, 2026, 10:21 AM UTC· resolved Oct 05, 2026, 11:39 AM UTC
- investigating Oct 05, 2026, 10:21 AM 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.
- identified Oct 05, 2026, 10:38 AM 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.
- monitoring Oct 05, 2026, 10:43 AM 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.
- resolved Oct 05, 2026, 11:39 AM 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.
Minor September 28, 2026 Increased turnaround times for Async Universal-3 model 30m Asynchronous API
Started Sep 28, 2026, 05:27 PM UTC· resolved Sep 28, 2026, 05:58 PM UTC
- identified Sep 28, 2026, 05:27 PM 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.
- identified Sep 28, 2026, 05:38 PM UTC
We are still working to fully resolve the issue, but we are seeing improvement in turnaround times for the Universal-3 Pro models.
- monitoring Sep 28, 2026, 05:44 PM 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.
- resolved Sep 28, 2026, 05:58 PM UTC
Processing times have continued to be in the normal range, so we are now marking this issue as resolved.
Critical September 16, 2026 Outage on US Async Endpoint 1h 14m Asynchronous API
Started Sep 16, 2026, 08:22 PM UTC· resolved Sep 16, 2026, 09:37 PM UTC
- investigating Sep 16, 2026, 08:22 PM 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.
- identified Sep 16, 2026, 08:24 PM UTC
The issue has been identified and our team released fix. This is affecting approximately 50% of all async transcriptions. Success rate is beginning to improve.
- identified Sep 16, 2026, 08:57 PM UTC
We are continuing to investigate these elevated errors. We will provide an update as soon as possible.
- identified Sep 16, 2026, 09:10 PM UTC
We are seeing a reduction in the number of errors, but we are still working to fully resolve the issue.
- monitoring Sep 16, 2026, 09:12 PM UTC
A fix has been released and we are continuing to monitor the situation. Our Async API service is recovering.
- resolved Sep 16, 2026, 09:37 PM UTC
This incident has been resolved. Service on our Async API has returned to normal.
- postmortem Sep 21, 2026, 08:38 PM 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 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 that did get through was delayed behind reduced throughput. We mitigated by disabling Fair Queues across our services and reverting to standard SQS queues, which restored normal operation roughly an hour after the first error. **What we're doing about it** * **Faster configuration changes.** Much of our service configuration lives in environment variables, which require task restarts to propagate. We are moving this to a global feature flag system so mitigations like this one take seconds rather than minutes. * **A single, unified kill switch.** Disabling the affected feature required toggling it service by service. We are consolidating this into one control. * **Expedited emergency deploys.** We are adding a reviewed break-glass path so urgent fixes can bypass non-essential CI steps. * **Multi-region failover.** We are prioritizing work to fail the US pipeline over to a second region when a regional provider dependency degrades, rather than relying on feature-level mitigations alone. We're sorry for the disruption. No customer audio or transcript data was lost, and any requests that failed during this window can be safely resubmitted.
Notice September 13, 2026 Elevated turnaround times for async transcription 7m
Started Sep 13, 2026, 11:30 PM UTC· resolved Sep 13, 2026, 11:37 PM UTC
- resolved Sep 14, 2026, 01:27 AM 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.
Minor August 25, 2026 Increased latency for Universal 3.5 Pro Realtime model 6m Streaming API
Started Aug 25, 2026, 02:55 PM UTC· resolved Aug 25, 2026, 03:01 PM UTC
- investigating Aug 25, 2026, 02:55 PM 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 3:15pm UTC.
- identified Aug 25, 2026, 02:57 PM UTC
The issue has been identified and our team is working on a fix.
- monitoring Aug 25, 2026, 02:57 PM UTC
The fix has been implemented and latency has recovered as of 3:45pm UTC. The team is continuing to monitor the situation.
- resolved Aug 25, 2026, 03:01 PM UTC
This incident has been resolved. From 3:15p-3:45p 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.
Minor August 20, 2026 Async Transcription Service Issues 49m Asynchronous API
Started Aug 20, 2026, 02:21 PM UTC· resolved Aug 20, 2026, 03:10 PM UTC
- investigating Aug 20, 2026, 02:21 PM 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.
- identified Aug 20, 2026, 02:25 PM 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.
- monitoring Aug 20, 2026, 02:39 PM UTC
A fix has been implemented and we are monitoring recovery.
- resolved Aug 20, 2026, 03:10 PM 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.
Major August 19, 2026 EU endpoint session failures on Universal 3.5 Pro Realtime 7m Streaming API
Started Aug 19, 2026, 01:17 PM UTC· resolved Aug 19, 2026, 01:24 PM UTC
- investigating Aug 19, 2026, 01:17 PM 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.
- identified Aug 19, 2026, 01:17 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 19, 2026, 01:18 PM UTC
A fix has been implemented and our team is monitoring the results. Users can now create new realtime sessions successfully.
- monitoring Aug 19, 2026, 01:20 PM UTC
We are continuing to monitor for any further issues.
- resolved Aug 19, 2026, 01:24 PM UTC
This incident has been resolved.
Minor August 18, 2026 Elevated processing times for Universal-3 Pro and Universal-3.5 Pro async transcription 38m Asynchronous API
Started Aug 18, 2026, 07:34 PM UTC· resolved Aug 18, 2026, 08:12 PM UTC
- investigating Aug 18, 2026, 07:34 PM 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.
- identified Aug 18, 2026, 07:46 PM 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.
- monitoring Aug 18, 2026, 07:55 PM 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.
- resolved Aug 18, 2026, 08:12 PM 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.
Minor August 14, 2026 Delayed Webhook Delivery on Async EU Endpoint 20m Asynchronous API
Started Aug 14, 2026, 02:49 PM UTC· resolved Aug 14, 2026, 03:09 PM UTC
- investigating Aug 14, 2026, 02:49 PM 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.
- identified Aug 14, 2026, 02:59 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 14, 2026, 03:03 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 14, 2026, 03:09 PM UTC
This incident has been resolved.
Minor August 3, 2026 503 Error when using temp tokens with Realtime API 1h 47m Streaming API
Started Aug 03, 2026, 04:08 PM UTC· resolved Aug 03, 2026, 05:56 PM UTC
- investigating Aug 03, 2026, 04:08 PM UTC
We are currently investigating an issue where users on our us-east-1 endpoint are experiencing 503 errors when using temporary tokens with our Realtime API.
- identified Aug 03, 2026, 04:11 PM UTC
Our team has identified the issue and a fix is being released.
- identified Aug 03, 2026, 04:33 PM UTC
We are continuing to work on a fix for the issue. The API is stable and the errors subsided at 5:11pm UTC.
- monitoring Aug 03, 2026, 04:37 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 03, 2026, 05:56 PM UTC
This incident has been resolved.
Notice July 31, 2026 Degraded Universal-3.5 Pro streaming in us-east 2h 15m
Started Jul 31, 2026, 08:00 PM UTC· resolved Jul 31, 2026, 10:15 PM UTC
- resolved Aug 01, 2026, 04:57 PM UTC
This incident affected a subset of Universal-3.5 Pro streaming sessions in the us-east region on July 31 between 20:15 and 22:15 UTC. Affected sessions connected successfully but did not process incoming audio, so no transcript was returned while the connection remained open. Other regions, other streaming models, and our asynchronous API were unaffected. We apologize for the disruption to your workflows. If you have any questions, please reach out to [email protected].
Minor July 9, 2026 Increased processing times for US async transcription 19m Asynchronous API
Started Jul 09, 2026, 01:53 PM UTC· resolved Jul 09, 2026, 02:12 PM UTC
- investigating Jul 09, 2026, 01:53 PM UTC
We are seeing increased processing times for pre-recorded (async) transcriptions on the US endpoint. Webhook deliveries may also be delayed. We are currently investigating.
- identified Jul 09, 2026, 01:59 PM UTC
We have identified the issue causing elevated processing times for async transcriptions on the US endpoint and have addressed the root cause. The system is recovering, but processing times remain elevated while the backlog clears. Webhook deliveries may also continue to be delayed.
- monitoring Jul 09, 2026, 02:10 PM UTC
We have been monitoring the queue drain and transcription pickup delays caused by the backlog. Processing times are returning to normal ranges on the US endpoint and the backlog has cleared. We are continuing to monitor.
- resolved Jul 09, 2026, 02:12 PM UTC
This incident has been resolved. Async transcription processing times on the US endpoint have returned to normal ranges and webhook deliveries are operating normally.
Notice July 7, 2026 Degraded streaming session creation for Universal Streaming English in us-west 10m
Started Jul 07, 2026, 03:00 PM UTC· resolved Jul 07, 2026, 03:10 PM UTC
- resolved Jul 16, 2026, 11:45 PM UTC
Incident window: July 7, 2026, 15:00 to 15:10 UTC During this window, newly created Universal Streaming English sessions in the us-west region were degraded. Affected sessions were cancelled with error code 3005 shortly after connecting and did not return transcripts. Sessions already in progress, other regions, other streaming models, and all other services were unaffected. The cause was insufficient compute capacity after a scaling schedule failed to execute ahead of a traffic spike. Capacity recovered at 15:10 UTC and service returned to normal. Sessions affected during this window can be re-submitted and will process normally. If you have any questions, please reach out to [email protected].
Major June 25, 2026 Timeout on transcriptions using speaker labels 1h 10m Asynchronous API
Started Jun 25, 2026, 03:37 PM UTC· resolved Jun 25, 2026, 04:48 PM UTC
- investigating Jun 25, 2026, 03:37 PM UTC
We are currently investigating an issue with async transcriptions on the US endpoint that use speaker labels. This is resulting in timeouts for all transcriptions with speaker labels enabled for files under 5 minutes long.
- identified Jun 25, 2026, 03:38 PM UTC
The issue has been identified and a fix has been released.
- monitoring Jun 25, 2026, 04:00 PM UTC
A fix has been implemented and our API is slowly beginning to recover normal processing.
- monitoring Jun 25, 2026, 04:14 PM UTC
The root cause has been addressed and our system is slowly working through the transcript backlog, which is causing slower processing on our US async endpoint.
- monitoring Jun 25, 2026, 04:27 PM UTC
Our API is continuing to recover and incoming transcriptions are returning to normal processing. We are continuing to monitor the situation.
- resolved Jun 25, 2026, 04:48 PM UTC
This incident has been resolved.
- postmortem Jun 25, 2026, 06:02 PM UTC
**What happened** An issue related to our speaker diarization service caused certain requests to hang until they timed out. This lead to a backlog of requests to our async API creating a processing queue across our US transcription pipeline, which slowed and timed out transcription requests more broadly, including requests that were not using speaker diarization. --- **When** Impact ran from approximately 15:00 to 16:25 UTC on June 25, 2026 \(about 1 hour 25 minutes\). The most severe disruption was in the first 45 minutes \(15:00–15:45 UTC\); remaining delays and timeouts cleared shortly after. Full recovery was confirmed by ≈16:40 UTC. --- **What services were affected** On our US async API endpoint transcription requests during this window saw processing delays and timeouts. Our EU async API endpoint was not affected and operated normally throughout.
Critical June 24, 2026 Pre-recorded Universal-3-pro and Universal-3-5-pro degradation in the EU 1h 26m Asynchronous API
Started Jun 24, 2026, 09:13 AM UTC· resolved Jun 24, 2026, 10:40 AM UTC
- investigating Jun 24, 2026, 09:13 AM UTC
We are currently investigating degradations affecting only traffic to the EU versions of Universal-3Pro and Universal-3-5-pro for pre-recorded audio transcription.
- identified Jun 24, 2026, 09:34 AM UTC
Our engineering team has identified the issue and is actively working to implement a fix. We will continue to provide updates as more information becomes available.
- monitoring Jun 24, 2026, 10:16 AM UTC
A fix has been implemented and requests to the EU versions of Universal-3-Pro and Universal-3-5-Pro no longer show degradations. We are continuing to monitor to ensure stability.
- resolved Jun 24, 2026, 10:40 AM UTC
The issue affecting EU pre-recorded transcription for Universal-3-Pro and Universal-3-5-Pro has been fully resolved, the fix was implemented at 10:05 UTC. All systems are operating normally. We apologize for the disruption to your workflows. If you have any questions, please reach out to [email protected].
Minor May 27, 2026 Degraded New Account Signup and Account Provisioning 1h 13m Dashboard
Started May 27, 2026, 09:00 PM UTC· resolved May 27, 2026, 10:13 PM UTC
- investigating May 27, 2026, 09:00 PM UTC
We are currently experiencing degraded performance with new account signups and provisioning due to an upstream issue with our billing provider. Existing accounts and API usage are unaffected. New users may experience errors or delays when creating an account. Our team is actively working with our provider to resolve the issue and will provide updates as more information becomes available.
- monitoring May 27, 2026, 09:16 PM UTC
Account signups and upgrades have recovered and we are seeing successful new account creation. Our team is continuing to monitor and clean up a small number of affected accounts. We will provide a final update once fully resolved.
- resolved May 27, 2026, 10:13 PM UTC
Processes are continuing to work normally, and all affected accounts have been fixed, so we are not moving this issue to resolved.
Minor May 19, 2026 Increased processing times and errors for Async EU endpoint 4h 20m Asynchronous API
Started May 19, 2026, 11:08 AM UTC· resolved May 19, 2026, 03:28 PM UTC
- monitoring May 19, 2026, 11:08 AM UTC
A fix has been implemented and the EU endpoint is recovering. Processing times and error rates are stabilizing.
- resolved May 19, 2026, 03:28 PM UTC
This incident is resolved. To summarize, this incident began at 9am UTC and a fix was implemented around 10am UTC. This incident affected async requests to our EU endpoint and resulted in an increase in processing time and errors.
Notice May 19, 2026 Increased Processing Times for EU Endpoint –
Started May 19, 2026, 10:53 AM UTC· resolved May 19, 2026, 10:53 AM UTC
- resolved May 19, 2026, 10:56 AM UTC
Async transcription on the EU endpoint experienced elevated processing times due to a capacity constraint. The constraint has been addressed and processing times have returned to normal ranges.
Minor May 7, 2026 Billing Balance & Notification Delays 3h 8m Billing
Started May 07, 2026, 01:56 PM UTC· resolved May 07, 2026, 05:04 PM UTC
- investigating May 07, 2026, 01:56 PM UTC
We are currently investigating an issue affecting billing balance updates and notifications. Some customers may notice that their account balance is not reflecting the most up-to-date usage. Additionally, the following notifications may not be delivered as expected: - Low balance and $0 balance alerts - Autopay confirmation emails - Custom email alerts for usage spend and threshold notifications Our team is actively working to identify the root cause and restore normal functionality. We will provide updates as more information becomes available.
- identified May 07, 2026, 02:27 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 07, 2026, 04:34 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 07, 2026, 05:04 PM UTC
This incident has been resolved.
Minor April 16, 2026 Increased processing times and errors for Universal-2 47m Asynchronous API
Started Apr 16, 2026, 06:37 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- identified Apr 16, 2026, 06:37 PM UTC
We have identified an issue that is causing elevated processing times for requests that are using Universal-2 for pre-recorded audio. Most requests are still completing successfully, but we are also seeing a small increase in errors as a result of some requests timing out. Our team has identified the root cause of this issue and is working to resolve it as quickly as possible. Request using Universal-3 Pro are unaffected by this issue.
- monitoring Apr 16, 2026, 06:56 PM UTC
The root cause of the slowdown has been addressed and turnaround times have once again returned to the normal range. We will continue to monitor traffic going forward to ensure continued good performance.
- resolved Apr 16, 2026, 07:24 PM UTC
We have continued to see processing times remain in the normal range and are now marking this issue as resolved.
Major April 9, 2026 Degraded Async Transcription Performance 15m Asynchronous API, Transcription Queue
Started Apr 09, 2026, 09:33 PM UTC· resolved Apr 09, 2026, 09:49 PM UTC
- identified Apr 09, 2026, 09:33 PM UTC
We are currently experiencing degraded async transcription performance. Some customers may see increased processing times or throttled requests. Our engineering team has identified the issue and is actively working to restore full capacity. We will continue to provide updates as more information becomes available.
- monitoring Apr 09, 2026, 09:40 PM UTC
The capacity constraint has been addressed and the transcription queue is actively clearing. Processing times should return to normal within the next few minutes. We are continuing to monitor to ensure stability.
- resolved Apr 09, 2026, 09:49 PM UTC
The issue affecting async transcription processing has been fully resolved. All systems are operating normally. We apologize for the disruption to your workflows. If you have any questions, please reach out to [email protected].
Notice April 6, 2026 Pre-recorded STT requests that include Content Moderation failing 1h 52m
Started Apr 06, 2026, 06:14 PM UTC· resolved Apr 06, 2026, 08:06 PM UTC
- resolved Apr 06, 2026, 09:51 PM UTC
Resolved – Content Safety Errors | April 6, 2026 Incident Window: 18:14 – 20:06 UTC Current Status: Resolved ✅ On April 6, 2026, during the incident window, customers using our Content Safety feature for Pre-recorded STT experienced errors for their requests. What happened: A configuration change inadvertently prevented our systems from processing Content Safety requests. This caused all Content Safety-enabled transcription jobs for Pre-recorded STT to fail during the affected period. Who was affected: Customers with the Content Safety feature enabled who submitted Pre-recorded STT requests between 18:14 and 20:06 UTC. What we did: Our team detected the issue and reverted the configuration change, fully restoring Content Safety functionality by 20:06 UTC. We sincerely apologize for the impact this had on your workflows. If you have any questions, please contact our team at [email protected], and we'll be happy to assist.