- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Retell AI. 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 2025-08-25 19:15 UTC and 2025-08-25 19:15 UTC may need a replay.Subscribe to Retell AI's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=retell works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Retell AI 1
- resolved
Starting from 10:25am to 11:23am, for some customers concurrency was not resetting correctly, causing some calls to fail to connect. We are mitigating the issue by manually resetting concurrency, so the dashboard may not reflect the actual current value. We identified the root cause to be a case where audio file manipulation led to a full disk usage under a corner case scenario, and a fix is deployed.
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-e34637299f
Is Retell AI still down?
No, this incident was resolved 2025-08-25 19:15 UTC. For Retell AI's live state, see https://down.guide/retell.
How long did it last?
0m, from 2025-08-25 19:15 UTC to 2025-08-25 19:15 UTC, by the times Retell AI posted.
What caused it?
Retell AI hasn't published a root cause. If it does, it shows here.
Where does this come from?
Retell AI's official status page, https://status.retellai.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.