Retell AI incident

Concurrency values were not resetting as expected.

Resolved on August 25, 2025.

resolved Aug 25, 2025, 07:15 PM UTC

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.

Started: Aug 25, 2025, 07:15 PM UTC
Resolved: Aug 25, 2025, 07:15 PM UTC
Duration: –
Detected by Pingoru: Aug 25, 2025, 07:15 PM UTC

Update timeline

resolved Aug 25, 2025, 07:15 PM UTC

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.

Your product runs on more than Retell AI

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.