Issue with Stale Observations Results when Querying Memory Recall

What to do

• Check whether you use Twilio 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 2h 57m it lasted.

  Anything that failed between 2026-07-24 22:46 UTC and 2026-07-25 01:43 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 3

1. identifiedJul 24, 2026, 10:46 PM UTC

   Our engineers have identified an issue with Memory Recall and are working to deploy a fix. At this time, profiles with more than 500 observations could see stale observations in their results from Memory Recall. We expect to provide another update in 1 hour or as soon as more information becomes available.

   provider

2. monitoringJul 24, 2026, 11:43 PM UTC

   Observations results in Memory Recall is now operating normally. We will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.

   provider

3. resolvedJul 25, 2026, 1:43 AM UTC

   The issue affecting observation results has been resolved and Memory Recall is operating normally at this time.

   provider

Corrections

None so far.

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