Incidentsby IbisSIEM - Delayed Investigation Creation
May 5, 14:48 UTCMay 5, 16:43 UTC
Duration
1h 55m
Impact
Minor
Root cause
Not disclosed
Rapid7, 90 days
9 incidents
Affected
Data ProcessingSIEM (US1) - Data ProcessingSIEM (EU) - Data ProcessingSIEM (CA) - Data ProcessingSIEM (AU) - Data ProcessingSIEM (AP) - Data ProcessingSIEM (US2) - Data ProcessingSIEM (US3) - Data Processing
Final update
Update: Replay of impacted alerts for all regions has been completed.
Timeline
- Resolved · May 5, 16:43 UTC
Update: Replay of impacted alerts for all regions has been completed.
- Identified · May 5, 15:58 UTC
Update: Replay of impacted alerts for the CA and AP regions has been completed.
- Identified · May 5, 15:08 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.
- Identified · May 5, 14:48 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.
More from Rapid7
Full historyVulnerability Management Increased Latencylasted 1h 38mAlert and Investigation Creation Delayslasted 43mVulnerability Management - Dashboard and Reporting Degradationlasted 1h 53mVulnerability Management - Dashboard and Reporting Degradationlasted 25mCommand Platform Dashboard Degraditionlasted 32mRapid7 Customer Portal Degradationlasted 7h 4m