ElevenLabs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-06 10:28 UTC

   We're currently investigating disruptions in SIP calls in our EU residency.

2. investigating 2026-10-06 11:21 UTC

   We are still investigating. We will continue posting updates as more information becomes available

3. investigating 2026-10-06 12:04 UTC

   We are currently still investigating. We will post updates here as soon as more information becomes available

4. monitoring 2026-10-06 12:14 UTC

   Error rates have returned to normal. We're currently monitoring the situation to confirm that the issue has been resolved

5. resolved 2026-10-06 12:51 UTC

   The issue has been resolved. EU SIP services are operational and stable.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-09 12:41 UTC

   We are investigating an issue where the MCP connection is not working. Please note that this does not affect ElevenAgents, where everything is working correctly.

2. identified 2026-09-10 01:28 UTC

   We are currently working to release a targeted fix to restore functionality to the Claude MCP tool

3. resolved 2026-09-10 14:58 UTC

   Our engineers have deployed a fix that has fully restored Claude MCP functionality.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-04 11:41 UTC

   We're investigating a latency increase on the EU Residency server for Speech-to-Text models, affecting a small subset of requests.

2. monitoring 2026-09-04 12:07 UTC

   We have released a fix, the error rate is back at zero. We are monitoring the situation.

3. resolved 2026-09-04 12:12 UTC

   The issue has been resolved, everything is back at normal.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-18 12:39 UTC

   From ~07:00 UTC, a small percentage (<1%) of inbound Twilio calls failed to connect due to a configuration error on our side. Affected callers were unable to connect to an agent; outbound calls and other traffic were unaffected. The change has been rolled back and calls have...

2. resolved 2026-08-18 12:43 UTC

   Inbound calls are currently operational.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-03 17:39 UTC

   We are having issues with our marketing website - our web app and API are unaffected.

2. monitoring 2025-09-03 18:15 UTC

   The marketing website is live again. We are monitoring. The web app and API remain unaffected.

3. resolved 2025-09-03 18:44 UTC

   Marketing website is live again. Web app and API remain unaffected.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-10-13 03:25 UTC

   Between 03:25 and 04:44 UTC on October 13, 2026, some requests to create an Instant Voice Clone failed with an error. This affected the Voice Lab in the app and the Voices API endpoint (POST /v1/voices/add), when background noise removal was turned on. Clones created without...

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-20 11:04 UTC

   We are currently investigating an issue causing request failures with the v3 model. This only affects the v3 model.

2. resolved 2026-01-20 11:35 UTC

   The issue has been completely resolved, and the requests with the v3 model are being processed.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-09 16:36 UTC

   Some Agent Platform conversations utilizing RAG are currently affected by RAG latency increases, in some cases resulting in slower RAG performance or intermittent call failures. Our team is currently working to resolve this.

2. monitoring 2026-01-09 17:19 UTC

   We have identified the direct cause of the RAG failures, and are monitoring performance. At the moment, instances of call failures have returned to baseline. We are investigating further measures that may be necessary to completely mitigate the core issue.

3. identified 2026-01-10 06:17 UTC

   Some Agent Platform conversations utilizing RAG are currently affected by RAG latency increases, in some cases resulting in slower RAG performance or intermittent call failures. Our team is currently working to resolve this.

4. monitoring 2026-01-10 07:51 UTC

   Remediation measures have rolled out and instances of failures have returned to baseline. We are continuing to investigate further measures that may be necessary to completely mitigate the core issue.

5. resolved 2026-01-13 07:00 UTC

   Remediation measures have been fully rolled out, restoring failure rates to baseline. The root cause has been addressed, and the issue is now fully resolved.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-31 05:27 UTC

   We are investigating an issue with adding/missing voices in the EU and India Residency Environments. THe

2. monitoring 2025-10-31 06:37 UTC

   We have released a fix, and the error rate is decreasing. We are monitoring the performance.

3. resolved 2025-10-31 07:07 UTC

   The issue with the Isolated Environments has been resolved after we released a fix. The incident was caused by a change made to how we cache Voice Library voices in data residency environments. The issue only surfaced gradually hours after we released it as the cache for these...

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-08 16:09 UTC

   We are currently investigating increased latency and request failures affecting Dubbing.

