Recorded Future incident
Recorded Future Sandbox Service Disruption
Recorded Future experienced a critical incident on July 15, 2025 affecting Sandbox, lasting 14m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 15, 2025, 06:48 AM UTC
Dear Customer, We are currently experiencing a service disruption to our Sandbox feature, with access currently unavailable on sandbox.recordedfuture.com and private.tria.ge . We're currently reviewing the incident with high urgency, and 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
- investigating Jul 15, 2025, 07:02 AM UTC
Dear Recorded Future Customers, We want to inform you that the Sandbox service disruption and degraded performance have now been resolved. System performance and response times are back to normal. Please contact our support team at [email protected] if you have any questions or concerns. Regards, Recorded Future Platform Operations
- resolved Jul 15, 2025, 07:02 AM UTC
This incident has been resolved.
- postmortem Jul 23, 2025, 08:56 PM UTC
* **Issue:** * At approximately 6:25 UTC on July 15th, we received several reports that the Recorded Future Sandbox \(specifically [sandbox.recordedfuture.com](http://sandbox.recordedfuture.com)\), was unavailable, which was confirmed by our operations team. * **Cause:** * The root cause of the incident was a configuration error. * **Remediation / Path Forward:** * At approximately 6:48 UTC, a formal incident was opened for client communications, with the root cause being identified shortly thereafter. The correct Sandbox configurations were applied, with the incident being marked as resolved at approximately 7:02 UTC. As a path forward, new monitoring checks were added to alert for any future configuration discrepancies.