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 588 (0%) |
Incidents, newest first
Minor March 30, 2026 Increase in error rates for Claude Sonnet 4.6 5h 13m LLM Gateway
Started Mar 30, 2026, 06:41 PM UTC· resolved Mar 30, 2026, 11:55 PM UTC
- 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.
Minor March 6, 2026 Longer than usual processing times for transcription of pre-recorded audio – Asynchronous API
Started Mar 06, 2026, 07:04 PM UTC· resolved Mar 06, 2026, 07:04 PM UTC
- 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.
Minor February 28, 2026 Billing Issue Affecting Some Universal-3-Pro Users 1h 24m Billing
Started Feb 28, 2026, 07:19 PM UTC· resolved Feb 28, 2026, 08:44 PM UTC
- 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.
Minor February 27, 2026 Degraded Speaker Identification and Translation 1h 52m LLM Gateway
Started Feb 27, 2026, 01:29 PM UTC· resolved Feb 27, 2026, 03:21 PM UTC
- 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.
Major February 25, 2026 Negative Balance Error 1h 55m Asynchronous API, Streaming API, Playground, Billing and 1 more
Started Feb 25, 2026, 07:39 PM UTC· resolved Feb 25, 2026, 09:34 PM UTC
- 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.
Minor February 9, 2026 Increase in 429 errors with LLM Gateway requests using Haiku 4.5 4h 39m LLM Gateway
Started Feb 09, 2026, 07:53 PM UTC· resolved Feb 10, 2026, 12:33 AM UTC
- 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.
Critical January 29, 2026 Async + LLM gateway APIs returning 5xx 1h 38m Asynchronous API, Website, Streaming API, Playground and 2 more
Started Jan 29, 2026, 05:54 PM UTC· resolved Jan 29, 2026, 07:32 PM UTC
- investigating Jan 29, 2026, 05:54 PM UTC
We are currently investigating an issue affecting async + LLM gateway services. More updates to come as we learn more.
- investigating Jan 29, 2026, 06:02 PM UTC
We are continuing to investigate this issue.
- investigating Jan 29, 2026, 06:09 PM UTC
We are currently investigating an issue affecting our Async and LLM Gateway services, which are returning 500 errors. Our team is actively working to identify and resolve the problem. We will provide updates as more information becomes available. All streaming API and EU endpoint services are running normally. This incident is isolated to NA API endpoints for async + LLM gateway.
- investigating Jan 29, 2026, 06:29 PM UTC
We are seeing requests beginning to successfully complete and have moved to the monitoring phase. Some requests are still returning 500 errors. Our team continues to actively investigate and monitor the situation. We will provide updates as more information becomes available.
- monitoring Jan 29, 2026, 06:30 PM UTC
We are seeing requests beginning to successfully complete and have moved to the monitoring phase. Some requests are still returning 500 errors. Our website is down, and logins may be affected. Our team continues to actively investigate and monitor the situation. We will provide updates as more information becomes available.
- monitoring Jan 29, 2026, 06:42 PM UTC
We are continuing to see requests being completed. We are working through a backlog of requests, resulting in elevated turnaround times while we recover. Our team continues to actively monitor the situation. We will provide updates as more information becomes available.
- monitoring Jan 29, 2026, 07:18 PM UTC
We are continuing to work through the backlog, and turnaround times are improving. Our team continues to actively monitor the situation. We will provide updates as more information becomes available.
- resolved Jan 29, 2026, 07:32 PM UTC
We have cleared the backlog, and turnaround times are back to normal. Our team continues to actively monitor the situation. We will provide a post-mortem when available.
- postmortem Feb 05, 2026, 06:35 PM UTC
**Summary: January 29 Outage** On January 29, our Async Transcription and LLM Gateway went down for 25 minutes, followed by two hours of degraded performance. Here's what happened. Our traffic has been steadily increasing and we received an influx of batch transcription jobs that were higher than usual. Autoscaling did what it should—spun up workers. We ran out of spot instances, fell back to on-demand, then hit AWS's Elastic Network Interface limit. Every ECS task needs an ENI. With no ENIs available, our authentication service couldn't rotate its tasks. It scaled to zero. Everything stopped. When we tried to recover, a Lambda function meant to help with failures was hammering the AWS API with describe calls, rate-limiting the very operations we needed to bring things back. A tool built for recovery was blocking recovery. **What actually went wrong:** We didn't monitor ENI utilization and our authentication service shared resources with batch workers. Traffic spike in one starved the other. **What we're doing:** Short-term: ENI alerts, isolate auth on dedicated capacity, fix the Lambda. Medium-term: Full multi-region for everything. This was preventable. We had the warning signs and didn't connect them. We're sorry, and we're fixing it.
Minor January 28, 2026 Higher latency when using the EU endpoint 2h 7m Asynchronous API
Started Jan 28, 2026, 05:50 PM UTC· resolved Jan 28, 2026, 07:58 PM UTC
- investigating Jan 28, 2026, 05:50 PM UTC
Our team is actively investigating an issue that is causing increased latency for transcriptions using the EU endpoint for pre-recorded transcriptions. Customers may experience transcripts being queued. This is not affecting streaming usage on the EU endpoint.
- investigating Jan 28, 2026, 06:06 PM UTC
This issue is also affecting the EU DELETE endpoint. Some DELETE requests for transcriptions are resulting in an error.
- identified Jan 28, 2026, 06:39 PM UTC
The team has identified the issue and it is caused by an AWS Operational Issue on their Amazon Elastic Compute Cloud (Ireland). Our team is in touch with AWS and monitoring the situation: https://health.aws.amazon.com/health/status
- monitoring Jan 28, 2026, 07:02 PM UTC
We are seeing significant signs of recovery and processing of queued transcripts. Our team will continue to monitor the situation.
- resolved Jan 28, 2026, 07:58 PM UTC
We have continued to see good performance, and traffic is once again working normally so we are marking this issue as resolved.
Minor January 5, 2026 Elevated connection errors when starting new Streaming sessions 17m Streaming API
Started Jan 05, 2026, 04:45 PM UTC· resolved Jan 05, 2026, 05:03 PM UTC
- investigating Jan 05, 2026, 04:45 PM UTC
We experienced a spike in connection issues for new streaming sessions between 8:30 and 8:35am PT. These errors affected requests for both NA and EU regions. These connection issues have subsided, but our team is working to ensure continued good performance.
- resolved Jan 05, 2026, 05:03 PM UTC
This increase in errors was inadvertantly caused by a change that was made around 8:30am PT, which was immediately reverted when our team noticed the increase in errors. We have continued to see good performance since that rollback and are now marking this issue as resolved.
Minor November 24, 2025 Expected responses from LLM Gateway using Claude models 3h 5m LLM Gateway
Started Nov 24, 2025, 10:39 PM UTC· resolved Nov 25, 2025, 01:45 AM UTC
- investigating Nov 24, 2025, 10:39 PM UTC
We are currently investigating an issue with LLM Gateway that is causing unexpected responses when using Claude models. This issue is not affecting LLM Gateway requests using other models. We are working to identify and resolve the root cause of these issues.
- identified Nov 25, 2025, 12:22 AM UTC
We have identified the root cause of this issue and are working to release a fix.
- monitoring Nov 25, 2025, 01:15 AM UTC
We have released a fix that has resolved the unexpected responses we were seeing when Claude models were used. Everything is working normally now, but we will continue to monitor traffic to ensure continued good performance.
- resolved Nov 25, 2025, 01:45 AM UTC
We have continued to see good performance since releasing the earlier fix and are now marking this issue as resolved.
Major November 20, 2025 Delayed processing of transcripts on Slam 1h 20m Asynchronous API
Started Nov 20, 2025, 08:21 AM UTC· resolved Nov 20, 2025, 09:41 AM UTC
- investigating Nov 20, 2025, 08:21 AM UTC
We are currently investigating an issue where there has been delayed processing of transcripts on Slam-1, specifically in our us-west-2 region. This began at 5:43 UTC. Customers will experience queueing or erroring of transcripts when using our Slam-1 model. Our Universal model is not affected by this incident.
- identified Nov 20, 2025, 08:26 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Nov 20, 2025, 08:47 AM UTC
A fix has been implemented and our team is monitoring the results. Slam-1 has resumed normal processing.
- resolved Nov 20, 2025, 09:41 AM UTC
This incident has been resolved.
Major November 18, 2025 Cloudflare outage affecting documentation access and Google Auth flow on dashboard 6h 43m Website, Dashboard
Started Nov 18, 2025, 02:15 PM UTC· resolved Nov 18, 2025, 08:58 PM UTC
- investigating Nov 18, 2025, 02:15 PM UTC
Due to the ongoing incident with Cloudflare, our documentation is unable to be accessed and users cannot use Google Authentication to sign in to their dashboard.
- identified Nov 18, 2025, 02:23 PM UTC
Due to the ongoing incident with Cloudflare, our documentation is unable to be accessed and users cannot use Google Authentication to sign in to their dashboard.
- monitoring Nov 18, 2025, 03:15 PM UTC
Our documentation is now accessible and all users can sign-in to the dashboard using Google Authentication. We will continue to monitor the situation in case anything changes.
- resolved Nov 18, 2025, 08:58 PM UTC
Cloudflare has restored normal operation, and access to our documentation and Google Authentication is fully restored. All services are functioning as expected, and the incident is now resolved.
Minor November 15, 2025 SSL certificate validation errors connecting to Streaming API 7h
Started Nov 15, 2025, 07:30 AM UTC· resolved Nov 15, 2025, 02:30 PM UTC
- resolved Nov 15, 2025, 02:33 PM UTC
From 8p GMT on November 14, 2025 - 2:20p GMT on November 15, 2025, users connecting to our Streaming API using our US endpoint `wss://streaming.assemblyai.com/v3/ws` from Europe, Africa, and eastern Asia were experiencing SSL certificate validation errors. While the underlying SSL misconfiguration was resolved shortly after engineering engagement, some customers experienced extended connection failures during this window. Additional safeguards have since been implemented to prevent similar issues..
Minor October 31, 2025 Degraded performance for requests using Slam-1 2h 49m Asynchronous API
Started Oct 31, 2025, 10:38 AM UTC· resolved Oct 31, 2025, 01:27 PM UTC
- investigating Oct 31, 2025, 10:38 AM UTC
We are currently investigating an issue that is leading to longer-than-usual processing times for pre-recorded audio transcriptions using the Slam-1 model that is resulting in some transcripts being returned with server errors. Requests using the Universal model, which is enabled by default, are not affected by this issue.
- investigating Oct 31, 2025, 10:39 AM UTC
We are continuing to investigate this issue.
- identified Oct 31, 2025, 10:42 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 31, 2025, 11:49 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 31, 2025, 01:27 PM UTC
This incident has been resolved.
Major October 22, 2025 Requests failing for Slam-1 model 6h 1m Asynchronous API
Started Oct 22, 2025, 05:56 PM UTC· resolved Oct 22, 2025, 11:58 PM UTC
- identified Oct 22, 2025, 05:56 PM UTC
We are currently seeing longer-than-usual turnaround times for pre-recorded audio transcriptions that are using our Slam-1 model. Requests using the Universal model are unaffected. We are working to address this issue and will provide an update here as soon as possible.
- identified Oct 22, 2025, 06:01 PM UTC
We are now seeing increased error rates and failures for requests using the Slam-1 model so we are elevating this issue to a partial outage. Requests using Universal are working normally, so consider using that model as a short-term workaround if needed. Our team is working to resolve this issue as quickly as possible.
- identified Oct 22, 2025, 07:03 PM UTC
We are once again starting to see requests using Slam-1 succeed, but we are still working to fully resolve the issue. We will follow up with another update once the issue has been fully mitigated.
- identified Oct 22, 2025, 07:20 PM UTC
We are still seeing good success rates for requests using the Slam-1 model, but we are still seeing occasional slower-than-usual processing times, which we are working to address.
- monitoring Oct 22, 2025, 07:37 PM UTC
Success rates and turnaround times for requests using Slam-1 have returned to normal ranges, but we are continuing to monitor traffic to ensure continued good performance.
- resolved Oct 22, 2025, 11:58 PM UTC
We have continued to see good performance for requests using Slam-1 and are now marking this issue as resolved.
Minor October 20, 2025 Account Creation Issues 1h 29m Billing
Started Oct 20, 2025, 11:00 PM UTC· resolved Oct 21, 2025, 12:29 AM UTC
- identified Oct 20, 2025, 11:00 PM UTC
We are currently experiencing an issue with new account creation due to the ongoing AWS issues that may affect the ability of newly created accounts to use our API or Playground.
- monitoring Oct 20, 2025, 11:39 PM UTC
Account creation and updates are once again working normally, but we are continuing to monitor the situation to ensure continued good performance.
- resolved Oct 21, 2025, 12:29 AM UTC
This incident has been resolved.
Minor September 30, 2025 Increased error rates for pre-recorded Speech-to-Text 2h 54m Asynchronous API
Started Sep 30, 2025, 05:33 PM UTC· resolved Sep 30, 2025, 08:28 PM UTC
- investigating Sep 30, 2025, 05:33 PM UTC
Our team is currently investigating an issue that is causing an increase in server errors for our pre-recorded audio speech-to-text feature. This issue is only affecting a small number of requests, but it is affecting requests to both Universal and Slam-1 models. If you experience a server error we suggest retrying the request as those will likely be successful.
- identified Sep 30, 2025, 06:25 PM UTC
Our team has identified where the errors are occurring in our pipeline and is currently working to identify and resolve the root cause. This issue is currently only affecting an extremely small percentage of total pre-recorded audio traffic. 99%+ of requests are still completing successfully.
- monitoring Sep 30, 2025, 07:28 PM UTC
We have released a fix to address the small increase in errors we were seeing and are monitoring to ensure continued good performance.
- resolved Sep 30, 2025, 08:28 PM UTC
We have continued to see good performance for pre-recorded audio so we are now marking this issue as resolved.
Minor September 29, 2025 Some Streaming Sessions are Failing to be Established 11h 41m Streaming API
Started Sep 29, 2025, 01:49 PM UTC· resolved Sep 30, 2025, 01:31 AM UTC
- investigating Sep 29, 2025, 01:49 PM UTC
Between 1:30p and 1:40p GMT there were an increased number of new streaming sessions that were failing to be established. Customers would have received the error message "received 3005 (registered) Session Cancelled: An error occurred; ".
- investigating Sep 29, 2025, 01:50 PM UTC
The Streaming API has now returned to full functionality. Our team is still investigating the root cause of this issue.
- investigating Sep 29, 2025, 03:41 PM UTC
Our team is still investigating the cause of the elevated errors, but the Streaming API is still continuing to function normally.
- monitoring Sep 29, 2025, 07:32 PM UTC
We have continued to see stable performance throughout the day. The Streaming API is operating normally and we are monitoring the effects of recent changes to ensure continued service stability. Our team continues working to determine the root cause of the earlier connection failures.
- resolved Sep 30, 2025, 01:31 AM UTC
We have continued to see good performance since rolling back the update that was identified to be the cause of this issue, so we are marking this issue as resolved.
Minor September 23, 2025 Increased Processing Time for Non-English Language Transcriptions 2h
Started Sep 23, 2025, 08:00 AM UTC· resolved Sep 23, 2025, 10:00 AM UTC
- resolved Sep 23, 2025, 10:26 AM UTC
From 8a - 10a GMT there was an issue related to the pick-up time of our non-English language models. This caused an increase in processing time for pre-recorded transcriptions. Our Engineering team has released a fix and all transcriptions should now be processing normally.
Notice September 22, 2025 Increase in turnaround times for pre-recorded audio transcription 14m Asynchronous API
Started Sep 22, 2025, 07:34 PM UTC· resolved Sep 22, 2025, 07:49 PM UTC
- investigating Sep 22, 2025, 07:34 PM UTC
We are currently investigating an issue that is causing a small increase in turnaround times for STT services for pre-recorded audio for some requests. Traffic as a whole is still completing within the range of normal turnaround times. We will provide additional updates as we learn more.
- resolved Sep 22, 2025, 07:49 PM UTC
Aside from a small window of about five minutes around 12:10pm PT where turnaround times were slightly higher than usual, we have continued to see turnaround times within the expected ranges so we are now closing this issue.
Minor September 16, 2025 Degraded Streaming Performance 1h 4m
Started Sep 16, 2025, 09:00 AM UTC· resolved Sep 16, 2025, 10:04 AM UTC
- resolved Sep 16, 2025, 10:30 AM UTC
We experienced an issue with our Streaming API between 09:00 GMT and 10:04 GMT. This resulted in reduced quality of service for streaming sessions and some sessions were closing unexpectedly. A fix was implemented and our Streaming API is now functioning normally.
Major August 5, 2025 Slam-1 requests not completing successfully 7h 9m Asynchronous API
Started Aug 05, 2025, 04:05 PM UTC· resolved Aug 05, 2025, 11:15 PM UTC
- investigating Aug 05, 2025, 04:05 PM UTC
We are currently investigating an issue with Slam-1 that is preventing the successful completion of transcription requests using the model. We will share additional information as it becomes available. Please note this issue is only affecting requests using Slam-1 as the `speech_model`. Universal is unaffected.
- investigating Aug 05, 2025, 04:14 PM UTC
We are continuing to investigate the issues affecting Slam-1. Currently, all requests using Slam-1 as the `speech_model` are failing with a "Server error, developers have been alerted" error. Our team is working to resolve this issue as quickly as possible. Note: This issue is only affecting requests using Slam-1 as the `speech_model`. Changing the `speech_model` to Universal will allow requests to complete successfully. See this section of our documentation for more information on specifying a speech model: https://www.assemblyai.com/docs/speech-to-text/pre-recorded-audio/select-the-speech-model
- monitoring Aug 05, 2025, 04:23 PM UTC
We have resolved the issue that was affecting Slam-1 and are now seeing requests being processed successfully. We will continue to monitor traffic to ensure good performance, but everything is working as expected at the moment.
- identified Aug 05, 2025, 04:42 PM UTC
We are once again experiencing issues with Slam-1 where requests are failing with a "Server error, developers have been alerted" error. Note: This issue is only affecting requests using Slam-1 as the `speech_model`. Changing the `speech_model` to Universal will allow requests to complete successfully. See this section of our documentation for more information on specifying a speech model: https://www.assemblyai.com/docs/speech-to-text/pre-recorded-audio/select-the-speech-model
- identified Aug 05, 2025, 04:53 PM UTC
We are seeing Slam-1 requests complete successfully once again, but we are still working to fully resolve the root cause of this issue.
- identified Aug 05, 2025, 05:16 PM UTC
We are still seeing good performance with the Slam model and requests completing as expected, but we are still working to fully resolve the root cause to prevent issues in the future.
- monitoring Aug 05, 2025, 07:38 PM UTC
We have continued to see good performance with no instances of increased errors over the last couple of hours ,but are continuing to monitor to ensure there are no further issues.
- resolved Aug 05, 2025, 11:15 PM UTC
We have continued to see good performance for the last ~6 hours so we are marking this issue as resolved. To prevent future issues, we have made some improvements to allow Slam-1 to scale more effectively.
Minor July 30, 2025 Delay in New Transcriptions Appearing Under Transcription History on Dashboard 4h 46m Dashboard
Started Jul 30, 2025, 09:05 AM UTC· resolved Jul 30, 2025, 01:52 PM UTC
- investigating Jul 30, 2025, 09:05 AM UTC
We are currently investigating an issue where there is a delay in new transcriptions showing up under the Transcription History tab of the dashboard.
- investigating Jul 30, 2025, 10:02 AM UTC
Our team is still currently investigating the root cause of this delay.
- identified Jul 30, 2025, 11:48 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 30, 2025, 12:57 PM UTC
A fix has been implemented and all customer dashboards should now be up to date. We are continuing to monitor the situation.
- resolved Jul 30, 2025, 01:52 PM UTC
This incident has been resolved.
Minor July 28, 2025 Slower than usual processing times with Slam-1 – Asynchronous API
Started Jul 28, 2025, 03:33 PM UTC· resolved Jul 28, 2025, 03:33 PM UTC
- resolved Jul 28, 2025, 03:33 PM UTC
We had a brief period earlier where processing times for requests using the Slam-1 beta model took longer than expected. This slowdown occurred from approximately 7:37am PT to 7:57am PT and has now been resolved. Our team is continuing to monitor traffic to ensure continued good performance.
Minor July 14, 2025 Degraded Formatting for English Transcripts 1h 9m Asynchronous API
Started Jul 14, 2025, 03:38 PM UTC· resolved Jul 14, 2025, 04:47 PM UTC
- investigating Jul 14, 2025, 03:38 PM UTC
We are experiencing a formatting issue affecting English transcripts. Transcripts will continue to process successfully, but formatting may appear incorrect or incomplete. We're actively investigating this issue.
- monitoring Jul 14, 2025, 03:59 PM UTC
The English transcript formatting issue is now considered resolved. We are monitoring to ensure continued stability. Please re-run any affected transcripts to ensure correct formatting.
- resolved Jul 14, 2025, 04:47 PM UTC
This incident has been resolved.