Recorded Future Outage History

Recorded Future is up right now

Recorded Future had 10 outages in the last 2 years totaling 642h 2m of downtime — averaging 0.4 incidents per month.

There were 10 Recorded Future outages since July 15, 2025 totaling 642h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.recordedfuture.com

Critical July 9, 2026

Portal Disruption of Service

Detected by Pingoru
Jul 09, 2026, 07:34 AM UTC
Resolved
Jul 09, 2026, 08:01 AM UTC
Duration
26m
Affected: User Interface
Timeline · 3 updates
  1. investigating Jul 09, 2026, 07:34 AM UTC

    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

  2. investigating Jul 09, 2026, 07:35 AM UTC

    We are continuing to investigate this issue.

  3. resolved Jul 09, 2026, 08:01 AM 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

Read the full incident report →

Notice March 5, 2026

Recorded Future ASI disruption of service

Detected by Pingoru
Mar 05, 2026, 08:30 PM UTC
Resolved
Mar 05, 2026, 10:47 PM UTC
Duration
2h 17m
Affected: Attack Surface Intelligence
Timeline · 4 updates
  1. investigating Mar 05, 2026, 08:30 PM UTC

    Dear Customer, We are currently experiencing a service disruption with the Recorded Future Attack Surface Intelligence. 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 Mar 05, 2026, 09:58 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 05, 2026, 10:10 PM UTC

    The application is performing as expected. We are continuing to monitor to ensure it remains performant.

  4. resolved Mar 05, 2026, 10:47 PM UTC

    The incident has been resolved, and Attack Surface Module has returned to normal performance.

Read the full incident report →

Major February 26, 2026

Code Repository Collection Disruption

Detected by Pingoru
Feb 26, 2026, 08:43 PM UTC
Resolved
Mar 25, 2026, 02:48 AM UTC
Duration
26d 6h
Affected: Collection and Processing
Timeline · 4 updates
  1. identified Feb 26, 2026, 08:43 PM UTC

    Dear Customer, Starting today, Recorded Future became aware of a disruption in some of its collection of commits to public repositories, with expected intermittent gaps to customers who rely on ingestion of the "Code Repository" source type within queries or alerts. We are actively working to resolve the collection issue, and are actively backfilling any missing data now. We expect to be fully caught up within the next few days, with relevant alerts being triggered retroactively. We will continue to provide updates as they become available, and when the backfill is fully caught up. Please contact our support team at [email protected], or your Technical Account Manager if you have any questions. Regards, Recorded Future Platform Operations

  2. identified Mar 03, 2026, 04:25 PM UTC

    Dear Customer, We wanted to provide an update regarding the disruption and recovery to the code repository collection data. We are still actively working to resolve the collection issue, and expect to be fully caught up within the next 24 hours, with relevant alerts being triggered retroactively. We will continue to provide updates as they become available, and when the backfill is fully caught up. Please contact our support team at [email protected], or your Technical Account Manager if you have any questions. Regards, Recorded Future Platform Operations

  3. monitoring Mar 09, 2026, 08:18 PM UTC

    Dear Customer, We wanted to provide an update as to the disruption and recovery to the code repository collection data, as we are still actively working to resolve the collection issue. While conditions have improved dramatically, we are still in a degraded performance state with data coming in slightly delayed. We will continue to provide updates as they become available, and when the backfill is fully caught up. Please contact our support team at [email protected], or your Technical Account Manager if you have any questions. Regards, Recorded Future Platform Operations

  4. resolved Mar 25, 2026, 02:48 AM UTC

    Dear Customer, Collection and processing of content is now near current, and systems that process new content within Recorded Future are returning to normal operations. We apologize for the delays experienced earlier today. Please contact our support team at [email protected] if you have any questions. Regards, Recorded Future Platform Operations

Read the full incident report →

Major January 21, 2026

SendGrid Email Alert Delivery Disruption

Detected by Pingoru
Jan 21, 2026, 08:55 AM UTC
Resolved
Jan 21, 2026, 11:10 AM UTC
Duration
2h 14m
Affected: Alerts
Timeline · 3 updates
  1. identified Jan 21, 2026, 08:55 AM UTC

    Dear Customer, We are currently addressing a service disruption with our email delivery provider, SendGrid, which may result in delayed or intermittent delivery of automated email alerts. Our engineering team is working urgently with the provider to restore full functionality. Please note that all alerts remain fully accessible via the Recorded Future Portal. This disruption is limited to email delivery only; your real-time data and monitoring within the platform are unaffected. We will notify you as soon as email services are fully restored. Please contact our support team at [email protected] if you have any questions. Thank you for your patience. Regards, Recorded Future Platform Operations

  2. resolved Jan 21, 2026, 11:10 AM UTC

    This incident has been resolved.

  3. postmortem Jan 23, 2026, 07:54 PM UTC

    * **Issue:** * Between 08:55 and 11:10 UTC on January 21, 2026, the Recorded Future portal experienced a service disruption affecting outbound email delivery. * **Cause:** * Our outbound mail partner temporarily disabled mail sending from our domain which was promptly resolved. * **Remediation / Path Forward:** * We have worked extensively with our mail partner to ensure that such disabling actions are not taken in the future and we are also investigating adding backup email sending partners to provide additional resilience.

