Störungsverlauf von Rapid7

1. 3. September 2026 um 22:31 UTCidentified

   Wir untersuchen derzeit ein Problem, das sich auf Exposure Command Platform Experiences auswirkt. Kunden können Latenz und Fehler auftreten. Unsere Engineering-Teams überwachen aktiv ein damit verbundenes Lieferantenproblem und konzentrieren sich auf die Wiederherstellung des normalen Service. Updates werden hier veröffentlicht, sobald sie verfügbar sind.

2. 3. September 2026 um 22:33 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 3. September 2026 um 22:37 UTCmonitoring

   Wir werden weiterhin auf weitere Probleme achten.

4. 3. September 2026 um 22:40 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 18. August 2026 um 16:41 UTCinvestigating

   Wir werden planmäßige Wartungsarbeiten an SIEM/Sammler am 19/08/2026 17:00 Uhr durchführen UTC - 19/08/2026 18:00 Uhr UTC. Während dieser Zeit können Kunden erleben Sammler vorübergehende Stopp der Sammlung. Auswirkung: Anhalten der Sammlung bei allen Sammlerquellen für 5-10 Minuten. Worst-Case-Szenario: Collector geht offline bis zum manuellen Eingriff Wir schätzen Ihre Geduld und Ihr Verständnis, während wir daran arbeiten, die Zuverlässigkeit und Leistung unserer Dienstleistungen zu verbessern.

2. 19. August 2026 um 17:03 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 19. August 2026 um 17:55 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. August 2026 um 15:44 UTCinvestigating

   Wir werden planmäßige Wartungsarbeiten an SIEM/Sammler am 18.08.2026 16:00 Uhr durchführen UTC - 18/08/2026 17:00 Uhr UTC. Während dieser Zeit können Kunden erleben Sammler vorübergehende Stopp der Sammlung. Auswirkung: Anhalten der Sammlung bei allen Sammlerquellen für 5-10 Minuten. Worst-Case-Szenario: Collector geht offline bis zum manuellen Eingriff Wir schätzen Ihre Geduld und Ihr Verständnis, während wir daran arbeiten, die Zuverlässigkeit und Leistung unserer Dienstleistungen zu verbessern.

2. 18. August 2026 um 16:04 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 18. August 2026 um 16:08 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 18. August 2026 um 16:55 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. August 2026 um 16:09 UTCinvestigating

   We are investigating reports of API issues in the EU region

2. 14. August 2026 um 17:00 UTCresolved

   This incident has been resolved.

1. 13. August 2026 um 15:37 UTCinvestigating

   We will be performing scheduled maintenance on SIEM/Collectors on 14/08/2026 16:00 PM UTC - 14/08/2026 17:00 PM UTC. During this time, customers may experience collector temporary stopping of collection. Impact: collection stopping on all collector based sources for 5-10 minutes. Worst case scenario: Collector goes offline until manual intervention We appreciate your patience and understanding as we work to improve the reliability and performance of our services.

2. 14. August 2026 um 16:01 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 14. August 2026 um 17:00 UTCresolved

   This incident has been resolved.

1. 3. August 2026 um 16:55 UTCinvestigating

   **Degradierte Leistung – Verarbeitung von Erkennungsereignissen (US-1)** Wir erleben derzeit langsamere Verarbeitungszeiten für Detection Events in der US-1-Region. Unser Team wurde benachrichtigt und untersucht das Problem aktiv. Andere Regionen sind derzeit nicht betroffen. Wir werden ein weiteres Update bereitstellen, sobald weitere Informationen verfügbar sind.

2. 3. August 2026 um 16:58 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 3. August 2026 um 17:45 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. Juni 2026 um 13:22 UTCinvestigating

   We are currently investigating reports of platform access issues for Threat Intelligence.

2. 12. Juni 2026 um 14:42 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 12. Juni 2026 um 15:40 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 14. Juni 2026 um 16:42 UTCresolved

   All systems have recovered and are confirmed as operating as normal.

1. 21. Mai 2026 um 15:49 UTCmonitoring

   We are aware of an issue that presented with viewing and adding comments to SIEM investigations. Our engineering has identified the issue and implemented a solution. We are actively monitoring performance.

2. 21. Mai 2026 um 16:02 UTCresolved

   This incident has been resolved.

1. 12. Mai 2026 um 10:22 UTCinvestigating

   We are currently investigating an issue impacting APIv4 and Bulk Export API used by Vulnerability Management. We appreciate your patience as we work to restore full functionality!

2. 12. Mai 2026 um 10:29 UTCidentified

   We have identified the cause of the issue impacting APIv4 and Bulk Export API used by Vulnerability Management, we are also investigating a related issue impacting SIEM. We expect resolution by 11:35am UTC+1. We appreciate your patience as we work to restore full functionality!

3. 12. Mai 2026 um 10:30 UTCmonitoring

   A fix has been implemented, our monitoring indicates recovery. We continue to monitor this incident.

4. 12. Mai 2026 um 10:44 UTCresolved

   This incident has been resolved.

1. 8. Mai 2026 um 02:05 UTCinvestigating

   We are currently investigating intermittent issues in the agent management UI and delays in SIEM data processing.

2. 8. Mai 2026 um 02:24 UTCidentified

   We have identified the issue as a vendor dependency. We are working closely with the provider to restore full service.

3. 8. Mai 2026 um 04:51 UTCmonitoring

   Functionality has been restored, and systems are now operating normally. We are monitoring to ensure full stability.

4. 8. Mai 2026 um 12:49 UTCresolved

   This incident has been resolved.

