ElevenLabs text-to-speech, voice cloning, speech-to-text, and audio AI services.
Official status data last reflected here:
[ STATUS AT A GLANCE ]
Current status of individual ElevenLabs services
When ElevenLabs has issues, Bifrost automatically routes your requests to a healthy alternative provider. Zero code changes. 99.999% effective uptime.
What ElevenLabs does, where the data on this page comes from, and recent reliability
[ ABOUT ELEVENLABS ]
ElevenLabs provides Text-to-speech, Voice cloning, Speech-to-text, and Conversational voice APIs. Voice AI outages can interrupt customer-facing voice flows, content pipelines, and speech interfaces that depend on fast and reliable audio generation.
This page pulls data from ElevenLabs's official status page to show current service health, any active incidents, and a history of recent issues, all in one view.
[ DATA SOURCES ]
ElevenLabs publishes detailed component status, a full incident archive, and scheduled maintenance data through their official status page.
[ RELIABILITY ]
[ COMMON USE CASES ]
Voice AI outages can interrupt customer-facing voice flows, content pipelines, and speech interfaces that depend on fast and reliable audio generation.
Active incidents, scheduled maintenance, and incident history for ElevenLabs
Oct 6, 2026
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.
Sep 29, 2026 · Resolved Sep 29, 2026
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.
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.
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.
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 generated a response after progressing".
Sep 28, 2026 · Resolved Sep 28, 2026
Our engineers have confirmed that STT latency has fully recovered.
We have traced STT latency metrics as they have improved and are continuing to monitor to ensure full resolution.
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.
Sep 28, 2026 · Resolved Sep 28, 2026
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.
We have released a fix, we are continuing to monitor the situation, the platform is operational now.
We are investigating a possible issue with our underlying database provider. We will continue posting updates.
We are investigating an issue on EU residency affecting the ElevenAgents platform.
Sep 21, 2026 · Resolved Sep 22, 2026
The elevated error rate has been resolved and we're following up internally to prevent future occurrences.
We're currently investigating an elevated error rate occurring with ElevenReader that may impact streaming and app navigation.
Sep 19, 2026 · Resolved Sep 19, 2026
The issue has been fully resolved and everything is functional again.
We have released another fix, the error rate is now down.
We are still seeing some calls that are failing, our team is currently applying a new fix.
The calls are working now.
We are investigating an issue that occurred with some calls where the call didn't start; however, the calls are working now.
Sep 10, 2026 · Resolved Sep 10, 2026
Our engineers have confirmed full recovery of the Conversation Search functionality in the web UI and the API.
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 search](https://elevenlabs.io/docs/eleven-agents/api-reference/conversations/messages/text-search "Text search") endpoint may continue to see failures as we continue to work to mitigate the issue.
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.
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 are working on getting the history back up.
Sep 9, 2026 · Resolved Sep 10, 2026
Our engineers have deployed a fix that has fully restored Claude MCP functionality.
We are currently working to release a targeted fix to restore functionality to the Claude MCP tool
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.
Sep 7, 2026 · Resolved Sep 7, 2026
Service has been fully restored to remaining affected areas. We will share further details on the cause.
Services have started recovering. Streaming is now functional, and we're working to restore service to other impacted product areas.
We've identified the cause and are currently implementing a fix to restore full service availability.
We're currently investigating an elevated error rate occurring with ElevenReader. Some pages may fail to load, or the app may be inaccessible.
Sep 4, 2026 · Resolved Sep 4, 2026
After completing the monitoring stage, we have confirmed that STT latency has returned to baseline stability.
The issue has been fixed, the error rate should be zero. We are currently monitoring the situation.
We've identified the root cause and are rolling out a fix. Error rates should be improving, and we're continuing to monitor.
We're investigating a latency increase on the Global Residency server for Speech-to-Text and Dubbing models, affecting a small subset of requests.
Sep 4, 2026 · Resolved Sep 4, 2026
The issue has been resolved, everything is back at normal.
We have released a fix, the error rate is back at zero. We are monitoring the situation.
We're investigating a latency increase on the EU Residency server for Speech-to-Text models, affecting a small subset of requests.
Aug 31, 2026 · Resolved Aug 31, 2026
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.
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.
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. Response times may be slightly longer than usual, and we appreciate your patience. We will respond to everyone as soon as we can.
We're still investigating. This is an issue with our ticketing provider, and we're working with them to restore the service.
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.
Aug 27, 2026 · Resolved Aug 27, 2026
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.
Outbound Batch calls in the European residency experienced dispatch delays of up to 30 minutes between 08:00 and 11:00 UTC.
Aug 26, 2026 · Resolved Aug 26, 2026
The issue has been resolved. A root cause analysis will be shared shortly.
Latency has returned to baseline levels.
We are currently investigating the root cause.
Aug 24, 2026 · Resolved Aug 24, 2026
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.
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 pass further updates as we track the deployment of this fix.
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.
The error rate has decreased, although the issue has not been fully resolved yet. We are continuing to work toward a complete resolution.
We have located the cause of the elevated errors, and we are working on a fix.
+ 1 more updates
Aug 18, 2026 · Resolved Aug 18, 2026
Inbound calls are currently operational.
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 been connecting normally since ~11:00 UTC. No customer action needed.
Aug 3, 2026 · Resolved Aug 3, 2026
The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.
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 were affected; retried requests generally succeeded. The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.
Jul 31, 2026 · Resolved Jul 31, 2026
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.
Our engineers are putting together a targeted fix to resolve the remaining SIP failures in the US region.
We have identified the root cause of the failed SIP calls and prepared a fix.
Our team is still actively working to restore all calls and phone numbers to their normal working state.
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.
+ 5 more updates
Jul 17, 2026 · Resolved Jul 17, 2026
The issue has been resolved. All the previous conversations should be visible now.
We have fixed the issue, all the conversations should become visible. We are monitoring the situation.
Conversations in the EU Residency are appearing in Conversation History with a smaller delay. However, nothing is lost; all the conversations are saved. We are working on a fix.
Jul 14, 2026 · Resolved Jul 14, 2026
We've taken steps to mitigate the Speech Engine failures and have confirmed that performance has returned to baseline.
We've identified a recent release that is causing Speech Engine conversations to fail. We are currently working to address the issue.
Jul 9, 2026 · Resolved Jul 9, 2026
The fix has been released. Outbound WhatsApp messaging is operating normally.
Customers using WhatsApp to initiate outbound messages will see failed conversations. We've identified the problem and a fix is being rolled out.
Check the status indicator at the top of this page. It pulls directly from ElevenLabs's official status page. If ElevenLabs is experiencing any issues, you'll see it reflected here. This real-time monitoring helps teams quickly identify whether performance problems are caused by ElevenLabs infrastructure or their own systems.
This page tracks Text-to-speech, Voice cloning, Speech-to-text, and Conversational voice APIs using data from ElevenLabs's official status page. You can see current component health, active incidents, and a history of past issues. This visibility is crucial for teams building resilient AI applications that need to route around provider outages.
We check ElevenLabs's status page every 60 seconds to ensure you get near real-time status updates. How quickly issues show up here depends on how fast ElevenLabs updates their own official status. For production systems that need instant failover, Bifrost can automatically detect and route around degraded providers.
Voice AI outages can interrupt customer-facing voice flows, content pipelines, and speech interfaces that depend on fast and reliable audio generation. Real-time status monitoring enables proactive incident response and helps teams decide when to route traffic to alternative providers for maximum uptime.
When ElevenLabs experiences an outage, the best practice is automatic failover to alternative AI providers. Bifrost is an open-source AI gateway that automatically detects ElevenLabs degradation and routes LLM traffic to healthy alternatives like Azure AI Speech, Google Text-to-Speech, keeping your application running with zero manual intervention. This intelligent routing ensures your users never experience downtime from a single provider's issues.
Production AI applications should never depend on a single provider. Bifrost AI Gateway provides automatic multi-provider failover, intelligent load balancing, and health-based routing. When ElevenLabs degrades, Bifrost instantly routes requests to operational alternatives while maintaining API compatibility. This architecture approach is used by teams running mission-critical AI features.
Based on incident history, ElevenLabs issues most frequently affect Text to Speech. Common causes include infrastructure scaling issues, regional cloud provider problems, API gateway overload, and deployment errors. Teams using Bifrost can configure automatic routing rules based on component-level status to minimize impact.
When ElevenLabs experiences issues, Bifrost AI Gateway can automatically route your LLM traffic to these alternatives
💡 Build resilient AI apps: Configure Bifrost to automatically detect ElevenLabs outages and route requests to healthy alternatives. This multi-provider approach ensures your application maintains uptime even when individual providers experience issues. Learn more about Bifrost AI Gateway