Twilio incident

Issue with Stale Observations Results when Querying Memory Recall

Resolved after 2 hours 56 minutes, affecting Conversation Memory, on July 24, 2026.

resolved Jul 25, 2026, 01:43 AM UTC

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

Started
Jul 24, 2026, 10:46 PM UTC
Resolved
Jul 25, 2026, 01:43 AM UTC
Duration
2h 56m
Detected by Pingoru
Jul 24, 2026, 10:46 PM UTC

Affected components

Conversation Memory

Update timeline

  1. identified Jul 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.

  2. monitoring Jul 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.

  3. resolved Jul 25, 2026, 01:43 AM UTC

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

Your product runs on more than Twilio

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →