- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on ElevenLabs. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-10-21 17:30 UTC and 2026-08-18 12:43 UTC may need a replay.Subscribe to ElevenLabs's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=elevenlabs works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from ElevenLabs 2
- 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.
provider
- resolved
Inbound calls are currently operational.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-e81014c463
Is ElevenLabs still down?
No, this incident was resolved 2026-08-18 12:43 UTC. For ElevenLabs's live state, see https://down.guide/elevenlabs.
How long did it last?
0m, from 2026-10-21 17:30 UTC to 2026-08-18 12:43 UTC, by the times ElevenLabs posted.
What caused it?
ElevenLabs hasn't published a root cause. If it does, it shows here.
Where does this come from?
ElevenLabs's official status page, https://status.elevenlabs.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.