ElevenLabs incident
[EU] Multiple US endpoints experiencing timeouts and latency
ElevenLabs experienced a minor incident on October 13, 2026 affecting Other APIs and Conversations and 1 more component, lasting 4h 57m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 13, 2026, 09:21 AM UTC
Status: Investigating 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. Affected components Other APIs (Partial outage) UI (Partial outage) Integrations (Partial outage) Conversations (Partial outage) Telephony (Partial outage) RAG (Partial outage) Quality (Partial outage)
- resolved Oct 13, 2026, 09:47 AM UTC
Status: Resolved 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. Affected components Telephony (Operational) RAG (Operational) Quality (Operational) Other APIs (Operational) UI (Operational) Integrations (Operational) Conversations (Operational)
- identified Oct 13, 2026, 09:57 AM UTC
Status: Identified We’re seeing error rates rise again, so calls may still fail or experience increased latency. Affected components Telephony (Partial outage) RAG (Partial outage) Quality (Partial outage) Other APIs (Partial outage) UI (Partial outage) Integrations (Partial outage) Conversations (Partial outage)
- monitoring Oct 13, 2026, 10:38 AM UTC
Status: Monitoring 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. Affected components Integrations (Partial outage) Conversations (Partial outage) Telephony (Partial outage) RAG (Partial outage) Quality (Partial outage) Other APIs (Partial outage) UI (Partial outage)
- identified Oct 13, 2026, 11:42 AM UTC
Status: Identified 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. Affected components Telephony (Partial outage) RAG (Partial outage) Quality (Partial outage) Other APIs (Partial outage) UI (Partial outage) Integrations (Partial outage) Conversations (Partial outage)
- identified Oct 13, 2026, 12:54 PM UTC
Status: Identified 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. Affected components Conversations (Partial outage) Telephony (Partial outage) RAG (Partial outage) Quality (Partial outage) Other APIs (Partial outage) UI (Partial outage) Integrations (Partial outage)
- monitoring Oct 13, 2026, 01:42 PM UTC
Status: Monitoring Error rates have continued to stabilize. We are continuing to monitor the affected endpoints to ensure service remains steady. Affected components Integrations (Partial outage) Conversations (Partial outage) Telephony (Partial outage) RAG (Partial outage) Quality (Partial outage) Other APIs (Partial outage) UI (Partial outage)
- resolved Oct 13, 2026, 02:18 PM UTC
Status: Resolved 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. Affected components Telephony (Operational) RAG (Operational) Quality (Operational) Other APIs (Operational) UI (Operational) Integrations (Operational) Conversations (Operational)