Increased Investigation Volume
Incident Lifecycle
Incident Timeline
Monitoring
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 evalua...
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 evalua...
Mar 11, 2026 at 3:36 PM UTC
Identified
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.
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.
Mar 11, 2026 at 3:09 PM UTC
Was your business affected by this Rapid7 outage?
Set up instant alerts for Rapid7 — be the first to know about outages via email, Slack, Teams, or Discord.