ElevenLabs Outage History
ElevenLabs is up right nowPingoru has recorded 168 incidents for ElevenLabs: 168 in the last 12 months and 95 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 10 | 23 of 720 (3%) |
| May 2026 | 9 | 17 of 744 (2%) |
| June 2026 | 6 | 18 of 720 (2%) |
| July 2026 | 10 | 33 of 744 (4%) |
| August 2026 | 27 | 21 of 744 (3%) |
| September 2026 | 33 | 53 of 720 (7%) |
| October 2026 | 30 | 16 of 592 (3%) |
Incidents, newest first
Minor March 8, 2026 SIP Trunking Failures 12m Conversations
Started Mar 08, 2026, 04:58 PM UTC· resolved Mar 08, 2026, 05:11 PM UTC
- monitoring Mar 08, 2026, 04:58 PM UTC
Starting at 03:50 UTC today, a portion of SIP Trunks imported into ElevenLabs saw failures when SIP calls were initiated. As of 16:45 UTC, mitigation measures were implemented, and monitoring continues to ensure full resolution.
- resolved Mar 08, 2026, 05:11 PM UTC
We have confirmed with affected clients and in our analytics that SIP trunking functionality is now fully restored.
Minor March 6, 2026 Voice Not Found Generation Failures 1h 45m Conversations, Text to Speech
Started Mar 06, 2026, 10:28 PM UTC· resolved Mar 07, 2026, 12:13 AM UTC
- identified Mar 06, 2026, 10:28 PM UTC
Requests made to the voice "George", ID: JBFqnCBsd6RMkjVDRZzb, started failing at 19:30 UTC today. We have identified the cause of the issue and are working to release a fix for this. As a temporary solution, adding the voice ID 6WwXjDDEMyNmFG95zycZ from the library will allow generations that were previously directed at the voice of George to complete. The voice of George will soon be accessible again. If you are making requests to legacy voices "legacy voices": https://help.elevenlabs.io/hc/en-us/articles/26928417254801-What-are-Legacy-voices and getting the same error, please switch to a non-legacy voice.
- resolved Mar 07, 2026, 12:13 AM UTC
We have confirmed fully restored functionality of the voice of "George".
Minor March 4, 2026 Small number of calls being stuck in "in progress" state 4h 26m Conversations
Started Mar 04, 2026, 07:31 AM UTC· resolved Mar 04, 2026, 11:57 AM UTC
- identified Mar 04, 2026, 07:31 AM UTC
Since March 3 at 7:00 AM UTC, an issue has been affecting some calls using the Conversational v3 Model, which is in Alpha stage. We have identified the root cause, and a fix is being deployed. Conversation recordings, transcripts, and analytics are unavailable for affected calls. Affected calls are currently displayed as "in progress" and will be transitioned to "failed" automatically in the next 48h. We will provide a further update once the fix has been fully rolled out.
- resolved Mar 04, 2026, 11:57 AM UTC
The issue has been resolved.
Minor February 27, 2026 Conversation latency 1h 11m Conversations
Started Feb 27, 2026, 01:50 PM UTC· resolved Feb 27, 2026, 03:02 PM UTC
- investigating Feb 27, 2026, 01:50 PM UTC
We are currently investigating increased conversation latency affecting the Gemini models. Conversations are not failing due to fallbacks; however, we are observing elevated response times. We are actively working with the cloud provider to diagnose and resolve the issue.
- identified Feb 27, 2026, 02:20 PM UTC
The issue has been identified as originating from the cloud provider. We are actively working with them to resolve it.
- monitoring Feb 27, 2026, 02:25 PM UTC
Error rates have decreased, and we are currently awaiting confirmation from the cloud provider.
- resolved Feb 27, 2026, 03:02 PM UTC
Gemini model performance has fully recovered; Our cloud provider has informed us that the upstream issue is fully resolved, and we have carefully tracked our metrics to confirm this.
Minor February 26, 2026 Elevated 429 “system_busy” errors from STT 56s
Started Feb 26, 2026, 11:25 PM UTC· resolved Feb 26, 2026, 11:26 PM UTC
No vendor updates were posted for this incident.
Minor February 25, 2026 Website Slowness and API Request Latency 5h 9m UI, Speech to Text, Other, Other API endpoints and 1 more
Started Feb 25, 2026, 02:36 PM UTC· resolved Feb 25, 2026, 07:45 PM UTC
- investigating Feb 25, 2026, 02:36 PM UTC
We are currently investigating an issue with website and API requests and are working to identify the root cause as quickly as possible. We will provide an update as soon as more information becomes available. TTS API request and Agents conversations are working. There may be issues related to API services that affect conversation initiation.
- identified Feb 25, 2026, 03:04 PM UTC
We have identified an underlying issue with our cloud provider that is impacting service availability.
- identified Feb 25, 2026, 05:05 PM UTC
We have isolated the components responsible for performance degradation and are attempting to implement workarounds to bypass the affected cloud provider services.
- identified Feb 25, 2026, 05:23 PM UTC
Our engineering team is continuing to investigate issues with the cloud provider components. Multiple engineering teams and leadership is involved in the efforts. We'll continue monitoring closely and provide timely updates as the situation evolves.
- identified Feb 25, 2026, 05:44 PM UTC
Our engineering team is actively exploring multiple remediation paths in parallel while working to isolate the root cause. We have escalated this issue both to our infrastructure provider and to internal leadership to ensure it receives the highest level of attention and resources. A definitive root cause has not yet been identified, but we are making iterative changes and closely monitoring their impact. We will continue to provide updates as our investigation progresses.
- identified Feb 25, 2026, 06:01 PM UTC
Our team continues to actively investigate the degraded performance affecting services. We are working through several lines of investigation in parallel and methodically testing potential contributing factors. This remains escalated with our infrastructure provider and internal leadership, with additional engineering resources dedicated to this effort. While a definitive root cause has not yet been identified, each step is helping us build a clearer picture of the underlying issue. We understand the impact this is having and are treating this with the highest priority. We will provide another update in 15-20 minutes.
- identified Feb 25, 2026, 06:27 PM UTC
We are continuing to investigate all possible root causes and eliminate potential causes. Additionally we are clarifying affected products below. What's affected: • Agents Platform - degraded performance due to issues around conversation initiation. Conversations that do start function as normal thus API customers should retry failed initiation conversations. • Website - intermittent slowness What's working normally: • Text-to-Speech (TTS) API • Speech-to-Text (STT) API • Dubbing API Our engineering team remains fully engaged and is continuing to work through active lines of investigation alongside our infrastructure provider. We are iterating on potential mitigations and monitoring the results closely. We will continue to provide updates every 15-20 minutes.
- identified Feb 25, 2026, 06:54 PM UTC
Our team remains fully engaged and continues to work through active lines of investigation. All previously noted affected and operational components remain in the same state. We will provide another update in 15-20 minutes
- monitoring Feb 25, 2026, 07:10 PM UTC
We have implemented changes to the affected services that have resulted in signs of recovery and improved performance. We are closely monitoring to confirm stability and will provide an another update in 15–20 minutes.
- monitoring Feb 25, 2026, 07:27 PM UTC
Affected services continue to show sustained improvement following the changes implemented earlier. We are continuing to monitor key metrics and will confirm full resolution once we are satisfied with stability across baseline error rates. Next update in 15-20 minutes.
- resolved Feb 25, 2026, 07:45 PM UTC
As of 7:45 PM UTC, all affected services have fully recovered and are operating normally. Agents Platform and Audio Platform (Website) have returned to full health. Text-to-Speech (TTS), Speech-to-Text (STT), and Dubbing APIs were unaffected throughout the incident. The root cause has been identified and remediated. We will be conducting a thorough post-incident review and will share further details in a follow-up report. We apologize for the disruption and appreciate your patience throughout this incident. If you are still experiencing any issues, please don't hesitate to contact our support team.
Minor February 23, 2026 Agents - v3 conversational model 2h 7m Conversations
Started Feb 23, 2026, 10:53 AM UTC· resolved Feb 23, 2026, 01:01 PM UTC
- investigating Feb 23, 2026, 10:53 AM UTC
We are currently investigating a potential issue affecting the v3 conversational TTS model on the Agents platform.
- monitoring Feb 23, 2026, 12:34 PM UTC
We have released a fix. The error rate has returned to normal levels, and we are actively monitoring the situation.
- resolved Feb 23, 2026, 01:01 PM UTC
The issue has been resolved.
Minor February 17, 2026 Failures for Post Call Webhooks – UI, Conversations, Quality, Speech to Text and 6 more
Started Feb 17, 2026, 01:26 PM UTC· resolved Feb 17, 2026, 01:26 PM UTC
- resolved Feb 17, 2026, 01:26 PM UTC
We had a temporary outage between 13:26 and 13:56 UTC, which resulted in a number of post call webhook failures. This issue should now be resolved.
Minor February 14, 2026 V3 requests intermittently produced static noise 1m Text to Speech
Started Feb 14, 2026, 09:51 AM UTC· resolved Feb 14, 2026, 09:52 AM UTC
- identified Feb 14, 2026, 09:51 AM UTC
We detected that approximately 1.5% of v3 requests produced static noise
- resolved Feb 14, 2026, 09:52 AM UTC
The error rates have now returned to normal levels
Minor February 10, 2026 Degraded RAG performance 2h 35m RAG
Started Feb 10, 2026, 11:36 PM UTC· resolved Feb 11, 2026, 02:12 AM UTC
- identified Feb 10, 2026, 11:36 PM UTC
Degraded RAG performance, which may cause increased latency.
- monitoring Feb 11, 2026, 01:53 AM UTC
We have pushed a fix, which has resulted in latency returning to baseline.
- resolved Feb 11, 2026, 02:12 AM UTC
The RAG performance issue is now resolved.
Minor February 10, 2026 Post-Call Webhook Schema Missing conversation_id 2h 2m Other API endpoints
Started Feb 10, 2026, 08:13 PM UTC· resolved Feb 10, 2026, 10:15 PM UTC
- identified Feb 10, 2026, 08:13 PM UTC
At 18:30 UTC, an unintentional change resulted in conversation_id not being included as a field within Post Call Transcript webhooks. As a temporary workaround, we advise consuming it from conversation_initiation_client_data.dynamic_variables.system__conversation_id, if possible. We are currently working on a fix to address this.
- resolved Feb 10, 2026, 10:15 PM UTC
The fix to resolve the missing conversation_id in Post Call Transcripts has been successfully deployed. A detailed RCA will be published later.
Minor February 3, 2026 Data Extraction/Call Summary Disruption and Conversation Latency 6d 23h Conversations
Started Feb 03, 2026, 05:37 PM UTC· resolved Feb 10, 2026, 05:04 PM UTC
- identified Feb 03, 2026, 05:37 PM UTC
Starting at ~14:00 UTC today, some conversations have been affected by a disruption in our data extraction and call summary mechanisms, and a subset of these may have seen increased conversation latency. We have identified the issue as stemming from reduced availability of the Gemini 2.0 and Gemini 2.5 Flash models, and are currently working to resolve the issue.
- identified Feb 03, 2026, 08:14 PM UTC
We have observed a significant reduction in errors, and continue to work on a solution to fully mitigate the core issue.
- monitoring Feb 03, 2026, 10:23 PM UTC
We have observed errors return to baseline. Currently, call summaries and data extraction are fully functional. At this point in time, we are following through with improvements to data extraction and call summaries to ensure they are not impacted by similar availability issues in the future.
- resolved Feb 04, 2026, 10:13 AM UTC
The issue has been fully resolved, and safeguards have been implemented to prevent recurrence.
- monitoring Feb 04, 2026, 03:53 PM UTC
We have observed data extraction and evaluation failures reoccur, and are following through to ensure complete mitigation.
- resolved Feb 04, 2026, 10:10 PM UTC
We have fully released a fix that implements increased redundancy in our Data Collection and Evaluation mechanisms via multiple backup LLMs, and confirmed complete mitigation.
- identified Feb 05, 2026, 01:55 PM UTC
We have observed an increase in latency affecting the Gemini models and are actively investigating the issue, and are working on improvements to the formatting of the recently implemented Data Collection backups.
- resolved Feb 06, 2026, 11:31 PM UTC
Following our recent patch, we have tracked incidence of unexpected Data Collection values and Evaluation failures as they have decreased to negligible levels, and confirmed restored functionality with affected users. Moving forward, we will continue to improve our system to have effective fallbacks and increased redundancy.
- identified Feb 09, 2026, 04:44 PM UTC
We have observed a reoccurrence of Data Collection failures, and are working on additional measures to mitigate them.
- monitoring Feb 09, 2026, 11:03 PM UTC
We have implemented additional safeguards, and will continue to monitor through peak traffic to ensure complete resolution.
- resolved Feb 10, 2026, 05:04 PM UTC
We have confirmed the release of our Data Extraction fix has continued to mitigate issue occurrence during peak traffic and that rates of Data Extraction failures are below pre-incident baseline.
Minor February 2, 2026 EU Residency - Issue with SIP trunks utilizing static IP addresses 1h 27m Conversations
Started Feb 02, 2026, 09:12 AM UTC· resolved Feb 02, 2026, 10:40 AM UTC
- investigating Feb 02, 2026, 09:12 AM UTC
We are investigating a potential issue with SIP trunks utilizing static IP addresses on EU Residency servers.
- monitoring Feb 02, 2026, 09:28 AM UTC
We have released a fix, and we are monitoring the situation.
- resolved Feb 02, 2026, 10:40 AM UTC
The issue with Static SIP traffic on the EU residency server has been fully resolved.
Major January 30, 2026 Dubbing failures 2m
Started Jan 30, 2026, 12:12 PM UTC· resolved Jan 30, 2026, 12:15 PM UTC
No vendor updates were posted for this incident.
Minor January 28, 2026 Issue with exports in Dubbing 1h 15m ElevenCreative
Started Jan 28, 2026, 02:52 PM UTC· resolved Jan 28, 2026, 04:08 PM UTC
- investigating Jan 28, 2026, 02:52 PM UTC
We are investigating an issue related to the export of Dubbing jobs.
- monitoring Jan 28, 2026, 03:29 PM UTC
We have reverted the release responsible for the issues exporting Dubbing projects, and are seeing restored functionality. We are monitoring to ensure fully restored service.
- resolved Jan 28, 2026, 04:08 PM UTC
We have confirmed that our fix successfully remediated the issue, and Dub Exportation is fully functional. Previous download attempts may need to be resubmitted.
Minor January 27, 2026 Increased Conversation Latency 1d 6h Conversations
Started Jan 27, 2026, 05:44 PM UTC· resolved Jan 29, 2026, 12:30 AM UTC
- investigating Jan 27, 2026, 05:44 PM UTC
Currently, some conversations are affected by increased latency due to elevated LLM generation failures. We are investigating the root cause and working to mitigate this.
- identified Jan 27, 2026, 06:30 PM UTC
We have identified the issue scope is isolated to the Gemini-2.5-Flash model. We are working with our cloud provider to resolve this.
- monitoring Jan 27, 2026, 09:10 PM UTC
We have observed a significant decrease in error occurrence and are continuing to monitor availability of the resources that provide service for Gemini-2.5-Flash.
- resolved Jan 27, 2026, 10:18 PM UTC
LLM failures have now returned to baseline, and conversation latency using Gemini-2.5-Flash is now back to expected levels. For future mitigation, we plan to improve our fallback methods to better handle reduced cloud provider availability.
- monitoring Jan 28, 2026, 03:49 PM UTC
We have observed a reoccurrence of Gemini-2.5-Flash failures and are continuing to monitor the issue.
- resolved Jan 29, 2026, 12:30 AM UTC
LLM error rates have normalized, and Gemini-2.5-Flash conversation latency is back within expected ranges. We’ll continue monitoring closely. Improvements accommodating reduced cloud provider have been implemented, and will be live shortly.
Minor January 27, 2026 Delayed RAG indexing 28m RAG
Started Jan 27, 2026, 06:16 AM UTC· resolved Jan 27, 2026, 06:44 AM UTC
- investigating Jan 27, 2026, 06:16 AM UTC
RAG indexing has been delayed for some documents. This does not affect RAG during calls; it only impacts the indexing of newly uploaded documents.
- resolved Jan 27, 2026, 06:44 AM UTC
The issue with RAG indexing has been resolved.