Sysdig Us West 2 中断历史

1. 2026年8月14日 UTC 19:12identified

   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日 UTC 22:04monitoring

   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日 UTC 16:17monitoring

   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日 UTC 19:48resolved

   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日 UTC 09:17investigating

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

2. 2026年8月4日 UTC 09:28monitoring

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

3. 2026年8月4日 UTC 09:48resolved

   This incident has been resolved.

1. 2026年8月3日 UTC 09:36investigating

   我们正在调查这个问题

2. 2026年8月3日 UTC 10:30resolved

   这一事件已经得到解决.

3. 2026年8月3日 UTC 15:59postmortem

   在这次事件中,CSPM服务由于外部供应商的连接问题导致服务启动失败而无法处理扫描. 因此,扫描任务排出队列,在停用期间没有处理. 受影响的服务恢复后,积压的待扫描工作预计将自动减少,正常的扫描功能将逐步恢复.

自动翻译自官方事件更新。

1. 2026年7月3日 UTC 06:01investigating

   我们目前正在调查这一问题.

2. 2026年7月3日 UTC 06:01identified

   这一问题已经确定,一个解决办法正在实施之中.

3. 2026年7月3日 UTC 06:03identified

   我们正在继续努力解决这个问题。

4. 2026年7月3日 UTC 10:24identified

   我们正在努力处理积压的数据,核实其是否正确.

5. 2026年7月3日 UTC 10:56monitoring

   一项措施已经执行,我们正在监测结果.

6. 2026年7月3日 UTC 11:16resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月1日 UTC 23:29investigating

   我们正在调查影响脆弱性管理报告功能的问题。 由于影响扫描结果处理的问题,客户在VM报告中可能遇到延误并缺少脆弱性数据。 我们的调查显示,这个问题与基本搜索基础设施的处理量减少有关。 其他Sysdig特性没有受到影响。 我们正在积极调查影响的范围,一旦获得更多信息,我们将提供另一个最新情况.

2. 2026年7月2日 UTC 01:29identified

   我们查明了影响脆弱性管理报告特征的问题的根源,并看到改进。 处理工作已恢复,扫描结果消息不再丢失. 然而,在我们处理排队扫描结果的积压时,客户可能会继续遇到在VM报告中出现的脆弱性数据的拖延。 我们正积极努力恢复正常的处理,并将随着进展的继续提供另一个最新情况.

3. 2026年7月2日 UTC 20:16monitoring

   缓解措施已成功实施,造成脆弱性管理报告延误的问题已得到解决。 随着剩余积压的扫描结果得到处理,我们正在监测回收情况。 客户可能会继续经历延迟更新,直到积压工作完全结清。 没有出现新的数据损失.

4. 2026年7月3日 UTC 05:38resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年6月23日 UTC 23:17identified

   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日 UTC 00:28identified

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

3. 2026年6月24日 UTC 01:46monitoring

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

4. 2026年6月24日 UTC 04:26monitoring

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

5. 2026年6月24日 UTC 13:58monitoring

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

6. 2026年6月24日 UTC 17:41monitoring

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

7. 2026年6月24日 UTC 17:42resolved

   This incident has been resolved.

1. 2026年6月23日 UTC 14:50investigating

   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日 UTC 16:07investigating

   We are continuing to investigate the issue.

3. 2026年6月23日 UTC 16:16identified

   We are continuing to investigate the issue.

4. 2026年6月24日 UTC 00:04identified

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

5. 2026年6月24日 UTC 01:20monitoring

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

6. 2026年6月24日 UTC 04:38monitoring

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

7. 2026年6月24日 UTC 13:59monitoring

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

8. 2026年6月25日 UTC 12:02monitoring

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

9. 2026年6月25日 UTC 16:14resolved

   This incident has been resolved.

1. 2026年6月16日 UTC 12:13investigating

   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日 UTC 13:53identified

   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日 UTC 15:24monitoring

   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日 UTC 18:22resolved

   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日 UTC 02:33identified

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

2. 2026年6月16日 UTC 02:42monitoring

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

3. 2026年6月16日 UTC 06:00monitoring

   We are continuing to monitor recovery of the system.

4. 2026年6月16日 UTC 06:22resolved

   This incident has been resolved.

1. 2026年5月6日 UTC 23:08investigating

   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日 UTC 23:22identified

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

3. 2026年5月6日 UTC 23:46monitoring

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

4. 2026年5月7日 UTC 00:10resolved

   This incident has been resolved.

1. 2026年4月27日 UTC 21:11investigating

   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日 UTC 22:22identified

   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日 UTC 00:28monitoring

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

4. 2026年4月28日 UTC 02:44monitoring

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

5. 2026年4月28日 UTC 04:12monitoring

   We are continuing to monitor for any further issues.

6. 2026年4月28日 UTC 07:34resolved

   This incident has been resolved.

1. 2026年4月9日 UTC 02:08resolved

   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日 UTC 02:04resolved

   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日 UTC 08:31investigating

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

2. 2026年4月3日 UTC 08:57investigating

   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日 UTC 11:34investigating

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

4. 2026年4月3日 UTC 15:44investigating

   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日 UTC 07:10monitoring

   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日 UTC 16:19monitoring

   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日 UTC 20:05monitoring

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

8. 2026年4月5日 UTC 00:04monitoring

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

9. 2026年4月5日 UTC 04:59monitoring

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

10. 2026年4月5日 UTC 06:53resolved

    This incident has been resolved.

1. 2026年3月26日 UTC 12:50resolved

   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日 UTC 09:47investigating

   We are currently investigating the issue

2. 2026年2月17日 UTC 11:58identified

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

3. 2026年2月17日 UTC 17:35identified

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

4. 2026年2月17日 UTC 21:57monitoring

   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日 UTC 07:03investigating

   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日 UTC 09:42identified

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

7. 2026年2月18日 UTC 17:12monitoring

   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日 UTC 21:55monitoring

   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日 UTC 00:21monitoring

   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日 UTC 08:58monitoring

    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日 UTC 19:53monitoring

    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日 UTC 01:05monitoring

    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日 UTC 10:36monitoring

    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日 UTC 15:55resolved

    This incident has been resolved.

1. 2026年1月15日 UTC 09:07monitoring

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

2. 2026年1月15日 UTC 10:14resolved

   This incident has been resolved.

1. 2026年1月13日 UTC 15:21investigating

   We are currently investigating this issue.

2. 2026年1月13日 UTC 17:13identified

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

3. 2026年1月13日 UTC 18:40monitoring

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

4. 2026年1月13日 UTC 20:30resolved

   This incident has been resolved.

1. 2025年12月17日 UTC 14:37resolved

   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日 UTC 18:42investigating

   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日 UTC 18:39identified

   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日 UTC 17:19identified

   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日 UTC 19:48monitoring

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

5. 2025年12月10日 UTC 16:56resolved

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