Sysdig Us West 2 장애 기록

1. 2026년 8월 14일 PM 7:12 UTCidentified

   We have identified an issue causing intermittent KSPM scan failures across all regions. Some scans are completing successfully, while others are not. As a result, Kubernetes posture and compliance data may be incomplete or unavailable for some customers. We have identified the cause and are actively implementing a fix. We will provide another update as progress continues.

2. 2026년 8월 14일 PM 10:04 UTCmonitoring

   We have rolled out remediation changes across the affected environments, and KSPM scan processing has resumed. Customers may continue to experience delays while the accumulated scan data is processed. We will continue monitoring the service throughout the weekend and provide further updates if the situation changes.

3. 2026년 8월 17일 PM 4:17 UTCmonitoring

   KSPM data collection has resumed and scan processing is progressing. Kubernetes posture and compliance data is being repopulated, and customers may still see incomplete or delayed results while the remaining scans complete. We are continuing to monitor recovery and will confirm once posture data is fully up to date

4. 2026년 8월 17일 PM 7:48 UTCresolved

   A permanent fix has been successfully deployed across all environments, and the backlog of pending scans has been fully processed. KSPM scan functionality is operating normally, and posture and compliance data is fully updated across all regions. We have confirmed that service metrics and data processing have returned to baseline performance. This incident is now resolved.

1. 2026년 8월 4일 AM 9:17 UTCinvestigating

   Customers may observe delays and/or misses in stateful detection policy events. We are currently investigating the issue.

2. 2026년 8월 4일 AM 9:28 UTCmonitoring

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

3. 2026년 8월 4일 AM 9:48 UTCresolved

   This incident has been resolved.

1. 2026년 8월 3일 AM 9:36 UTCinvestigating

   우리는 현재 문제를 조사하고 있습니다

2. 2026년 8월 3일 AM 10:30 UTCresolved

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

3. 2026년 8월 3일 PM 3:59 UTCpostmortem

   이 사건 중 CSPM 서비스는 외부 공급자의 연결 문제로 인해 서비스 시작 실패로 인해 스캔을 처리 할 수 없었습니다. 결과적으로, 작업이 채우고 아웃시의 기간 동안 처리되지 않았습니다. 영향을받는 서비스가 복원 된 후, 보류 스캔의 백로가 자동으로 배수 할 것으로 예상되며, 정상적인 스캔 기능으로 진보적으로 재배됩니다.

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

1. 2026년 7월 3일 AM 6:01 UTCinvestigating

   우리는 현재이 문제를 조사하고 있습니다.

2. 2026년 7월 3일 AM 6:01 UTCidentified

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

3. 2026년 7월 3일 AM 6:03 UTCidentified

   이 문제를 해결하기 위해 계속 노력하고 있습니다.

4. 2026년 7월 3일 AM 10:24 UTCidentified

   우리는 우리가 데이터의 backlog를 처리하고 수정을 확인하는 장소에 대한 수정이 있습니다.

5. 2026년 7월 3일 AM 10:56 UTCmonitoring

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

6. 2026년 7월 3일 AM 11:16 UTCresolved

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

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

1. 2026년 7월 1일 PM 11:29 UTCinvestigating

   Vulnerability Management Reporting 기능에 대한 문제점을 조사하고 있습니다. 고객은 스캔 결과의 처리에 영향을 미치는 문제로 인해 VM Reporting의 지연 및 누락 취약성 데이터를 경험할 수 있습니다. 우리의 조사에 따르면, 문제는 결과적으로 검색 인프라에서 처리 처리 처리 처리 처리량을 감소시킨다. 다른 Sysdig 특징은 영향을 미치지 않습니다. 우리는 적극적으로 영향의 범위를 투자하고 더 많은 정보가 가능한 한 빨리 다른 업데이트를 제공 할 것입니다.

2. 2026년 7월 2일 AM 1:29 UTCidentified

   Vulnerability Management Reporting 기능에 영향을 미치는 문제의 원인을 확인하고 개선을 볼 수 있습니다. 처리는 이력서 및 스캔 결과 메시지가 더 이상 손실되지 않습니다. 그러나 고객은 VM Reporting에 표시된 취약성 데이터에 대한 지연을 계속 경험할 수 있습니다. 우리는 정상적인 가공을 복원하고 계속 진행으로 또 다른 업데이트를 제공합니다.

