Rapid7 incident

SIEM - Delayed Investigation Creation

Minor Resolved View vendor source →
Started
May 05, 2026, 02:48 PM UTC
Resolved
May 05, 2026, 04:43 PM UTC
Duration
1h 55m
Detected by Pingoru
May 05, 2026, 02:48 PM UTC

Affected components

Data ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData Processing

Update timeline

  1. identified May 05, 2026, 02:48 PM UTC

    We have identified an issue that caused delays in the creation of Investigations for SIEM (InsightIDR) and Managed Detection and Response customers. A fix has been deployed. Investigations that should have been created between 11:25 and 13:50 UTC on May 5, 2026 may still be delayed. We are actively replaying impacted alerts and working to ensure all missing Investigations are generated as quickly as possible.

  2. identified May 05, 2026, 03:08 PM UTC

    Update: For Managed Detection and Response (MDR) customers, Rapid7 Managed alerts were not impacted. However, Custom and Contextual alerts (not triaged by the Rapid7 SOC) may have experienced delays in Investigation creation during this time window.

  3. identified May 05, 2026, 03:58 PM UTC

    Update: Replay of impacted alerts for the CA and AP regions has been completed.

  4. resolved May 05, 2026, 04:43 PM UTC

    Update: Replay of impacted alerts for all regions has been completed.

Looking to track Rapid7 downtime and outages?

Pingoru polls Rapid7's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Rapid7 reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Rapid7 alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Rapid7 for free

5 free monitors · No credit card required