Recorded Future incident

Portal Disruption of Service

Major Resolved View vendor source →

Recorded Future experienced a major incident on November 5, 2025 affecting User Interface and API and 1 more component, lasting 1h 10m. The incident has been resolved; the full update timeline is below.

Started
Nov 05, 2025, 11:40 AM UTC
Resolved
Nov 05, 2025, 12:50 PM UTC
Duration
1h 10m
Detected by Pingoru
Nov 05, 2025, 11:40 AM UTC

Affected components

User InterfaceAPIMobile applicationBrowser Extension

Update timeline

  1. investigating Nov 05, 2025, 11:40 AM UTC

    Dear Customer, We are currently experiencing a service disruption with the Recorded Future application portal & Mobile Application. Our product operations team are actively working on restoring accessibility to an optimal level of service. We will continue to provide updates as they become available. Please contact our support team at [email protected] if you have any questions. Regards, Recorded Future Platform Operations

  2. investigating Nov 05, 2025, 11:56 AM UTC

    The application portal, API, and Mobile applications are functional, performance is improving but is not yet returned to full speed. We will continue to provide updates as they become available. Please contact our support team at [email protected] if you have any questions. Regards, Recorded Future Platform Operations

  3. resolved Nov 05, 2025, 12:50 PM UTC

    The incident has been resolved, and the User Interface has returned to normal performance. The root cause has been identified, and corrective actions are being implemented.

  4. postmortem Dec 03, 2025, 12:57 PM UTC

    * **Issue:** * Between 11:40 UTC and 12:50 UTC on November 5, 2025, Recorded Future Application Portal and Mobile Application experienced performance degradation. From 11:30 - 11:57 UTC, some users experienced access issues. * **Cause:** * The issue was traced to a malfunctioning service that caused an overload of the user interface. * **Remediation / Path Forward:** * The underlying issues has been resolved and the service has been scaled appropriately to prevent recurrence.