Read the full incident report →

Notice November 12, 2025

Delay in content processing

Detected by Pingoru
Nov 12, 2025, 02:03 AM UTC
Resolved
Oct 26, 2025, 10:00 PM UTC
Duration
—
Timeline · 2 updates
  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.

Read the full incident report →

Critical November 12, 2025

Recorded Future AI Disruption of Service

Detected by Pingoru
Nov 12, 2025, 01:01 AM UTC
Resolved
Nov 12, 2025, 03:36 AM UTC
Duration
2h 34m
Affected: Recorded Future AI
Timeline · 5 updates
  1. investigating Nov 12, 2025, 01:01 AM UTC

    Dear Customer, We are currently experiencing a service disruption with the Recorded Future AI. 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. monitoring Nov 12, 2025, 01:53 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Nov 12, 2025, 01:53 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Nov 12, 2025, 03:36 AM UTC

    This incident has been resolved.

  5. postmortem Nov 28, 2025, 07:37 PM UTC

    * **Issue:** * Between 20:25 UTC on November 11, 2025 and 01:53 UTC on November 12, 2025, Recorded Future’s AI service experienced slow performance and intermittent outages, affecting the timely delivery and processing of intelligence reports. * **Cause:** * The disruption was caused by a system configuration which did not allow sufficient automatic scaling. * **Remediation / Path Forward:** * Immediate action was taken to update this configuration and we are implementing a comprehensive plan for long-term resilience.

Read the full incident report →

Notice September 30, 2025

Portal disruption of service

Detected by Pingoru
Sep 30, 2025, 03:27 PM UTC
Resolved
Sep 30, 2025, 03:49 PM UTC
Duration
22m
Affected: User InterfaceAPIMobile application
Timeline · 3 updates
  1. investigating Sep 30, 2025, 03:27 PM 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 Sep 30, 2025, 03:46 PM UTC

    Dear Customer, We have resolved a service disruption with the Recorded Future Application and APIs. The disruption occurred between 15:27-15:45 UTC on Tuesday September 30, 2025. Please contact our support team at [email protected] if you have any questions. Regards, Recorded Future Platform Operations

  3. resolved Sep 30, 2025, 03:49 PM UTC

    Dear Customer, We have resolved a service disruption with the Recorded Future Application and APIs. The disruption occurred between 15:27-15:45 UTC on Tuesday September 30, 2025. Please contact our support team at [email protected] if you have any questions. Regards, Recorded Future Platform Operations

Read the full incident report →

Critical August 6, 2025

Degraded Performance - Course Platform Availability

Detected by Pingoru
Aug 06, 2025, 02:55 PM UTC
Resolved
Aug 06, 2025, 05:44 PM UTC
Duration
2h 49m
Affected: Recorded Future University
Timeline · 4 updates
  1. investigating Aug 06, 2025, 02:55 PM UTC

    We are currently investigating this issue.

  2. identified Aug 06, 2025, 03:52 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Aug 06, 2025, 04:45 PM UTC

    Dear Customer, We are currently experiencing a service disruption pertaining to the Recorded Future University training platform, which may result in errors trying to log in to https://university.recordedfuture.com/ . We are currently working with our vendor to resolve this problem as soon as possible. Please note that access to the Recorded Future application platform (https://recordedfuture.com/live) is unaffected, and our support site (https://support.recordedfuture.com/hc/en-us) is still available for additional training content. We will follow up when the system performance returns to normal, but please contact our support team at [email protected] if you have any questions or concerns. Regards, Recorded Future Platform Operations

  4. resolved Aug 06, 2025, 05:44 PM UTC

    Dear Customer, Access to the Recorded Future University training platform is now restored, and the incident is now considered resolved. Please contact our support team at [email protected] if you have any questions or concerns. Regards, Recorded Future Platform Operations

Read the full incident report →

Critical July 15, 2025

Recorded Future Sandbox Service Disruption

Detected by Pingoru
Jul 15, 2025, 06:48 AM UTC
Resolved
Jul 15, 2025, 07:02 AM UTC
Duration
14m
Affected: Sandbox
Timeline · 4 updates
  1. 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

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

  3. resolved Jul 15, 2025, 07:02 AM UTC

    This incident has been resolved.

  4. 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.

Read the full incident report →