- Detected by Pingoru
- Jun 25, 2026, 03:37 PM UTC
- Resolved
- Jun 25, 2026, 04:48 PM UTC
- Duration
- 1h 10m
Affected: Asynchronous API
Timeline · 7 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jun 24, 2026, 09:13 AM UTC
- Resolved
- Jun 24, 2026, 10:40 AM UTC
- Duration
- 1h 26m
Affected: Asynchronous API
Timeline · 4 updates
-
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].
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 09:00 PM UTC
- Resolved
- May 27, 2026, 10:13 PM UTC
- Duration
- 1h 13m
Affected: Dashboard
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 11:08 AM UTC
- Resolved
- May 19, 2026, 03:28 PM UTC
- Duration
- 4h 20m
Affected: Asynchronous API
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 10:56 AM UTC
- Resolved
- May 19, 2026, 10:53 AM UTC
- Duration
- —
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- May 07, 2026, 01:56 PM UTC
- Resolved
- May 07, 2026, 05:04 PM UTC
- Duration
- 3h 8m
Affected: Billing
Timeline · 4 updates
-
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.
Read the full incident report →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
Critical January 29, 2026 - Detected by Pingoru
- Jan 29, 2026, 05:54 PM UTC
- Resolved
- Jan 29, 2026, 07:32 PM UTC
- Duration
- 1h 38m
Affected: Asynchronous APIWebsiteStreaming APIPlaygroundDashboardLLM Gateway
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Jan 28, 2026, 05:50 PM UTC
- Resolved
- Jan 28, 2026, 07:58 PM UTC
- Duration
- 2h 7m
Affected: Asynchronous API
Timeline · 5 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jan 05, 2026, 04:45 PM UTC
- Resolved
- Jan 05, 2026, 05:03 PM UTC
- Duration
- 17m
Affected: Streaming API
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Nov 24, 2025, 10:39 PM UTC
- Resolved
- Nov 25, 2025, 01:45 AM UTC
- Duration
- 3h 5m
Affected: LLM Gateway
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Nov 20, 2025, 08:21 AM UTC
- Resolved
- Nov 20, 2025, 09:41 AM UTC
- Duration
- 1h 20m
Affected: Asynchronous API
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 02:15 PM UTC
- Resolved
- Nov 18, 2025, 08:58 PM UTC
- Duration
- 6h 43m
Affected: WebsiteDashboard
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Nov 15, 2025, 02:30 PM UTC
- Resolved
- Nov 15, 2025, 02:30 PM UTC
- Duration
- —
Timeline · 1 update
-
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..
Read the full incident report →
- Detected by Pingoru
- Oct 31, 2025, 10:38 AM UTC
- Resolved
- Oct 31, 2025, 01:27 PM UTC
- Duration
- 2h 49m
Affected: Asynchronous API
Timeline · 5 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Oct 22, 2025, 05:56 PM UTC
- Resolved
- Oct 22, 2025, 11:58 PM UTC
- Duration
- 6h 1m
Affected: Asynchronous API
Timeline · 6 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 11:00 PM UTC
- Resolved
- Oct 21, 2025, 12:29 AM UTC
- Duration
- 1h 29m
Affected: Billing
Timeline · 3 updates
-
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.
Read the full incident report →
