ElevenLabs

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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

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

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

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.

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.

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.

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.

We experienced an increased error rate across multiple services between 17:04 UTC to 17:13 UTC on July 8th in the US region. We are investigating why this happened to prevent recurrence.

We have implemented a fix for the heightened image and video generation error rate. We have not seen any further issues after implementing the fix.

We are experiencing an increased error rate for generating images and videos. This will impact all services that rely on image and video generation, including Flows and Templates. We are looking into this and will post updates as they become available.

Our engineers were able to push a fix to resolve the failure to save when editing or creating Agent tools that include the Put, Patch, or Post methods in their configuration. We have validated that the tools are now able to be saved, and confirm full resolution.

Currently, creating and updating agent tools when the tool has the Post, Put, and Patch methods in the tool configuration does not allow the tool to save. Our engineers have identified the core issue and are currently working to implement a fix.

We have confirmed that dubbing request errors have fully returned to baseline.

We are aware of reports of intermittent issues affecting some UI dubbing requests and are actively investigating. The platform remains available, and no broader impact to the UI has been identified at this time.

The issue has been resolved, the users can now login normally.

We are currently investigating an issue where certain users are unable to log in to the website.

We've confirmed that the issue has been resolved with our upstream provider and error rates have remained stable at zero.

Error rates have returned to zero, and we are continuing to monitor performance to ensure stability.

We are currently investigating an issue stemming from an upstream provider which is affecting Text to Voice (TTV), where some generations are failing with a 500 error.

Starting Thursday, June 4th at approximately 19:12 UTC, we experienced an issue with OpenAI image and video models (GPT Image and Sora) due to a provider-side issue. Requests that used any of these models would fail. This also impacted Flows and Templates. This was fully resolved at 19:52 UTC on the same day.

The incident has been resolved. The root cause of the problem was a GCP incident affecting I/O on certain VM types in one of the zones we are using. As a result, some nodes in our clusters were affected.

We are monitoring an issue that caused transient errors for a small number of customers using Speech-to-Text and Speech-to-Speech services.

We are currently investigating an issue causing transient errors for a small subset of customers using Speech-to-Text (STT) and Speech-to-Speech (STS). We will provide updates as our investigation progresses.

The incident was resolved.

We recently identified an issue where a smaller number of Eleven V3 TTS generations were returning 429s on the global residency server. This affected users on lower priority tiers. The service has since been fully restored and is operating normally.