Live / Rapid7 / Incident
Rapid7: SIEM - Rapid7 Collector
Rapid7 · rapid7.comMinor incidentResolved2026-11-06 16:26 UTC
Public — what happened
Summary
Rapid7 said that starting on 2026-10-26 at 19:45 UTC, some of its SIEM collectors could appear stuck or unresponsive following a recent update. The company said its engineers found the cause within about an hour, then spent several days working on and testing a fix. Rapid7 said a fix was put in place on 2026-10-30 and it kept monitoring for further problems, and the incident was marked resolved on 2026-11-06 at 16:26.
Affected
Data Processing, Data Processing, Data Processing, Data Processing, Data Processing, Data Processing, Data Processing
Timeline
- Started — 2026-10-26 19:45 UTC
- Investigating — 2026-10-26 19:45 UTC
- Identified — 2026-10-26 20:35 UTC (4 updates)
- Monitoring — 2026-10-30 18:05 UTC (2 updates)
- Resolved — 2026-11-06 16:26 UTC · 11 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Rapid7 against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Rapid7: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Rapid7 report →
More from Rapid7
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.