ElevenLabs Outage History

ElevenLabs is up right now

ElevenLabs had 42 outages in the last 2 years — averaging 1.7 incidents per month.

There were 42 ElevenLabs outages since January 27, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.elevenlabs.io

Minor March 8, 2026

SIP Trunking Failures

Detected by Pingoru
Mar 08, 2026, 05:11 PM UTC
Resolved
Mar 08, 2026, 05:11 PM UTC
Duration
—
Affected: Conversations
Timeline · 2 updates
  1. monitoring Mar 08, 2026, 04:58 PM UTC

    Status: Monitoring 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. Affected components Conversations (Partial outage)

  2. resolved Mar 08, 2026, 05:11 PM UTC

    Status: Resolved We have confirmed with affected clients and in our analytics that SIP trunking functionality is now fully restored. Affected components Conversations (Operational)

Read the full incident report →

Minor March 7, 2026

Voice Not Found Generation Failures

Detected by Pingoru
Mar 07, 2026, 12:13 AM UTC
Resolved
Mar 07, 2026, 12:13 AM UTC
Duration
—
Affected: ConversationsText to Speech
Timeline · 2 updates
  1. identified Mar 06, 2026, 10:28 PM UTC

    Status: Identified 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. Affected components Text to Speech (Degraded performance) Conversations (Degraded performance)

  2. resolved Mar 07, 2026, 12:13 AM UTC

    Status: Resolved We have confirmed fully restored functionality of the voice of "George". Affected components Text to Speech (Operational) Conversations (Operational)

Read the full incident report →

Minor March 4, 2026

Small number of calls being stuck in "in progress" state

Detected by Pingoru
Mar 04, 2026, 11:57 AM UTC
Resolved
Mar 04, 2026, 11:57 AM UTC
Duration
—
Affected: Conversations
Timeline · 2 updates
  1. identified Mar 04, 2026, 07:31 AM UTC

    Status: Identified 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. Affected components Conversations (Degraded performance)

  2. resolved Mar 04, 2026, 11:57 AM UTC

    Status: Resolved The issue has been resolved. Affected components Conversations (Operational)

Read the full incident report →

Minor February 27, 2026

Conversation latency

Detected by Pingoru
Feb 27, 2026, 03:02 PM UTC
Resolved
Feb 27, 2026, 03:02 PM UTC
Duration
—
Affected: Conversations
Timeline · 4 updates
  1. investigating Feb 27, 2026, 01:50 PM UTC

    Status: Investigating 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. Affected components Conversations (Degraded performance)

  2. identified Feb 27, 2026, 02:20 PM UTC

    Status: Identified The issue has been identified as originating from the cloud provider. We are actively working with them to resolve it. Affected components Conversations (Degraded performance)

  3. monitoring Feb 27, 2026, 02:25 PM UTC

    Status: Monitoring Error rates have decreased, and we are currently awaiting confirmation from the cloud provider. Affected components Conversations (Degraded performance)

  4. resolved Feb 27, 2026, 03:02 PM UTC

    Status: Resolved 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. Affected components Conversations (Operational)

Read the full incident report →

Minor February 26, 2026

Elevated 429 “system_busy” errors from STT

Detected by Pingoru
Feb 26, 2026, 11:26 PM UTC
Resolved
Feb 26, 2026, 11:26 PM UTC
Duration
—
Affected: Speech to Text
Timeline · 2 updates
  1. investigating Feb 26, 2026, 10:48 PM UTC

    Status: Investigating We are seeing an increased rate of 429 errors from the Speech-to-Text API. Affected components Speech to Text (Degraded performance)

  2. resolved Feb 26, 2026, 11:26 PM UTC

    Status: Resolved Error rates have returned to the baseline. Affected components Speech to Text (Operational)

Read the full incident report →

Minor February 23, 2026

Agents - v3 conversational model

Detected by Pingoru
Feb 23, 2026, 01:01 PM UTC
Resolved
Feb 23, 2026, 01:01 PM UTC
Duration
—
Affected: Conversations
Timeline · 3 updates
  1. investigating Feb 23, 2026, 10:53 AM UTC

    Status: Investigating We are currently investigating a potential issue affecting the v3 conversational TTS model on the Agents platform. Affected components Conversations (Degraded performance)

  2. monitoring Feb 23, 2026, 12:34 PM UTC

    Status: Monitoring We have released a fix. The error rate has returned to normal levels, and we are actively monitoring the situation. Affected components Conversations (Degraded performance)

  3. resolved Feb 23, 2026, 01:01 PM UTC

    Status: Resolved The issue has been resolved. Affected components Conversations (Operational)

Read the full incident report →

Minor February 14, 2026

V3 requests intermittently produced static noise

Detected by Pingoru
Feb 14, 2026, 09:52 AM UTC
Resolved
Feb 14, 2026, 09:52 AM UTC
Duration
—
Affected: Text to Speech
Timeline · 2 updates
  1. identified Feb 14, 2026, 09:51 AM UTC

    Status: Identified We detected that approximately 1.5% of v3 requests produced static noise Affected components Text to Speech (Degraded performance)

  2. resolved Feb 14, 2026, 09:52 AM UTC

    Status: Resolved The error rates have now returned to normal levels Affected components Text to Speech (Operational)

Read the full incident report →

Minor February 11, 2026

Degraded RAG performance

