Twilio incident
Customers Using Conversation Intelligence (Classic) May Experience Delays With Transcript and Operator Results Being Available
Twilio experienced a minor incident on September 24, 2026 affecting Conversation Intelligence, lasting 4h 58m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 24, 2026, 02:37 PM UTC
Our monitoring systems have detected a potential issue with Conversations. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
- investigating Sep 24, 2026, 02:49 PM UTC
Conversation Intelligence (classic) is experiencing issue processing Language Operators which may cause a delay in Operator Results and Transcriptions being available. Twilio Engineers are investigating the issue. We'll provide an update in 1 hour or as soon as more information becomes available.
- monitoring Sep 24, 2026, 03:11 PM UTC
We see recovery with Conversation Intelligence (classic) issue processing Language We'll monitor for 30 minutes.
- identified Sep 24, 2026, 05:09 PM UTC
We are seeing again, delays in Operator Results and Transcriptions being available. We'll provide an update in 1 hour or as soon as more information becomes available.
- monitoring Sep 24, 2026, 06:17 PM UTC
We are now seeing persistent recovery in transcription processing and operator results latency. We'll continue to monitor for 30 minutes
- resolved Sep 24, 2026, 07:35 PM UTC
The incident for Conversation Intelligence (classic) is experiencing issue processing Language Operators which may cause a delay in Operator Results and Transcriptions being available has been resolved and it is operating normally at this time.