3. 2026년 7월 2일 PM 8:16 UTCmonitoring

   Vulnerability Management Reporting의 지연이 성공적으로 구현되었습니다. 스캔 결과의 나머지 backlog로 복구를 모니터링하고 있습니다. 고객은 backlog가 완전히 명확하게 될 때까지 지연된 업데이트를 계속할 수 있습니다. 새로운 데이터 손실이 발생하지 않습니다.

4. 2026년 7월 3일 AM 5:38 UTCresolved

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

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

1. 2026년 6월 23일 PM 11:17 UTCidentified

   We are currently investigating an issue in the US2 region where users are unable to open the Vulnerability 360 drawer from the Vulnerability Finding page for KubeWorkload resources. Our engineering team has successfully identified the root cause and is actively working on a fix to deploy as soon as possible. We apologize for the inconvenience and will provide further updates here.

2. 2026년 6월 24일 AM 12:28 UTCidentified

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

3. 2026년 6월 24일 AM 1:46 UTCmonitoring

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

4. 2026년 6월 24일 AM 4:26 UTCmonitoring

   The fix is working as expected and we're actively monitoring until full recovery.

5. 2026년 6월 24일 PM 1:58 UTCmonitoring

   We're actively monitoring the recovery and will provide further updates as necessary.

6. 2026년 6월 24일 PM 5:41 UTCmonitoring

   We're actively monitoring the recovery and will provide further updates as necessary

7. 2026년 6월 24일 PM 5:42 UTCresolved

   This incident has been resolved.

1. 2026년 6월 23일 PM 2:50 UTCinvestigating

   We are currently experiencing a delay in processing mass data exports. No data has been lost, and all exports will be sent as soon as the issue is resolved.

2. 2026년 6월 23일 PM 4:07 UTCinvestigating

   We are continuing to investigate the issue.

3. 2026년 6월 23일 PM 4:16 UTCidentified

   We are continuing to investigate the issue.

4. 2026년 6월 24일 AM 12:04 UTCidentified

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

5. 2026년 6월 24일 AM 1:20 UTCmonitoring

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

6. 2026년 6월 24일 AM 4:38 UTCmonitoring

   The fix is working as expected and we're actively monitoring until full recovery.

7. 2026년 6월 24일 PM 1:59 UTCmonitoring

   We're actively monitoring the recovery and will provide further updates as necessary.

8. 2026년 6월 25일 PM 12:02 UTCmonitoring

   We're actively monitoring the recovery and will provide further updates as necessary

9. 2026년 6월 25일 PM 4:14 UTCresolved

   This incident has been resolved.

1. 2026년 6월 16일 PM 12:13 UTCinvestigating

   We’ve detected an issue in our processing systems and are actively investigating. We suspect this may be causing delays in Vulnerability Management (VM) data updates, meaning the latest scan findings could take longer than usual to appear. Scans are continuing to run. We’re working to confirm the extent of the impact and will post an update as soon as we know more.

2. 2026년 6월 16일 PM 1:53 UTCidentified

   We have identified the root cause and issued a fix, we are already recovering and we are processing the backlog of data pending to be processed. We will post updates here once we have more information about the recovery path

3. 2026년 6월 16일 PM 3:24 UTCmonitoring

   The data process it's recovering all new Scans should work fine, we might still some gaps until all the processes catch up with the queue. We will update here again when all the processes are good.

4. 2026년 6월 16일 PM 6:22 UTCresolved

   All scan processing services have fully recovered. Scan request volumes have returned to normal levels and all queue backlogs have been cleared. New scans are processing as expected with no further gaps anticipated. We will continue to monitor service health. No action is required on your end.

1. 2026년 6월 16일 AM 2:33 UTCidentified

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

2. 2026년 6월 16일 AM 2:42 UTCmonitoring

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

3. 2026년 6월 16일 AM 6:00 UTCmonitoring

   We are continuing to monitor recovery of the system.

4. 2026년 6월 16일 AM 6:22 UTCresolved

   This incident has been resolved.