Detected by Pingoru
Feb 11, 2026, 02:12 AM UTC
Resolved
Feb 11, 2026, 02:12 AM UTC
Duration
—
Affected: RAG
Timeline · 3 updates
  1. identified Feb 10, 2026, 11:36 PM UTC

    Status: Identified Degraded RAG performance, which may cause increased latency. Affected components RAG (Degraded performance)

  2. monitoring Feb 11, 2026, 01:53 AM UTC

    Status: Monitoring We have pushed a fix, which has resulted in latency returning to baseline. Affected components RAG (Degraded performance)

  3. resolved Feb 11, 2026, 02:12 AM UTC

    Status: Resolved The RAG performance issue is now resolved. Affected components RAG (Operational)

Read the full incident report →

Minor February 10, 2026

Post-Call Webhook Schema Missing conversation_id

Detected by Pingoru
Feb 10, 2026, 10:15 PM UTC
Resolved
Feb 10, 2026, 10:15 PM UTC
Duration
—
Affected: Other API endpoints
Timeline · 2 updates
  1. identified Feb 10, 2026, 08:13 PM UTC

    Status: Identified 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. Affected components Other API endpoints (Partial outage)

  2. resolved Feb 10, 2026, 10:15 PM UTC

    Status: Resolved The fix to resolve the missing conversation_id in Post Call Transcripts has been successfully deployed. A detailed RCA will be published later. Affected components Other API endpoints (Operational)

Read the full incident report →

Minor February 2, 2026

EU Residency - Issue with SIP trunks utilizing static IP addresses

Detected by Pingoru
Feb 02, 2026, 10:40 AM UTC
Resolved
Feb 02, 2026, 10:40 AM UTC
Duration
—
Affected: Conversations
Timeline · 3 updates
  1. investigating Feb 02, 2026, 09:12 AM UTC

    Status: Investigating We are investigating a potential issue with SIP trunks utilizing static IP addresses on EU Residency servers. Affected components Conversations (Degraded performance)

  2. monitoring Feb 02, 2026, 09:28 AM UTC

    Status: Monitoring We have released a fix, and we are monitoring the situation. Affected components Conversations (Degraded performance)

  3. resolved Feb 02, 2026, 10:40 AM UTC

    Status: Resolved The issue with Static SIP traffic on the EU residency server has been fully resolved. Affected components Conversations (Operational)

Read the full incident report →

Minor January 30, 2026

Dubbing failures

Detected by Pingoru
Jan 30, 2026, 12:15 PM UTC
Resolved
Jan 30, 2026, 12:15 PM UTC
Duration
—
Affected: OtherElevenCreative
Timeline · 2 updates
  1. investigating Jan 30, 2026, 11:48 AM UTC

    Status: Investigating We are investigating an issue affecting Dubbing jobs. Affected components ElevenCreative (Partial outage) Other (Partial outage)

  2. resolved Jan 30, 2026, 12:15 PM UTC

    Status: Resolved The issue has been fully resolved. Affected components Other (Operational) ElevenCreative (Operational)

Read the full incident report →

Minor January 29, 2026

Increased Conversation Latency

Detected by Pingoru
Jan 29, 2026, 12:30 AM UTC
Resolved
Jan 29, 2026, 12:30 AM UTC
Duration
—
Affected: Conversations
Timeline · 6 updates
  1. investigating Jan 27, 2026, 05:44 PM UTC

    Status: Investigating 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. Affected components Conversations (Degraded performance)

  2. identified Jan 27, 2026, 06:30 PM UTC

    Status: Identified 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. Affected components Conversations (Degraded performance)

  3. monitoring Jan 27, 2026, 09:10 PM UTC

    Status: Monitoring 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. Affected components Conversations (Degraded performance)

  4. resolved Jan 27, 2026, 10:18 PM UTC

    Status: Resolved 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. Affected components Conversations (Operational)

  5. monitoring Jan 28, 2026, 03:49 PM UTC

    Status: Monitoring We have observed a reoccurrence of Gemini-2.5-Flash failures and are continuing to monitor the issue. Affected components Conversations (Degraded performance)

  6. resolved Jan 29, 2026, 12:30 AM UTC

    Status: Resolved 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. Affected components Conversations (Operational)

Read the full incident report →

Minor January 28, 2026

Issue with exports in Dubbing

Detected by Pingoru
Jan 28, 2026, 04:08 PM UTC
Resolved
Jan 28, 2026, 04:08 PM UTC
Duration
—
Affected: ElevenCreative
Timeline · 3 updates
  1. investigating Jan 28, 2026, 02:52 PM UTC

    Status: Investigating We are investigating an issue related to the export of Dubbing jobs. Affected components ElevenCreative (Degraded performance)

  2. monitoring Jan 28, 2026, 03:29 PM UTC

    Status: Monitoring 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. Affected components ElevenCreative (Degraded performance)

  3. resolved Jan 28, 2026, 04:08 PM UTC

    Status: Resolved We have confirmed that our fix successfully remediated the issue, and Dub Exportation is fully functional. Previous download attempts may need to be resubmitted. Affected components ElevenCreative (Operational)

Read the full incident report →

Minor January 27, 2026

Delayed RAG indexing

Detected by Pingoru
Jan 27, 2026, 06:44 AM UTC
Resolved
Jan 27, 2026, 06:44 AM UTC
Duration
—
Affected: RAG
Timeline · 2 updates
  1. investigating Jan 27, 2026, 06:16 AM UTC

    Status: Investigating RAG indexing has been delayed for some documents. This does not affect RAG during calls; it only impacts the indexing of newly uploaded documents. Affected components RAG (Degraded performance)

  2. resolved Jan 27, 2026, 06:44 AM UTC

    Status: Resolved The issue with RAG indexing has been resolved. Affected components RAG (Operational)

Read the full incident report →