Delays Viewing and Receiving Operator Results in Conversation Intelligence and Accessing Conversation Memory

What to do

• Check whether you use Twilio Conversation Intelligence, Conversation Intelligence (classic), Conversation Memory. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 55m it lasted.

  Anything that failed between 2026-10-06 20:16 UTC and 2026-10-06 21:11 UTC may need a replay.

• Subscribe to Twilio's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Twilio 4

1. investigatingOct 6, 2026, 8:16 PM UTC

   Our monitoring systems have detected a potential issue with Conversation Intelligence. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

   provider

2. investigatingOct 6, 2026, 8:30 PM UTC

   Our engineering team is currently investigating an issue that affects our Conversation Intelligence and Conversation Memory features. Affected users will be unable to view and receive new results from GenAI Language Operators and access new Memories and Observations in Conversation Memory. We will provide another update in 1 hour, or as soon as more information is available.

   provider

3. monitoringOct 6, 2026, 8:55 PM UTC

   Our engineers have mitigated the incident. Memory and Intelligence v3 events are now publishing. Between the time of 12:33pm PT - 1:29pm PT Memory and Intelligence v3 events were not published. We are monitoring to ensure there is no further impact.

   provider

4. resolvedOct 6, 2026, 9:11 PM UTC

   Memory and Intelligence v3 continue to operate normally. This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.