Inbound Twilio calls experiencing intermittent connection failures

lowElevenLabsAug 18, 2026 12:40
apiconfigurationrouting
Configuration ErrorNetwork / RoutingAPI Issue

Summary

Inbound calls are currently operational.

Impact

minor

Timeline

Aug 18, 2026 12:39

[identified] From ~07:00 UTC, a small percentage 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.

via statuspage
+0m
Aug 18, 2026 12:39

[identified] 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.

via statuspage
+4m
Aug 18, 2026 12:43

[resolved] Inbound calls are currently operational.

via statuspage

Lessons Learned

ElevenLabs has experienced 60 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.

📊Incidents related to api, configuration, routing have occurred 1036 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.

💡This incident is categorized as: Configuration Error, Network / Routing, API Issue. Consider implementing preventive measures specific to this failure category.