56 Rapid7 incidents · 2025年2月 — official updates, affected components, duration and resolution details.
我们目前正在调查影响接触指挥平台经验的问题。 客户可能会遇到时间过长和错误。 我们的工程小组正在积极监测一个相关的供应商问题,并侧重于恢复正常服务。 更新情况一旦公布,将公布于此.
一项措施已经执行,我们正在监测结果.
我们正在继续监测任何其他问题.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们将在下午7: 00对SIEM/Collectors进行预定的维护 世界协调时-2013年8月19日-下午6:00 协调世界时. 在此期间,顾客可能会遇到收藏家暂时停止收藏的情况. 影响:收集工作停止于所有基于采集源上5-10分钟。 最坏情况:收集器停机,直到人工干预 我们赞赏你的耐心和理解,因为我们努力提高我们服务的可靠性和业绩.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们将在下午4: 00对SIEM/Collectors进行预定维护 UTC - 18/08/2026 下午5: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.
** 降级业绩 -- -- 侦测事件处理(美国-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.