Twilio incident

Errors Impacting Real-Time Transcriptions, Conversation Relay, <Gather> Voice TwiML

Minor Resolved View vendor source →

Twilio experienced a minor incident on September 12, 2026 affecting Speech Recognition (Gather Speech) US1, lasting 2h 47m. The incident has been resolved; the full update timeline is below.

Started
Sep 12, 2026, 09:25 PM UTC
Resolved
Sep 13, 2026, 12:12 AM UTC
Duration
2h 47m
Detected by Pingoru
Sep 12, 2026, 09:25 PM UTC

Affected components

Speech Recognition (Gather Speech) US1

Update timeline

  1. investigating Sep 12, 2026, 09:25 PM UTC

    Our engineering team has observed an increase in error rates affecting our Real-Time Transcriptions, Conversation Relay, and Voice TwiML products. We will provide another update in 1 hour or as soon as more information becomes available.

  2. identified Sep 12, 2026, 09:27 PM UTC

    Our engineering team has observed an increase in error rates affecting our Real-Time Transcriptions, Conversation Relay, and Voice TwiML products. We will provide another update in 1 hour or as soon as more information becomes available.

  3. identified Sep 12, 2026, 10:12 PM UTC

    Our engineering team has observed an increase in error rates affecting our Real-Time Transcriptions, Conversation Relay, and Voice TwiML products using the Deepgram model. Customers experiencing issues should use the Google model as a workaround. We will provide another update in 1 hour or as soon as more information becomes available.

  4. monitoring Sep 12, 2026, 11:12 PM UTC

    We are observing recovery across our Real-Time Transcriptions, Conversation Relay, and Voice TwiML products when using the Deepgram model. We will continue monitoring affected services to ensure a full recovery. We will provide another update in 2 hours or as soon as more information becomes available.

  5. resolved Sep 13, 2026, 12:12 AM UTC

    We are no longer experiencing issues with Real-Time Transcriptions, Conversation Relay, and Voice TwiML products when using the Deepgram model. This incident has been resolved.