2. monitoring 2026-10-08 16:15 UTC

   We have traced error metrics as they have returned to baseline. We're currently monitoring to ensure full resolution.

3. monitoring 2026-10-08 16:30 UTC

   Since 16:30 UTC, we have observed recurrence of Dubbing errors and latency. We're working with an upstream provider for full mitigation, and will continue to post updates as new information arises.

4. monitoring 2026-10-08 17:10 UTC

   Errors have returned to baseline since 17:10 UTC. We are continuing to work with an upstream provider for full mitigation.

5. resolved 2026-10-08 22:10 UTC

   After several hours of monitoring, our metrics show that error rate has remained at its stable baseline since 17:55 UTC; the increase in Dubbing platform latency and failure rate is now resolved.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-08 15:00 UTC

   We are currently investigating an issue causing call failures in Agent conversations using SIP. Non-SIP Agent conversations are unaffected.

2. resolved 2026-10-08 15:43 UTC

   We have monitored error metrics and have confirmed that as of 15:15 UTC, we do not see continuing Agent SIP conversation failures. We will conduct an internal investigation and post a full Root Cause Analysis upon conclusion.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-10 09:44 UTC

   We are investigating an issue in the EU Residency where recent conversations are not showing up in history. The conversation history is not lost; there is just a lag in displaying it. Please note that this doesn't affect actual conversations; everything is working correctly. We...

2. identified 2026-09-10 10:19 UTC

   Conversations are now populating in the conversation history again. Text search of conversations isn't working yet; we're actively fixing it and will post another update once it's resolved.