1. 2026년 5월 6일 PM 11:08 UTCinvestigating

   We are currently investigating an issue affecting vulnerability scan processing in the US2 (us-east-2) region. Customers may experience delays in scan results appearing in the UI. New scan requests are taking longer to be processed than expected. Our team is actively working to resolve the issue. Further updates will be provided as investigation progresses.

2. 2026년 5월 6일 PM 11:22 UTCidentified

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

3. 2026년 5월 6일 PM 11:46 UTCmonitoring

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

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

   This incident has been resolved.

1. 2026년 4월 27일 PM 9:11 UTCinvestigating

   We are currently investigating an issue that may affect report generation. In some cases, reports may be created without displaying data.

2. 2026년 4월 27일 PM 10:22 UTCidentified

   We are aware of a potential issue affecting report generation, where reports may occasionally be generated without displaying data. Our engineering team is investigating and working toward a resolution. Updates will be provided as appropriate.

3. 2026년 4월 28일 AM 12:28 UTCmonitoring

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

4. 2026년 4월 28일 AM 2:44 UTCmonitoring

   We are currently monitoring the system to ensure report generation is functioning as expected. Updates will be shared as needed.

5. 2026년 4월 28일 AM 4:12 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2026년 4월 28일 AM 7:34 UTCresolved

   This incident has been resolved.

1. 2026년 4월 9일 AM 2:08 UTCresolved

   A processing delay in the data ingestion pipeline is currently impacting vulnerability page visibility for US2 customers, with a fix deployed and full recovery expected

1. 2026년 4월 9일 AM 2:04 UTCresolved

   A processing delay in the data ingestion pipeline is currently impacting vulnerability page visibility for US2 customers, with a fix deployed and full recovery expected

1. 2026년 4월 3일 AM 8:31 UTCinvestigating

   We are currently investigating this issue. We will provide updates as more information becomes available.

2. 2026년 4월 3일 AM 8:57 UTCinvestigating

   Agentless Scanning is experiencing delays, with scans stuck in a "Pending" state or not completing within the expected timeframe. We are actively investigating the issue and will provide more updates as necessary.

3. 2026년 4월 3일 AM 11:34 UTCinvestigating

   This issue is still under active investigation. Additional updates will be provided as new information becomes available.

4. 2026년 4월 3일 PM 3:44 UTCinvestigating

   We have applied changes to improve processing of affected cloud accounts, and recovery is in progress. Some scans and related cloud security features may be delayed while this completes. Our teams are closely monitoring the environment to ensure stability.

5. 2026년 4월 4일 AM 7:10 UTCmonitoring

   We have applied changes to improve processing of affected cloud accounts, and recovery is in progress. Some scans and related cloud security features may be delayed while this completes. Our teams are closely monitoring the environment to ensure stability.

6. 2026년 4월 4일 PM 4:19 UTCmonitoring

   Recovery is in progress. Some scans and related cloud security features may be delayed while this completes. Our teams are closely monitoring the environment to ensure stability.

7. 2026년 4월 4일 PM 8:05 UTCmonitoring

   Recovery is progressing, with host scan volumes increasing. We are monitoring closely as the system continues to stabilize.

8. 2026년 4월 5일 AM 12:04 UTCmonitoring

   Recovery continues, with host scan volumes steadily increasing. We are monitoring closely as the system stabilizes

9. 2026년 4월 5일 AM 4:59 UTCmonitoring

   Recovery continues, with host scan volumes steadily increasing. We are closely monitoring as the system stabilizes.

10. 2026년 4월 5일 AM 6:53 UTCresolved

    This incident has been resolved.

1. 2026년 3월 26일 PM 12:50 UTCresolved

   Sysdig has become aware of an alerting issue in the cloud platform, which may cause some customers to experience alerts being triggered incorrectly or not on time, or gaps in populated graphs. The rest of Sysdig's features are functioning. The issue was solved at 12.18pm UTC

1. 2026년 2월 17일 AM 9:47 UTCinvestigating

   We are currently investigating the issue

2. 2026년 2월 17일 AM 11:58 UTCidentified

   The issues has been identified and the team is working on a fix

3. 2026년 2월 17일 PM 5:35 UTCidentified

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

