AssemblyAI Outage History

There were 9 AssemblyAI outages since February 9, 2026 totaling 16h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.assemblyai.com

Minor April 16, 2026

Increased processing times and errors for Universal-2

Detected by Pingoru: Apr 16, 2026, 06:37 PM UTC
Resolved: Apr 16, 2026, 07:24 PM UTC
Duration: 47m

Affected: Asynchronous API

Timeline · 3 updates

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.

Read the full incident report →

Major April 9, 2026

Degraded Async Transcription Performance

Detected by Pingoru: Apr 09, 2026, 09:33 PM UTC
Resolved: Apr 09, 2026, 09:49 PM UTC
Duration: 15m

Affected: Asynchronous APITranscription Queue

Timeline · 3 updates

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

Read the full incident report →

Notice April 6, 2026

Pre-recorded STT requests that include Content Moderation failing

Detected by Pingoru: Apr 06, 2026, 09:51 PM UTC
Resolved: Apr 06, 2026, 09:51 PM UTC
Duration: —

Timeline · 1 update

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.

Read the full incident report →

Minor March 30, 2026

Increase in error rates for Claude Sonnet 4.6

Detected by Pingoru: Mar 30, 2026, 06:41 PM UTC
Resolved: Mar 30, 2026, 11:55 PM UTC
Duration: 5h 13m

Affected: LLM Gateway

Timeline · 3 updates

identified Mar 30, 2026, 06:41 PM UTC

AWS Bedrock is currently experiencing issues that are leading to an increase in errors for Claude models. This increase in errors seems to be primarily with Sonnet 4.6, but could also affect other Claude models. We are working with their team to monitor the status of this issue and will provide additional updates as soon as we know more. LLM Gateway models from other providers are currently unaffected by this AWS Bedrock issue.
identified Mar 30, 2026, 09:54 PM UTC

The AWS Bedrock issues affecting some Claude models through LLM Gateway, mainly Sonnet 4.6, are still occurring, but the frequency of those errors has gone down. We are continuing to closely monitor the issue for a resolution.
resolved Mar 30, 2026, 11:55 PM UTC

The AWS Bedrock issues have been resolved, and we have once again seen success rates for Claude models, including Sonnet 4.6, return to normal levels.

Read the full incident report →

Minor March 6, 2026

Longer than usual processing times for transcription of pre-recorded audio

Detected by Pingoru: Mar 06, 2026, 07:04 PM UTC
Resolved: Mar 06, 2026, 07:04 PM UTC
Duration: —

Affected: Asynchronous API

Timeline · 1 update

resolved Mar 06, 2026, 07:04 PM UTC

From approximately 10:10am to 10:28am PT we experienced longer-than-usual processing times for transcription of pre-recorded audio. The root cause of this slowdown has been identified and resolved, and response times are back within normal ranges. Our team will continue to monitor traffic to ensure continued good performance.

Read the full incident report →

Minor February 28, 2026

Billing Issue Affecting Some Universal-3-Pro Users

Detected by Pingoru: Feb 28, 2026, 07:19 PM UTC
Resolved: Feb 28, 2026, 08:44 PM UTC
Duration: 1h 24m

Affected: Billing

Timeline · 2 updates

investigating Feb 28, 2026, 07:19 PM UTC

We are aware of an issue that caused unexpected multiple auto-refill charges for a subset of customers using Universal-3-Pro today, February 28, 2025. Our team is actively investigating the root cause and working to resolve it as quickly as possible. We apologize for the inconvenience and will provide further updates as they become available.
resolved Feb 28, 2026, 08:44 PM UTC

The billing issue that caused unexpected multiple auto-refill charges for a subset of Universal-3-Pro customers on February 28, 2025, has been resolved. Refunds have been issued to the affected customers.

Read the full incident report →

Minor February 27, 2026

Degraded Speaker Identification and Translation

Detected by Pingoru: Feb 27, 2026, 01:29 PM UTC
Resolved: Feb 27, 2026, 03:21 PM UTC
Duration: 1h 52m

Affected: LLM Gateway

Timeline · 4 updates

investigating Feb 27, 2026, 01:29 PM UTC

We are currently investigating an issue that is resulting in degraded Speaker Identification and Translation tasks.
identified Feb 27, 2026, 01:30 PM UTC

The issue has been identified and a fix is being implemented.
monitoring Feb 27, 2026, 02:47 PM UTC

A fix has been implemented and we are monitoring the results.
resolved Feb 27, 2026, 03:21 PM UTC

This incident has been resolved.

Read the full incident report →

Major February 25, 2026

Negative Balance Error

Detected by Pingoru: Feb 25, 2026, 07:39 PM UTC
Resolved: Feb 25, 2026, 09:34 PM UTC
Duration: 1h 55m

Affected: Asynchronous APIStreaming APIPlaygroundBillingLLM Gateway

Timeline · 3 updates

investigating Feb 25, 2026, 07:39 PM UTC

We are currently investigating a billing issue affecting a small number of customer accounts. Impacted accounts are receiving a negative balance via the API, which is preventing transcription requests from completing and returning errors instead. Our team is actively working to identify and correct all affected accounts. We apologize for the disruption this has caused to your workflows and will provide updates as the investigation progresses.
identified Feb 25, 2026, 08:34 PM UTC

Our team has identified the root cause of the negative balance error currently affecting a small number of accounts. A fix is actively being rolled out and we will continue to monitor the situation closely until full resolution is confirmed.
resolved Feb 25, 2026, 09:34 PM UTC

The negative balance error affecting a small number of accounts has been resolved. This issue was an unintentional error that occurred as a result of our ongoing billing system migration. Our team is continuing to monitor the situation to ensure full stability. We apologize for any disruption this caused and thank you for your patience.

Read the full incident report →

Minor February 9, 2026

Increase in 429 errors with LLM Gateway requests using Haiku 4.5

Detected by Pingoru: Feb 09, 2026, 07:53 PM UTC
Resolved: Feb 10, 2026, 12:33 AM UTC
Duration: 4h 39m

Affected: LLM Gateway

Timeline · 3 updates

identified Feb 09, 2026, 07:53 PM UTC

We have identified an issue with the AWS hosting of our Claude Haiku 4.5 model, which is leading to increased 429 errors when using LLM Gateway with the Haiku 4.5 model. This issue is not currently affecting other LLM Gateway models, and retries for requests using Haiku 4.5 are often successful. We are working with our provider to resolve the issue as quickly as possible.
monitoring Feb 09, 2026, 10:55 PM UTC

The increased error rates with Haiku 4.5 that we were seeing earlier have subsided but we are continuing to monitor traffic on our end to ensure continued good performance.
resolved Feb 10, 2026, 12:33 AM UTC

This issue has been resolved and LLM Gateway requests using Haiku 4.5 are continuing to complete normally.

Read the full incident report →

Looking to track AssemblyAI downtime and outages?

Pingoru polls AssemblyAI's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when AssemblyAI reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track AssemblyAI alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring AssemblyAI for free

5 free monitors · No credit card required