Recorded Future experienced a critical incident on July 30, 2026 affecting User Interface, lasting 6h 20m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 30, 2026, 06:55 AM UTC
Dear Customer, We are currently experiencing a service disruption with the Recorded Future application portal. Our Platform 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
- monitoring Jul 30, 2026, 09:24 AM UTC
Dear Customer, We have identified the root of instability and believe we have restored performance to optimal levels. We will continue to monitor to ensure services remain fully available and provide an update when the incident is fully resolved. Please contact our support team at [email protected] if you have any questions. Regards, Recorded Future Platform Operations
- resolved Jul 30, 2026, 01:15 PM UTC
Dear Customer, We are pleased to inform you that the service disruption affecting the Recorded Future application portal has been resolved. All systems are now operating normally. If you have any remaining questions or continue to experience issues, please contact our support team at [email protected]. Regards, Recorded Future Platform Operations
- postmortem Jul 31, 2026, 03:50 AM UTC
**Issue:** Between 06:30 and 08:30 UTC on July 30, 2026, customers experienced intermittent errors and degraded performance in the Recorded Future Platform. **Cause:** An internal content-processing service became unresponsive. Requests dependent on that service queued and timed out, which affected responsiveness across the Platform more broadly. **Remediation:** The affected service was restored and performance returned to normal. We have increased capacity for this service and are implementing additional safeguards to prevent recurrence and improve detection. This was an availability incident only; no Customer Data was impacted.