The issue has been resolved and error rates are back to normal.

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

We have implemented a fix for the issues affecting EU residency STT requests that use the source_url parameter or the deprecated cloud_storage_url parameter and confirmed full issue resolution.

We've tracked error rates and latency as they have returned to baseline, and confirm full resolution of the ASR issues affecting the EU Residency region.

We have released an update to resolve this issue.

We have confirmed full issue resolution.

The issue has been resolved, and the system is now showing the correct message.

We have taken measures to restore full SIP functionality and tracked error rates as they have returned to baseline.

The issue has been fixed; this affected only newly created accounts today. Impact is less than 100 workspaces.

The issue has been resolved, and all the voices should be visible now. This only affected workspaces with 50,000 or more voices.

The root cause was an incompatibility in how ElevenLabs handled mid-dialog re-INVITEs. When SIP providers sent re-INVITEs, ElevenLabs responded with 488, which some providers treat as fatal, issue a BYE, and terminate the call. Per RFC 3261, a 488 should not necessarily result in session termination, but provider behaviour varied.

The issue has been fully resolved. The issue was only with the calls on the EU Residency.

We were able to identify the root cause of the increase in errors. We have implemented a fix to mitigate any possible occurrences moving forward.

EU Residency:

Starting Saturday, March 14th at approximately 17:00 UTC, some calls were affected by connection failures, or connected with silent audio. This was fully resolved at 08:00 UTC on March 16th.

Cross-Region:

Starting Sunday, March 15th at approximately 01:00 UTC, some conversations experienced a 1 second delay to initial audio. In some cases, this caused disconnections due to how some SIP trunks handled the audio delay. This issue was fully resolved at 16:00 UTC on March 16th.

Our team has resolved the issue, services are back to normal.

We have confirmed full functionality of both EU and IN residency webpages.

We have confirmed with affected clients and in our analytics that SIP trunking functionality is now fully restored.

We have confirmed fully restored functionality of the voice of "George".

The issue has been 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.

Error rates have returned to the baseline.

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.

The issue has been resolved.