Recorded Future Outage History

13 incidents recorded over the last 365 days, 13 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Recorded Future status100.00% uptime history

Every Recorded Recorded Future Incident

Recorded Future incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 29, 2026Portal disruption of serviceDear 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…2 minResolved
Aug 21, 2026Attack Surface Intelligence disruptionsDear 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…1h 12mResolved
Aug 2, 2026Portal Disruption of ServiceDear 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…0 minResolved
Jul 30, 2026Portal Disruption of Service**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…6h 20mResolved
Jul 9, 2026Portal Disruption of Service**Issue:**   * Between 07:34 and 08:01 UTC on July 9, 2026 customers experienced intermittent ability to log into Recorded Future’s application interface.   **Cause:**   * A backend service contained a…26 minResolved
May 8, 2026Portal Disruption of Service**Issue:**   * Between 00:00 and 01:56 UTC on May 8, 2026 customers experienced intermittent access and performance issues with the Recorded Future Platform. **Cause:**   * Recorded Future’s cloud partner experienced…7h 29mResolved
Mar 29, 2026Portal Disruption of ServiceDear 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…7h 28mResolved
Mar 5, 2026Recorded Future ASI disruption of serviceThe incident has been resolved, and Attack Surface Module has returned to normal performance.2h 17mResolved
Feb 26, 2026Code Repository Collection DisruptionDear 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…630h 4mResolved
Jan 21, 2026SendGrid Email Alert Delivery Disruption* **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…2h 14mResolved
Nov 12, 2025Delay in content processing**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…-23283 minResolved
Nov 12, 2025Recorded Future AI Disruption of Service* **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…2h 34mResolved
Nov 5, 2025Portal Disruption of Service* **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…1h 10mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Recorded Future incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Recorded Future Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Recorded Future acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Recorded Future outage in this window ran 26d 6h, against a mean recovery of 2d 7h. If you depend on Recorded Future in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.