Retell AI: Phone call not connecting
Cloudflare outage, Jul 14, 2025 · 6 vendors, 6 incidents
Retell AI’s incident blames Cloudflare as the cause. (hop 1, posted +15 min vs the first vendor naming Cloudflare)
“…otential workarounds. Telephony provider confirmed that this is related to an outage with Cloudflare DNS, which they use in certain internal components. A change is being applied to mitigate. related…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Cloudflare<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>2 vendors, 2 blamed Cloudflare<br/>Cursor, Retell AI"]:::blames
root --> h1
me["Retell AI (this incident)<br/>posted +15 min"]:::me
h1 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: End to End Calling - TelephonyPhone Call
Timeline of updates
- investigating
Our telephony SIP provider confirmed there's an ongoing outage that led to phone call not connecting. We are escalating now, and is trying potential workarounds.
- identified
Telephony provider confirmed that this is related to an outage with Cloudflare DNS, which they use in certain internal components. A change is being applied to mitigate. related incident: https://www.cloudflarestatus.com/incidents/28r0vbbxsh8f
- identified
We are continuing to work on a fix for this issue.
- monitoring
The fix has been applied and phone calls are back to normal at the moment, we are keep monitoring.
- monitoring
We are continuing to monitor for any further issues.
- resolved
This incident has been resolved.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).