Retell AI incident

Concurrency values were not resetting as expected.

Notice Resolved View vendor source →

Retell AI experienced a notice incident on August 25, 2025, lasting —. The incident has been resolved; the full update timeline is below.

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

  1. 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.