4. 2026년 2월 17일 PM 9:57 UTCmonitoring

   We have deployed a fix to address the issue causing incorrect policy data in Compliance and Inventory. Systems are stable, and we are actively monitoring. Correct data is expected to progressively converge across affected areas within the next 24 hours as processing completes. We will provide further updates if needed

5. 2026년 2월 18일 AM 7:03 UTCinvestigating

   The previously deployed fix did not work as expected. While data briefly corrected after new scans, subsequent sync cycles are causing policies and controls to be removed again. We are actively investigating the issue.

6. 2026년 2월 18일 AM 9:42 UTCidentified

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

7. 2026년 2월 18일 PM 5:12 UTCmonitoring

   The new fix has been deployed, and we are observing policy data being correctly recovered across affected environments. The incident status has been moved to Monitoring while we continue validating stability.

8. 2026년 2월 18일 PM 9:55 UTCmonitoring

   The previously deployed fix continues to operate as expected, and we are observing policy and control data recovering normally. Systems remain stable, and we are actively monitoring to ensure consistency and sustained correctness of Compliance and Inventory data. We will provide further updates if necessary.

9. 2026년 2월 19일 AM 12:21 UTCmonitoring

   The previously deployed corrective fix continues to perform as expected, and we are observing policy, control, and requirement data recovering normally. Systems remain stable, and we have not observed any signs of regression. Due to the normal scan lifecycle, Compliance and Inventory data will progressively converge as background processing completes. We are actively monitoring the situation and will provide further updates if necessary.

10. 2026년 2월 19일 AM 8:58 UTCmonitoring

    Compliance and Inventory data is recovering as expected. We are actively monitoring the situation and will provide further updates if necessary.

11. 2026년 2월 19일 PM 7:53 UTCmonitoring

    Compliance and Inventory data continue to recover for the vast majority of customers. Systems remain stable, and no regression has been detected. Some customers may still observe partial data or temporary inconsistencies while background processing completes and results converge. We are actively monitoring the situation and will provide further updates if necessary.

12. 2026년 2월 20일 AM 1:05 UTCmonitoring

    Platform performance remains healthy, and Compliance and Inventory data continue to converge as expected. No regression has been detected. Some customers may still observe partial or delayed data while background processing completes. We will provide further updates if necessary.

13. 2026년 2월 20일 AM 10:36 UTCmonitoring

    We are still monitoring as some customers may still observe partial or delayed data while background processing completes. Platform performance remains healthy, and Compliance and Inventory data continue to converge. We will provide further updates if necessary.

14. 2026년 2월 20일 PM 3:55 UTCresolved

    This incident has been resolved.

1. 2026년 1월 15일 AM 9:07 UTCmonitoring

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

2. 2026년 1월 15일 AM 10:14 UTCresolved

   This incident has been resolved.

1. 2026년 1월 13일 PM 3:21 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 1월 13일 PM 5:13 UTCidentified

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

3. 2026년 1월 13일 PM 6:40 UTCmonitoring

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

4. 2026년 1월 13일 PM 8:30 UTCresolved

   This incident has been resolved.

1. 2025년 12월 17일 PM 2:37 UTCresolved

   We suffered a momentary disservice in the functionality of visualizing Attack Path due to a data migration, we have addressed the issue and the functionality is back online

1. 2025년 12월 1일 PM 6:42 UTCinvestigating

   Cloud log ingestion coming from workloads in us-east-1 at AWS are not being ingested by Sysdig. Our specialists are currently working with AWS to resolve the issue.

2. 2025년 12월 2일 PM 6:39 UTCidentified

   Our engineering teams have successfully identified the root cause of the failure that is preventing logs from being ingested by Sysdig. Resolution Underway: We are currently working directly with AWS specialists on the resolution steps required to restore the functionality.

3. 2025년 12월 3일 PM 5:19 UTCidentified

   We have collaborated with AWS to resolve the issue that was preventing logs from being ingested via EventBridge. Log ingestion has now resumed, and we have started processing the backlog of events.

4. 2025년 12월 4일 PM 7:48 UTCmonitoring

   Log ingestion is functional. We are currently processing the accumulated event backlog.

5. 2025년 12월 10일 PM 4:56 UTCresolved

   Our monitoring confirms that log ingestion is functioning as expected and no further delays or drops are occurring. We are now closing the incident.