Recorded Future incident

Delay in content processing

Notice Resolved View vendor source →

Recorded Future experienced a notice incident on November 12, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Nov 12, 2025, 02:03 AM UTC
Resolved
Oct 26, 2025, 10:00 PM UTC
Duration
Detected by Pingoru
Nov 12, 2025, 02:03 AM UTC

Update timeline

  1. resolved Nov 12, 2025, 02:03 AM UTC

    Dear Customer, Collection and analysis of content is now current and systems that process new content in Recorded Future are operating normally. We apologize for the delays earlier. Please contact our support team at [email protected] if you have any questions. Regards, Recorded Future Platform Operations

  2. postmortem Nov 12, 2025, 02:04 AM UTC

    **Issue:** * Between 21:56 and 22:08 UTC on October 27, 2025, Recorded Future's data processing system experienced a maximum delay of 72 minutes. This delay directly impacted the timeliness of data availability for users. **Cause:** * The root cause of the data processing delay was a loss of synchronization within the message queue cluster, triggered by a network interruption. The unsynchronized state led the message queue cluster to become unresponsive, halting the normal processing of data, resulting in the eventual 72-minute data delay. **Remediation / Path Forward:** * Manually restored cluster integrity. This action successfully restored the cluster integrity and brought the data processing back online.