Who is down right now

Rapid7 · SecurityMar 11, 2026, 15:09 UTC 7 months ago

Increased Investigation Volume

MajorConfig changeUpdated 2h ago
Mar 11, 15:09 UTCMar 18, 20:24 UTC
Duration
7d 5h
Impact
Major
Root cause
Config change
Rapid7, 90 days
9 incidents
Affected
User InterfaceSIEM (US1) - User InterfaceSIEM (EU) - User InterfaceSIEM (CA) - User InterfaceSIEM (AU) - User InterfaceSIEM (AP) - User InterfaceSIEM (US2) - User InterfaceSIEM (US3) - User Interface
Status page

Final update

We have contacted all affected customers via email or their account teams and shared remediation plans for investigations created during the affected window. Our engineering teams have also begun the cleanup process. Please note: We are transitioning to direct updates for impacted customers, and this status page will no longer be updated. If you believe you were affected but have not received communication, please contact Rapid7 Support or reach out to your account team.

Timeline

  1. Resolved · Mar 18, 20:24 UTC
    We have contacted all affected customers via email or their account teams and shared remediation plans for investigations created during the affected window. Our engineering teams have also begun the cleanup process. Please note: We are transitioning to direct updates for impacted customers, and this status page will no longer be updated. If you believe you were affected but have not received communication, please contact Rapid7 Support or reach out to your account team.
  2. Monitoring · Mar 11, 15:36 UTC
    We are aware of an unexpected increase in the number of new investigations being created, starting at 11:00 AM UTC. This was caused by a configuration error that briefly re-enabled a set of legacy detections. We have since disabled these detections and are working to identify and mitigate the impact on user dashboards.This issue impacts SIEM and Services customers. Impact: Users may see a spike in noisy investigations created during this 2-hour window. **Next Steps: We are currently evaluating a bulk cleanup for the noisy investigations.
  3. Identified · Mar 11, 15:09 UTC
    We are aware of an unexpected increase in the number of new investigations being created, starting at 11:00 AM UTC. This was caused by a configuration error that briefly re-enabled a set of legacy detections. We have since disabled these detections and are working to identify and mitigate the impact on user dashboards.This issue impacts SIEM and Services customers. Impact: Users may see a spike in noisy investigations created during this 2-hour window.

More from Rapid7

Full history

Also caused by configuration change

All