Twilio incident

Intermittent Failures to Update Call Recordings

Minor Resolved View vendor source →

Twilio experienced a minor incident on August 28, 2026 affecting Voice REST API US1, lasting 5h 12m. The incident has been resolved; the full update timeline is below.

Started
Aug 28, 2026, 05:31 PM UTC
Resolved
Aug 28, 2026, 10:43 PM UTC
Duration
5h 12m
Detected by Pingoru
Aug 28, 2026, 05:31 PM UTC

Affected components

Voice REST API US1

Update timeline

  1. identified Aug 28, 2026, 05:31 PM UTC

    Our engineers have identified the issue where a small set of in progress call recordings cannot be modified and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available.

  2. identified Aug 28, 2026, 06:32 PM UTC

    Our engineers have identified the issue where a small set of in progress call recordings cannot be modified and a small set of calls modification will not work and are working to deploy a fix. We expect to provide another update in 2 hour or as soon as more information becomes available.

  3. identified Aug 28, 2026, 08:47 PM UTC

    Our engineers have identified the issue where a small set of in progress call recordings cannot be modified and a small set of calls modification will not work and are working to deploy a fix. We expect to provide another update in 4 hours or as soon as more information becomes available.

  4. monitoring Aug 28, 2026, 09:42 PM UTC

    In progress call recording and call modification are now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  5. monitoring Aug 28, 2026, 10:12 PM UTC

    In progress call recording and call modification are now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  6. resolved Aug 28, 2026, 10:43 PM UTC

    In progress call recording and call modification are operating normally at this time. This incident has been resolved.