56 Rapid7 incidents · 2025年2月 — official updates, affected components, duration and resolution details.
現在、Exposure Command Platform Experiences に関する問題について調査しています。 レイテンシやエラーが発生する場合があります。 当社のエンジニアリングチームは、関連するベンダーの問題を積極的に監視し、通常のサービスを復元することに重点を置いています。 アップデートは随時掲載予定です.
修正を実装し、結果を監視しています.
今後の問題がないか引き続き監視しています。
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
SIEM/コレクターのメンテナンスは19/08/2026 17:00に予定しております。 UTC - 19/08/2026 18:00 午後 ツイート その際、コレクションのコレクター一時停止を体験できます。 影響:コレクションは5〜10分間のすべてのコレクターベースのソースを停止します。 最悪の場合のシナリオ: コレクターは手動介入までオフラインで行きます サービスの信頼性と性能を向上させるために、お客様のご満足とご理解を賜りますようお願い申し上げます.
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
SIEM/コレクターのメンテナンスを18/08/2026 16:00に行います。 UTC - 2018年8月20日 17:00 ツイート その際、コレクションのコレクター一時停止を体験できます。 影響:コレクションは5〜10分間のすべてのコレクターベースのソースを停止します。 最悪の場合のシナリオ: コレクターは手動介入までオフラインで行きます サービスの信頼性と性能を向上させるために、お客様のご満足とご理解を賜りますようお願い申し上げます.
問題が特定され、修正が実装されています.
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
We are investigating reports of API issues in the EU region
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
**劣化性能 – 検出イベント処理(US-1)** 米国1地域における検出イベントの通常の処理時間よりも遅くなっています。 当社のチームは、積極的に問題を調査しています。 上記以外の地域には影響しません。 詳細は、順次更新いたします.
今後もこの問題について調査を続けてまいります.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
We are currently investigating reports of platform access issues for Threat Intelligence.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
All systems have recovered and are confirmed as operating as normal.
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.
This incident has been resolved.
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!
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!
A fix has been implemented, our monitoring indicates recovery. We continue to monitor this incident.
This incident has been resolved.
We are currently investigating intermittent issues in the agent management UI and delays in SIEM data processing.
We have identified the issue as a vendor dependency. We are working closely with the provider to restore full service.
Functionality has been restored, and systems are now operating normally. We are monitoring to ensure full stability.
This incident has been resolved.
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.
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.
Update: Replay of impacted alerts for the CA and AP regions has been completed.
Update: Replay of impacted alerts for all regions has been completed.
We are currently investigating a slowdown in processing Alerts and creating investigations in ap-southeast-2 and eu-central-1 regions.
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.
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.
We have confirmed that all processing is up to date and operating as normal.
We are currently investigating an issue where InsightAppSec scans are failing to initiate or complete successfully.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
We are continuing to work on a fix for this issue.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are continuing to monitor our recovery.
This incident has been resolved. Thank you for your patience and cooperation as we investigated and remediated.
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.
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
This incident has been resolved.
We are currently investigating an issue impacting log-in to the Command Platform.
We have recovered, and login is now accessible across all regions we continue to monitor the situation.
This incident has been resolved.
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.
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.
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.
We are currently investigating an issue with an upgrade to collectors in the EU and US East 1 regions
The issue has been identified and a fix is being implemented.
The issue has been identified by our Engineering team and a fix is being tested.
We are continuing to work on a fix for this issue.
A fix has now been implemented and we are monitoring the results.
We continue to monitor the results of the fix implemented.
This incident has been resolved.