ElevenLabs incident: Inbound Twilio calls experiencing intermittent connection failures

1. resolvedAug 18, 2026, 12:43 UTC

   Inbound calls are currently operational.

2. identifiedAug 18, 2026, 12:39 UTC

   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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in ElevenLabs's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• Akamai: Connection drops and increased latency in MiamiMinor · Aug 13, 2026, 19:31 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Twilio: SMS Delivery Failures from Twilio to Telemat Cel BrazilMinor · Aug 15, 2026, 12:55 UTC
• HashiCorp Vault: Delayed HCP Terraform RunsMinor · Aug 15, 2026, 17:08 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Twilio: SMS Delivery Delays from Twilio to Free Caraibe FranceMinor · Aug 18, 2026, 00:33 UTC
• Twilio: SMS Delivery Failures from Twilio to Lycamobile United KingdomMinor · Aug 18, 2026, 10:14 UTC

How often does ElevenLabs have incidents?

ElevenLabs reported 19 incidents in the last 90 days, 6 of them major or critical. A typical incident lasted 1h 34m. See ElevenLabs's uptime and incident history