Rapid7 incident

Automation Reporting Homepage Dashboard Issue

Minor Resolved View vendor source →

Rapid7 experienced a minor incident on April 13, 2026 affecting User Interface and User Interface and 1 more component, lasting 2d 1h. The incident has been resolved; the full update timeline is below.

Started
Apr 13, 2026, 03:55 PM UTC
Resolved
Apr 15, 2026, 05:43 PM UTC
Duration
2d 1h
Detected by Pingoru
Apr 13, 2026, 03:55 PM UTC

Affected components

User InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser Interface

Update timeline

  1. investigating Apr 13, 2026, 03:55 PM UTC

    We are investigating an issue affecting the Automation Reporting Homepage at the primary landing page. Specific metrics, including "Time Saved" and "Time to Human Decision," are currently failing to load on this dashboard. Historical data remains secure on the backend, but we are currently verifying if new data is being successfully recorded. While these visual indicators are not appearing in the UI, users can still access reporting metrics through other areas of the product.

  2. identified Apr 13, 2026, 04:33 PM UTC

    The root cause has been identified and our teams are actively working on a remediation. While these visual indicators are currently absent from the UI, historical data remains secure on the backend. We have confirmed that no data is being lost during this period; once the fix is deployed, all missing data will be backfilled and restored to the dashboard.

  3. identified Apr 13, 2026, 04:35 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Apr 14, 2026, 03:57 PM UTC

    We are continuing to work on the fix for this issue. Our engineering teams have established a clear path to recovery, and we can confirm that all missing data will be backfilled automatically. No action is required from customers at this time, as metrics will be restored to the dashboard as soon as the remediation is deployed.

  5. monitoring Apr 15, 2026, 04:09 PM UTC

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

  6. resolved Apr 15, 2026, 05:43 PM UTC

    This incident has been resolved.