Recorded Future Outage History

Recorded Future is up right now

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

There were 9 Recorded Future outages since September 30, 2025 totaling 639h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.recordedfuture.com

Major August 21, 2026

Attack Surface Intelligence disruptions

Detected by Pingoru
Aug 21, 2026, 06:15 AM UTC
Resolved
Aug 21, 2026, 07:28 AM UTC
Duration
1h 12m
Affected: Attack Surface Intelligence
Timeline · 2 updates
  1. investigating Aug 21, 2026, 06:15 AM UTC

    Dear customers, We are currently investigating an issue affecting access to the Attack Surface Intelligence, which may result in errors for some users. Our team is actively working to resolve this as quickly as possible. We will post an update once normal performance is restored. In the meantime, if you have any questions or concerns, please reach out to our Support team at [email protected]. Thank you for your patience, Recorded Future Platform Operations

  2. resolved Aug 21, 2026, 07:28 AM UTC

    Dear customers, The issue affecting access to the Attack Surface Intelligence has been resolved, and the service is now operating normally. We apologize for any inconvenience this may have caused. If you continue to experience any issues, please contact our support team at [email protected]. Thank you for your patience, Recorded Future Platform Operations

Read the full incident report →

Notice August 2, 2026

Portal Disruption of Service

Detected by Pingoru
Aug 02, 2026, 05:41 PM UTC
Resolved
Aug 02, 2026, 05:41 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 02, 2026, 05:41 PM UTC

    Dear Customer, We recently experienced a service disruption regarding a series of Recorded Future Alerts. Our Platform Operations team recognized the disruption and worked quickly to resolve this incident. Between roughly 13:45-16:45 UTC on August 1st, a series of Alerts could not be generated. We are still investigating the initial cause. While services remain operational, a post-mortem will be updated once our investigation has completed. Please contact our support team at [email protected] if you have any questions. 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 →