- 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-10-02 20:27 UTC and 2025-10-02 13:30 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
Incident range: 6:30am - 11am PST impact: around 7% of the calls are having abnormally high latency post mortem: Some AWS automatic patches to our transcription clusters caused the container to lost GPU access, and used CPU for transcription, causing extra long latency there. Most calls are routed to the backup endpoint which was working fine, but around 7% did not trigger the fallback there. We are updating the containers to ensure it does not get impacted with the automatic patches.
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-72aa9ee723
Is Retell AI still down?
No, this incident was resolved 2025-10-02 13:30 UTC. For Retell AI's live state, see https://down.guide/retell.
How long did it last?
0m, from 2025-10-02 20:27 UTC to 2025-10-02 13:30 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.