3. identified 2026-09-10 16:21 UTC

   Currently, loading conversations in conversation history without filters is fully functional. Our engineers are still working to fully restore search filter functionality. Requests to the [Text...

4. resolved 2026-09-10 20:43 UTC

   Our engineers have confirmed full recovery of the Conversation Search functionality in the web UI and the API.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-07 02:19 UTC

   We're currently investigating an elevated error rate occurring with ElevenReader. Some pages may fail to load, or the app may be inaccessible.

2. identified 2026-09-07 05:14 UTC

   We've identified the cause and are currently implementing a fix to restore full service availability.

3. identified 2026-09-07 05:45 UTC

   Services have started recovering. Streaming is now functional, and we're working to restore service to other impacted product areas.

4. resolved 2026-09-07 07:20 UTC

   Service has been fully restored to remaining affected areas. We will share further details on the cause.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-15 09:12 UTC

   We are currently investigating an issue with the Agents platform, TTS and Scribe in the EU residency server.

2. monitoring 2026-05-15 09:30 UTC

   We have released an update, and the error rate is back to normal. We are currently monitoring the situation.

3. resolved 2026-05-15 09:42 UTC

   The issue has been resolved. We will publish a public write-up on this status page once the investigation is completed.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-22 14:50 UTC

   We are currently investigating evidence of issues related to payment-processing. We will publish further details when the problem's scope and impact are clear.

2. monitoring 2026-04-22 15:01 UTC

   As of 14:55 UTC, we have observed error rates return to baseline, and are continuing to investigate the root cause.

3. monitoring 2026-04-22 15:11 UTC

   We have identified the root cause: A misconfiguration in our billing system caused provisioning of subscriptions to be delayed. Errors remain at baseline. We are continuing our work to ensure the root cause is fully addressed to maintain future system integrity.

4. resolved 2026-04-22 15:39 UTC

   We have confirmed full issue resolution.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-25 14:36 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...

2. identified 2026-02-25 15:04 UTC

   We have identified an underlying issue with our cloud provider that is impacting service availability.

3. identified 2026-02-25 17:05 UTC

   We have isolated the components responsible for performance degradation and are attempting to implement workarounds to bypass the affected cloud provider services.

4. identified 2026-02-25 17:23 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.

5. identified 2026-02-25 17:44 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...

6. identified 2026-02-25 18:01 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...

7. identified 2026-02-25 18:27 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...

8. identified 2026-02-25 18:54 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

9. monitoring 2026-02-25 19:10 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.

10. monitoring 2026-02-25 19:27 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.

11. resolved 2026-02-25 19:45 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...

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: Security incident or emergency response to a vulnerability. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-10-15 02:01 UTC

   Some of our support forms have been temporarily disabled due to misuse. We’re working to restore them safely as soon as possible. In the meantime, please reach out to our support team via email for assistance.

2. resolved 2025-10-15 18:05 UTC

   We've now restored access to our customer support submission form and are monitoring the situation, though things seem to have slowed down. We also see this was a widespread attack affecting multiple companies. Our ticketing system provider, Zendesk, also issued a warning about...

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-04-08 13:00 UTC

   We are experiencing a temporary issue with website authentication rejecting all authentication tokens. We are working on a fix

2. resolved 2025-04-08 13:39 UTC

   Website should work now

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-02-19 19:10 UTC

   Some TTS requests using our TurboV2 model are seeing an increase in latency.

2. resolved 2025-02-19 19:34 UTC

   Incident Resolved

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-12-04 16:56 UTC

   We've identified an infrastructure issue which is causing elevated error rate for the Eleven Multilingual v2 model and are working on a solution.

2. monitoring 2024-12-04 17:41 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-12-04 18:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-10-30 17:42 UTC

   From 17:04 UTC to 17:22 UTC, users may have experienced elevated error rates for TTS v3, Dubbing, and STT, due to a brief capacity shortage. All other TTS models were unaffected.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-21 03:59 UTC

   We are investigating an increased error rate on calls to our Forced Alignment endpoint.

2. resolved 2025-09-21 06:58 UTC

   We've identified and resolved the issue.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-10 03:30 UTC

   We are seeing an elevated error rates when querying voices across the platform. Engineering has been alerted, and a fix is underway.

2. identified 2025-09-10 04:17 UTC

   We’re still seeing elevated error rates when querying voices. A fix has been deployed and will be available shortly as we monitor progress.

3. resolved 2025-09-10 04:28 UTC

   The fix is live, and voice query error rates have stabilized.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-06-11 12:15 UTC

   We have identified an issue causing fraction of API calls to fail. Mitigation is in progress.

2. resolved 2025-06-11 12:35 UTC

   Issue was resolved.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-05-16 12:24 UTC

   Transfer to human tool outage - incorrect number passed in.

2. resolved 2025-05-16 13:25 UTC

   Fix released.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-13 09:21 UTC

   We are investigating elevated latency and timeouts affecting multiple endpoints, including some Elevenagents endpoints. Some requests may be slow or fail. Our team is actively looking into the cause.

2. resolved 2026-10-13 09:47 UTC

   Error rates have returned to normal. We are currently still investigating the cause of this downtime and will update the status page with an RCA as soon as possible.

3. identified 2026-10-13 09:57 UTC

   We’re seeing error rates rise again, so calls may still fail or experience increased latency.

4. monitoring 2026-10-13 10:38 UTC

   Error rates are still flaky. We are monitoring the affected endpoints to confirm stability and are working with our data provider on a root cause analysis.

5. identified 2026-10-13 11:42 UTC

   We are still seeing elevated errors and timeouts on the affected endpoints, and requests may continue to fail. We are actively working with our data provider to restore full service and bring the endpoints back online.

6. identified 2026-10-13 12:54 UTC

   We are actively working with our data service provider to ensure endpoint stability. We will update the status page as soon as we have received confirmation that all our endpoints are back to normal.

7. monitoring 2026-10-13 13:42 UTC

   Error rates have continued to stabilize. We are continuing to monitor the affected endpoints to ensure service remains steady.

8. resolved 2026-10-13 14:18 UTC

   The incident is resolved. Error rates are back to normal, and stable service has been confirmed. We will publish a Root cause analysis once our review of the incident is complete.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-13 03:25 UTC

   Between 03:25 and 04:44 UTC on October 13, 2026, some requests to create an Instant Voice Clone failed with an error. This affected the Voice Lab in the app and the Voices API endpoint (POST /v1/voices/add), when background noise removal was turned on. Clones created without...

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-10-12 16:30 UTC

   We experienced a transient error due to a heavy traffic spike. We will implementing improvements to be more resilient in the future.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-08 16:09 UTC

   We are currently investigating increased latency and request failures affecting Dubbing.

2. monitoring 2026-10-08 16:15 UTC

   We have traced error metrics as they have returned to baseline. We're currently monitoring to ensure full resolution.

3. monitoring 2026-10-08 16:30 UTC

   Since 16:30 UTC, we have observed recurrence of Dubbing errors and latency. We're working with an upstream provider for full mitigation, and will continue to post updates as new information arises.

4. monitoring 2026-10-08 17:10 UTC

   Errors have returned to baseline since 17:10 UTC. We are continuing to work with an upstream provider for full mitigation.

5. resolved 2026-10-08 22:10 UTC

   After several hours of monitoring, our metrics show that error rate has remained at its stable baseline since 17:55 UTC; the increase in Dubbing platform latency and failure rate is now resolved.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-08 15:00 UTC

   We are currently investigating an issue causing call failures in Agent conversations using SIP. Non-SIP Agent conversations are unaffected.

2. resolved 2026-10-08 15:43 UTC

   We have monitored error metrics and have confirmed that as of 15:15 UTC, we do not see continuing Agent SIP conversation failures. We will conduct an internal investigation and post a full Root Cause Analysis upon conclusion.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-08 08:48 UTC

   We've identified degraded performance on our Music endpoints. We're investigating now.

2. monitoring 2026-10-08 08:51 UTC

   We have identified the cause, fixed the underlying issue and the service is now recovering.

3. resolved 2026-10-08 08:58 UTC

   Music had reduced availability after a latent infrastructure configuration issue was triggered by routine automated maintenance. This stopped new instances from starting and prevented automated recovery, and service was restored by manual intervention. The service is now fully...

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 10:28 UTC

   We're currently investigating disruptions in SIP calls in our EU residency.

2. investigating 2026-10-06 11:21 UTC

   We are still investigating. We will continue posting updates as more information becomes available

3. investigating 2026-10-06 12:04 UTC

   We are currently still investigating. We will post updates here as soon as more information becomes available

4. monitoring 2026-10-06 12:14 UTC

   Error rates have returned to normal. We're currently monitoring the situation to confirm that the issue has been resolved

5. resolved 2026-10-06 12:51 UTC

   The issue has been resolved. EU SIP services are operational and stable.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 09:09 UTC

   We are investigating elevated latency affecting a small percentage of text-to-speech (TTS) requests. We will share an update as soon as we have more information.

2. monitoring 2026-10-06 11:38 UTC

   A fix has been implemented for the elevated latency affecting some TTS requests. We are currently monitoring the results to confirm the issue is resolved.

3. resolved 2026-10-06 12:14 UTC

   The issue has been resolved, latency is back to normal.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-29 18:49 UTC

   We are currently investigating increased latency, conversation failures, and API request failures currently known to affect Agents and STT. These failures may manifest as delays in agent conversations, 429s to STT requests, or conversation failures with the error: "START node...

2. identified 2026-09-29 19:39 UTC

   We have isolated the cause of the increased latency and errors, and are working to resolve it. Current evidence suggests that the Sound Effects product and other Creative Platform products may also be affected, but scope and severity of impact to these products remains unclear.

3. monitoring 2026-09-29 20:12 UTC

   Our engineers have applied a fix for the likely root cause. We are seeing signs of recovery but we will continue to monitor until recovery is fully confirmed.

4. resolved 2026-09-29 20:23 UTC

   We have not seen any further errors after the fix was applied. All services are fully operational and stable. We will post an RCA on our status page after further investigation.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-28 15:42 UTC

   We have identified an issue with increased latency for Speech to Text API requests. We are looking into it and will post updates as they become available.

2. monitoring 2026-09-28 16:05 UTC

   We have traced STT latency metrics as they have improved and are continuing to monitor to ensure full resolution.

3. resolved 2026-09-28 16:54 UTC

   Our engineers have confirmed that STT latency has fully recovered.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-28 13:57 UTC

   We are investigating an issue on EU residency affecting the ElevenAgents platform.

2. investigating 2026-09-28 14:08 UTC

   We are investigating a possible issue with our underlying database provider. We will continue posting updates.

3. monitoring 2026-09-28 14:20 UTC

   We have released a fix, we are continuing to monitor the situation, the platform is operational now.

4. resolved 2026-09-28 14:39 UTC

   We can confirm that the issue has been fixed and that the service is fully operational. Resolution time was 14:18 UTC We will post the RCA to the status page after the investigation.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-21 23:25 UTC

   We're currently investigating an elevated error rate occurring with ElevenReader that may impact streaming and app navigation.

2. resolved 2026-09-22 02:56 UTC

   The elevated error rate has been resolved and we're following up internally to prevent future occurrences.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-19 00:34 UTC

   We are investigating an issue that occurred with some calls where the call didn't start; however, the calls are working now.

2. monitoring 2026-09-19 00:35 UTC

   The calls are working now.

3. identified 2026-09-19 00:48 UTC

   We are still seeing some calls that are failing, our team is currently applying a new fix.

4. monitoring 2026-09-19 00:56 UTC

   We have released another fix, the error rate is now down.

5. resolved 2026-09-19 02:08 UTC

   The issue has been fully resolved and everything is functional again.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-10 09:44 UTC

   We are investigating an issue in the EU Residency where recent conversations are not showing up in history. The conversation history is not lost; there is just a lag in displaying it. Please note that this doesn't affect actual conversations; everything is working correctly. We...

2. identified 2026-09-10 10:19 UTC

   Conversations are now populating in the conversation history again. Text search of conversations isn't working yet; we're actively fixing it and will post another update once it's resolved.

3. identified 2026-09-10 16:21 UTC

   Currently, loading conversations in conversation history without filters is fully functional. Our engineers are still working to fully restore search filter functionality. Requests to the [Text...

4. resolved 2026-09-10 20:43 UTC

   Our engineers have confirmed full recovery of the Conversation Search functionality in the web UI and the API.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-09 12:41 UTC

   We are investigating an issue where the MCP connection is not working. Please note that this does not affect ElevenAgents, where everything is working correctly.

2. identified 2026-09-10 01:28 UTC

   We are currently working to release a targeted fix to restore functionality to the Claude MCP tool

3. resolved 2026-09-10 14:58 UTC

   Our engineers have deployed a fix that has fully restored Claude MCP functionality.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-07 02:19 UTC

   We're currently investigating an elevated error rate occurring with ElevenReader. Some pages may fail to load, or the app may be inaccessible.

2. identified 2026-09-07 05:14 UTC

   We've identified the cause and are currently implementing a fix to restore full service availability.

3. identified 2026-09-07 05:45 UTC

   Services have started recovering. Streaming is now functional, and we're working to restore service to other impacted product areas.

4. resolved 2026-09-07 07:20 UTC

   Service has been fully restored to remaining affected areas. We will share further details on the cause.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-04 13:55 UTC

   We're investigating a latency increase on the Global Residency server for Speech-to-Text and Dubbing models, affecting a small subset of requests.

2. identified 2026-09-04 14:16 UTC

   We've identified the root cause and are rolling out a fix. Error rates should be improving, and we're continuing to monitor.

3. monitoring 2026-09-04 14:34 UTC

   The issue has been fixed, the error rate should be zero. We are currently monitoring the situation.

4. resolved 2026-09-04 21:01 UTC

   After completing the monitoring stage, we have confirmed that STT latency has returned to baseline stability.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-04 11:41 UTC

   We're investigating a latency increase on the EU Residency server for Speech-to-Text models, affecting a small subset of requests.

2. monitoring 2026-09-04 12:07 UTC

   We have released a fix, the error rate is back at zero. We are monitoring the situation.

3. resolved 2026-09-04 12:12 UTC

   The issue has been resolved, everything is back at normal.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-31 08:10 UTC

   We're aware that some users may experience issues when opening new customer support tickets or replying to old ones. We're investigating and will update shortly.

2. investigating 2026-08-31 08:46 UTC

   We're still investigating. This is an issue with our ticketing provider, and we're working with them to restore the service.

3. identified 2026-08-31 09:34 UTC

   Our ticketing provider has identified the cause of the issue and is working to restore service. At this stage, the resolution is dependent on their work, and we do not yet have a timeline from them. In the meantime, our team is handling as many tickets as possible manually....

4. identified 2026-08-31 11:20 UTC

   Our ticketing system is back online. Although, it is not yet at full capacity. We're still waiting for our ticketing provider to get us fully back up. We can now receive tickets again and have started getting back to customers.

5. resolved 2026-08-31 12:35 UTC

   We’ll mark this incident as resolved. Our ticketing system is operational again, though the outage materially affected its setup. We’re working with the team to restore full functionality, but capacity is sufficient to consider the incident resolved.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-27 13:05 UTC

   Outbound Batch calls in the European residency experienced dispatch delays of up to 30 minutes between 08:00 and 11:00 UTC.

2. resolved 2026-08-27 13:08 UTC

   Latency has since decreased, and we are working on adding more alerts on our side to help us identify and respond to similar latency issues earlier.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-26 17:10 UTC

   We are currently investigating the root cause.

2. monitoring 2026-08-26 17:53 UTC

   Latency has returned to baseline levels.

3. resolved 2026-08-26 23:13 UTC

   The issue has been resolved. A root cause analysis will be shared shortly.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-24 08:49 UTC

   We’re currently experiencing issues loading media across several products, including Studio, Audiobooks, Image & Video, Music and Dubbing. We are actively investigating the cause.

2. identified 2026-08-24 10:18 UTC

   We have located the cause of the elevated errors, and we are working on a fix.

3. identified 2026-08-24 11:42 UTC

   The error rate has decreased, although the issue has not been fully resolved yet. We are continuing to work toward a complete resolution.

4. identified 2026-08-24 14:53 UTC

   We are currently working to deploy a targeted fix to resolve the existing issues of media loading within Studio, Audiobooks, Image & Video, Music and Dubbing. We will pass further updates as we track the deployment of this fix.

5. identified 2026-08-24 17:12 UTC

   Work is still underway to release a fix to resolve media loading within Studio, Audiobooks, Image & Video, Music and Dubbing. Until the fix is fully rolled out, common symptoms may include failures when exporting media in Studio, Dubbing, and other products. We'll continue to...

6. resolved 2026-08-24 18:43 UTC

   Our engineers have traced media loading error rates as they have returned to baseline. Studio, Audiobooks, Image & Video, Music and Dubbing products should now functional normally.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-18 12:39 UTC

   From ~07:00 UTC, a small percentage (<1%) of inbound Twilio calls failed to connect due to a configuration error on our side. Affected callers were unable to connect to an agent; outbound calls and other traffic were unaffected. The change has been rolled back and calls have...

2. resolved 2026-08-18 12:43 UTC

   Inbound calls are currently operational.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-03 09:34 UTC

   Between 06:39 and 07:13 UTC on August 3, a network issue at our upstream cloud provider caused elevated error rates and intermittent connection timeouts on Text-to-Speech and Speech-to-Text requests. At peak, approximately 2% of Speech-to-Text and 1% of Text-to-Speech requests...

2. resolved 2026-08-03 09:36 UTC

   The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-31 03:08 UTC

   Starting at ~1:00 UTC, calls to a portion of phone numbers imported into the ElevenLabs Agent Platform are failing. We are currently working to isolate the root cause and restore full functionality.

2. identified 2026-07-31 04:00 UTC

   We've identified a likely contributing factor related to infrastructure resource constraints affecting SIP call routing. We're currently validating a fix.

3. resolved 2026-07-31 05:29 UTC

   The issue has been resolved. Call routing is now fully restored, and we're assessing follow-ups to improve proactive alerting and prevent recurrence.

4. investigating 2026-07-31 06:18 UTC

   Following the earlier fix, we're seeing renewed inbound call routing failures for a portion of phone numbers. We're currently investigating.

5. identified 2026-07-31 09:06 UTC

   Our team has identified a potential cause of the call outages and is currently validating a fix. We will share further updates as soon as we have more information.

6. identified 2026-07-31 11:12 UTC

   Calls should be back to normal for the EU and India residencies. The US residency may still experience some downtime, but our team is working to resolve the issue. In the meantime, the immediate workaround is to remove the affected number and re-add it, if possible.

7. identified 2026-07-31 13:01 UTC

   Our team is still actively working to restore all calls and phone numbers to their normal working state.

8. identified 2026-07-31 14:33 UTC

   We have identified the root cause of the failed SIP calls and prepared a fix.

9. identified 2026-07-31 18:02 UTC

   Our engineers are putting together a targeted fix to resolve the remaining SIP failures in the US region.

10. resolved 2026-07-31 19:00 UTC

    After our recent mitigation steps, our engineers have traced SIP call failure rate as it has returned to baseline. We will publish a complete root cause analysis shortly.

Excerpts are shortened. Read the full incident on ElevenLabs's status page.