Rapid7 장애 기록

1. 2026년 9월 3일 PM 10:31 UTCidentified

   우리는 현재 Exposure Command Platform 경험에 영향을 미치는 문제점을 조사하고 있습니다. 고객은 대기 시간 및 오류를 경험할 수 있습니다. 우리의 엔지니어링 팀은 관련 공급 업체 문제를 적극적으로 모니터링하고 정상적인 서비스에 중점을 둡니다. 업데이트는 여기에 게시됩니다.

2. 2026년 9월 3일 PM 10:33 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 9월 3일 PM 10:37 UTCmonitoring

   우리는 더 많은 문제를 모니터링하고 있습니다.

4. 2026년 9월 3일 PM 10:40 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 18일 PM 4:41 UTCinvestigating

   우리는 19/08/2026 17:00 PM에 SIEM/Collectors에 예정된 정비를 실시할 것입니다 UTC - 19/08/2026 18:00 오후 UTC. 이 시간 도중, 고객은 수집의 임시 정지를 경험할지도 모릅니다. 충격: 모든 수집가에 있는 수집은 5-10 분 동안 근원을 기초를 두었습니다. Worst case 시나리오: 수집가는 수동 개입까지 오프라인으로 간다 우리는 우리의 서비스의 신뢰성과 성과를 개량하기 위하여 우리가 일하기 때문에 당신의 인내 및 이해를 평가합니다.

2. 2026년 8월 19일 PM 5:03 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 8월 19일 PM 5:55 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 17일 PM 3:44 UTCinvestigating

   우리는 18/08/2026 16:00 PM에 SIEM/Collectors에 예정된 정비를 실행할 것입니다 UTC - 18/08/2026 17:00 오후 UTC. 이 시간 도중, 고객은 수집의 임시 정지를 경험할지도 모릅니다. 충격: 모든 수집가에 있는 수집은 5-10 분 동안 근원을 기초를 두었습니다. Worst case 시나리오: 수집가는 수동 개입까지 오프라인으로 간다 우리는 우리의 서비스의 신뢰성과 성과를 개량하기 위하여 우리가 일하기 때문에 당신의 인내 및 이해를 평가합니다.

2. 2026년 8월 18일 PM 4:04 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 8월 18일 PM 4:08 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 8월 18일 PM 4:55 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 14일 PM 4:09 UTCinvestigating

   We are investigating reports of API issues in the EU region

2. 2026년 8월 14일 PM 5:00 UTCresolved

   This incident has been resolved.

1. 2026년 8월 13일 PM 3: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. 2026년 8월 14일 PM 4:01 UTCmonitoring

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

3. 2026년 8월 14일 PM 5:00 UTCresolved

   This incident has been resolved.

1. 2026년 8월 3일 PM 4:55 UTCinvestigating

   **Degraded Performance - 탐지 이벤트 처리 (US-1)** 우리는 현재 미국-1 지역의 탐지 사건을 위한 정상적인 가공 시간 보다는 더 느립니다. 우리의 팀은 통보되고 적극적으로 문제점을 조사하고 있습니다. 다른 지역은 이 시간에 영향을 미치지 않습니다. 더 많은 정보를 사용할 수 있도록 더 많은 업데이트를 제공합니다.

2. 2026년 8월 3일 PM 4:58 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 8월 3일 PM 5:45 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 12일 PM 1:22 UTCinvestigating

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

2. 2026년 6월 12일 PM 2:42 UTCidentified

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

3. 2026년 6월 12일 PM 3:40 UTCmonitoring

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

4. 2026년 6월 14일 PM 4:42 UTCresolved

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

1. 2026년 5월 21일 PM 3: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. 2026년 5월 21일 PM 4:02 UTCresolved

   This incident has been resolved.

1. 2026년 5월 12일 AM 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. 2026년 5월 12일 AM 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. 2026년 5월 12일 AM 10:30 UTCmonitoring

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

4. 2026년 5월 12일 AM 10:44 UTCresolved

   This incident has been resolved.

1. 2026년 5월 8일 AM 2:05 UTCinvestigating

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

2. 2026년 5월 8일 AM 2:24 UTCidentified

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

3. 2026년 5월 8일 AM 4:51 UTCmonitoring

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

4. 2026년 5월 8일 PM 12:49 UTCresolved

   This incident has been resolved.

1. 2026년 5월 5일 PM 2: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. 2026년 5월 5일 PM 3: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. 2026년 5월 5일 PM 3:58 UTCidentified

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

4. 2026년 5월 5일 PM 4:43 UTCresolved

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

1. 2026년 4월 24일 AM 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. 2026년 4월 24일 PM 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. 2026년 4월 24일 PM 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. 2026년 4월 27일 PM 2:51 UTCresolved

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

1. 2026년 4월 17일 PM 5:17 UTCinvestigating

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

2. 2026년 4월 17일 PM 6:09 UTCmonitoring

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

3. 2026년 4월 17일 PM 7:05 UTCresolved

   This incident has been resolved.

1. 2026년 4월 15일 PM 4: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. 2026년 4월 15일 PM 5:18 UTCmonitoring

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

3. 2026년 4월 15일 PM 6:34 UTCresolved

   This incident has been resolved.

1. 2026년 4월 13일 PM 3: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. 2026년 4월 13일 PM 4: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. 2026년 4월 13일 PM 4:35 UTCidentified

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

4. 2026년 4월 14일 PM 3: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. 2026년 4월 15일 PM 4:09 UTCmonitoring

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

6. 2026년 4월 15일 PM 5:43 UTCresolved

   This incident has been resolved.

1. 2026년 4월 13일 PM 3: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. 2026년 4월 13일 PM 4:14 UTCmonitoring

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

3. 2026년 4월 13일 PM 4:35 UTCresolved

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

1. 2026년 4월 9일 AM 5: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. 2026년 4월 9일 AM 8: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. 2026년 4월 9일 PM 9:28 UTCresolved

   This incident has been resolved.

1. 2026년 3월 13일 PM 5:59 UTCinvestigating

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

2. 2026년 3월 13일 PM 6:31 UTCmonitoring

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

3. 2026년 3월 13일 PM 7:59 UTCresolved

   This incident has been resolved.

1. 2026년 3월 11일 PM 3: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. 2026년 3월 11일 PM 3: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. 2026년 3월 18일 PM 8: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. 2026년 3월 11일 PM 2:48 UTCinvestigating

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

2. 2026년 3월 11일 PM 4:56 UTCidentified

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

3. 2026년 3월 11일 PM 10:28 UTCidentified

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

4. 2026년 3월 12일 AM 2:23 UTCidentified

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

5. 2026년 3월 12일 AM 2:26 UTCmonitoring

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

6. 2026년 3월 16일 AM 10:55 UTCmonitoring

   We continue to monitor the results of the fix implemented.

7. 2026년 3월 18일 AM 8:43 UTCresolved

   This incident has been resolved.