1. 5. Mai 2026 um 14:48 UTCidentified

   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. 5. Mai 2026 um 15:08 UTCidentified

   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. 5. Mai 2026 um 15:58 UTCidentified

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

4. 5. Mai 2026 um 16:43 UTCresolved

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

1. 24. April 2026 um 11:21 UTCinvestigating

   We are currently investigating a slowdown in processing Alerts and creating investigations in ap-southeast-2 and eu-central-1 regions.

2. 24. April 2026 um 12:37 UTCinvestigating

   Impacted services have been scaled to process the backlog of investigations and are now fully caught up. We will continue to closely monitor service health to ensure ongoing stability.

3. 24. April 2026 um 12:38 UTCmonitoring

   Impacted services have been scaled to process the backlog of investigations and are now fully caught up. We will continue to closely monitor service health to ensure ongoing stability.

4. 27. April 2026 um 14:51 UTCresolved

   We have confirmed that all processing is up to date and operating as normal.

1. 17. April 2026 um 17:17 UTCinvestigating

   We are currently investigating an issue where InsightAppSec scans are failing to initiate or complete successfully.

2. 17. April 2026 um 18:09 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 17. April 2026 um 19:05 UTCresolved

   This incident has been resolved.

1. 15. April 2026 um 16:19 UTCidentified

   We have identified an issue impacting Attack Surface Management (Surface Command). Customers may experience failure of the Command Platform import feed. Our engineering teams have identified the root cause, applied the remediation and are actively restarting the impacted import feed due by 17:30 UTC - the time to completion of the import feed will vary based upon your environment size. Updates will be posted here as they become available.

2. 15. April 2026 um 17:18 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 15. April 2026 um 18:34 UTCresolved

   This incident has been resolved.

1. 13. April 2026 um 15:55 UTCinvestigating

   We are investigating an issue affecting the Automation Reporting Homepage at the primary landing page. Specific metrics, including "Time Saved" and "Time to Human Decision," are currently failing to load on this dashboard. Historical data remains secure on the backend, but we are currently verifying if new data is being successfully recorded. While these visual indicators are not appearing in the UI, users can still access reporting metrics through other areas of the product.

2. 13. April 2026 um 16:33 UTCidentified

   The root cause has been identified and our teams are actively working on a remediation. While these visual indicators are currently absent from the UI, historical data remains secure on the backend. We have confirmed that no data is being lost during this period; once the fix is deployed, all missing data will be backfilled and restored to the dashboard.

3. 13. April 2026 um 16:35 UTCidentified

   We are continuing to work on a fix for this issue.

4. 14. April 2026 um 15:57 UTCidentified

   We are continuing to work on the fix for this issue. Our engineering teams have established a clear path to recovery, and we can confirm that all missing data will be backfilled automatically. No action is required from customers at this time, as metrics will be restored to the dashboard as soon as the remediation is deployed.

5. 15. April 2026 um 16:09 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

6. 15. April 2026 um 17:43 UTCresolved

   This incident has been resolved.

1. 13. April 2026 um 15:45 UTCinvestigating

   We are currently investigating an issue affecting Command Platform Login and Navigation between Command Platform Experiences. Customers may experience login latency and latency navigating through the User Interface. Our engineering teams are actively working to identify the cause and restore normal service.  Updates will be posted here as they become available.

2. 13. April 2026 um 16:14 UTCmonitoring

   A fix has been implemented and we are continuing to monitor our recovery.

3. 13. April 2026 um 16:35 UTCresolved

   This incident has been resolved. Thank you for your patience and cooperation as we investigated and remediated.

1. 9. April 2026 um 05:12 UTCinvestigating

   Some customers in US East and US West are experiencing a higher than normal volume of investigations.  The issue is no longer occurring, however we are looking into alerts received within the timeframe - 6pm to 12:30am UTC. If you believe you have been affected by this issue, please log a support case with the subject line: increased-investigation-volume.

2. 9. April 2026 um 08:55 UTCmonitoring

   Between 6:00 PM and 12:30 AM UTC, customers in the US East and US West regions experienced a higher than normal volume of investigations. This issue has been resolved and systems are performing normally. For our managed customers, the SOC is currently processing the remaining backlog of investigations

3. 9. April 2026 um 21:28 UTCresolved

   This incident has been resolved.

1. 13. März 2026 um 17:59 UTCinvestigating

   We are currently investigating an issue impacting log-in to the Command Platform.

2. 13. März 2026 um 18:31 UTCmonitoring

   We have recovered, and login is now accessible across all regions we continue to monitor the situation.

3. 13. März 2026 um 19:59 UTCresolved

   This incident has been resolved.

1. 11. März 2026 um 15:09 UTCidentified

   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.

2. 11. März 2026 um 15:36 UTCmonitoring

   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. 18. März 2026 um 20:24 UTCresolved

   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.

1. 11. März 2026 um 14:48 UTCinvestigating

   We are currently investigating an issue with an upgrade to collectors in the EU and US East 1 regions

2. 11. März 2026 um 16:56 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 11. März 2026 um 22:28 UTCidentified

   The issue has been identified by our Engineering team and a fix is being tested.

4. 12. März 2026 um 02:23 UTCidentified

   We are continuing to work on a fix for this issue.

5. 12. März 2026 um 02:26 UTCmonitoring

   A fix has now been implemented and we are monitoring the results.

6. 16. März 2026 um 10:55 UTCmonitoring

   We continue to monitor the results of the fix implemented.

7. 18. März 2026 um 08:43 UTCresolved

   This incident has been resolved.