Sysdig Us West 2 の障害履歴

1. 2026年8月14日 19: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日 22: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日 16: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日 19: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日 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日 9:28 UTCmonitoring

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

3. 2026年8月4日 9:48 UTCresolved

   This incident has been resolved.

1. 2026年8月3日 9:36 UTCinvestigating

   現在、課題を調査しています

2. 2026年8月3日 10:30 UTCresolved

   この事件は解決しました.

3. 2026年8月3日 15:59 UTCpostmortem

   この場合、外部プロバイダへの接続の問題によるサービス起動障害によるCSPMサービスはスキャン処理できませんでした。 その結果、ジョブのキューイングをスキャンし、アウト率の持続時間のために処理されていないジョブをスキャンします。 影響を受けたサービスが復元された後、保留中のスキャンのバックログが自動的にドレインし、通常はスキャン機能が徐々に再開すると予想されます.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月3日 6:01 UTCinvestigating

   現在、この問題を調査中です.

2. 2026年7月3日 6:01 UTCidentified

   問題が特定され、修正が実装されています.

3. 2026年7月3日 6:03 UTCidentified

   この問題の修正には引き続き取り組んでいます。

4. 2026年7月3日 10:24 UTCidentified

   データのバックログを処理し、修正が正しいことを検証するために取り組んでいる場所で修正があります.

5. 2026年7月3日 10:56 UTCmonitoring

   修正を実装し、結果を監視しています.

6. 2026年7月3日 11:16 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月1日 23:29 UTCinvestigating

   脆弱性管理報告機能に影響を及ぼす問題について調査しています。 お客様は、スキャン結果の処理に影響を及ぼす問題により、VM Reportingの脆弱性データが遅延および欠落している可能性があります。 当社の調査によると、問題は、基礎的な検索インフラにおける処理のスループットを削減することに関連しています。 その他のSysdig機能は影響しません。 インパクトの規模を積極的に調査し、より多くの情報が利用可能になったらただちに別のアップデートを提供します.

2. 2026年7月2日 1:29 UTCidentified

   脆弱性管理報告機能に影響を及ぼす問題の原因を特定し、改善を図っています。 処理が再開され、結果メッセージが失われることはありません。 ただし、VM Reporting に表示される脆弱性データに、キューされたスキャン結果のバックログを処理します。 通常の処理を復元し、進捗を継続して別の更新を行います.

3. 2026年7月2日 20:16 UTCmonitoring

   脆弱性管理報告の遅延を引き起こした問題が正常に実施されてきました。 スキャン結果の残りのバックログが処理されるため、回復を監視しています。 バックログが完全にクリアされるまで、顧客は引き続き更新を遅らせることができます。 新しいデータ損失が発生しません.

4. 2026年7月3日 5:38 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年6月23日 23: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日 0:28 UTCidentified

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

3. 2026年6月24日 1:46 UTCmonitoring

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

4. 2026年6月24日 4:26 UTCmonitoring

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

5. 2026年6月24日 13:58 UTCmonitoring

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

6. 2026年6月24日 17:41 UTCmonitoring

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

7. 2026年6月24日 17:42 UTCresolved

   This incident has been resolved.

1. 2026年6月23日 14: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日 16:07 UTCinvestigating

   We are continuing to investigate the issue.

3. 2026年6月23日 16:16 UTCidentified

   We are continuing to investigate the issue.

4. 2026年6月24日 0:04 UTCidentified

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

5. 2026年6月24日 1:20 UTCmonitoring

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

6. 2026年6月24日 4:38 UTCmonitoring

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

7. 2026年6月24日 13:59 UTCmonitoring

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

8. 2026年6月25日 12:02 UTCmonitoring

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

9. 2026年6月25日 16:14 UTCresolved

   This incident has been resolved.

1. 2026年6月16日 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日 13: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日 15: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日 18: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日 2:33 UTCidentified

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

2. 2026年6月16日 2:42 UTCmonitoring

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

3. 2026年6月16日 6:00 UTCmonitoring

   We are continuing to monitor recovery of the system.

4. 2026年6月16日 6:22 UTCresolved

   This incident has been resolved.

1. 2026年5月6日 23: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日 23:22 UTCidentified

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

3. 2026年5月6日 23:46 UTCmonitoring

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

4. 2026年5月7日 0:10 UTCresolved

   This incident has been resolved.

1. 2026年4月27日 21: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日 22: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日 0:28 UTCmonitoring

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

4. 2026年4月28日 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日 4:12 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2026年4月28日 7:34 UTCresolved

   This incident has been resolved.

1. 2026年4月9日 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日 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日 8:31 UTCinvestigating

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

2. 2026年4月3日 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日 11:34 UTCinvestigating

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

4. 2026年4月3日 15: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日 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日 16: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日 20:05 UTCmonitoring

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

8. 2026年4月5日 0:04 UTCmonitoring

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

9. 2026年4月5日 4:59 UTCmonitoring

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

10. 2026年4月5日 6:53 UTCresolved

    This incident has been resolved.

1. 2026年3月26日 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日 9:47 UTCinvestigating

   We are currently investigating the issue

2. 2026年2月17日 11:58 UTCidentified

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

3. 2026年2月17日 17:35 UTCidentified

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

4. 2026年2月17日 21: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日 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日 9:42 UTCidentified

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

7. 2026年2月18日 17: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日 21: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日 0: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日 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日 19: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日 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日 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日 15:55 UTCresolved

    This incident has been resolved.

1. 2026年1月15日 9:07 UTCmonitoring

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

2. 2026年1月15日 10:14 UTCresolved

   This incident has been resolved.

1. 2026年1月13日 15:21 UTCinvestigating

   We are currently investigating this issue.

2. 2026年1月13日 17:13 UTCidentified

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

3. 2026年1月13日 18:40 UTCmonitoring

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

4. 2026年1月13日 20:30 UTCresolved

   This incident has been resolved.

1. 2025年12月17日 14: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日 18: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日 18: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日 17: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日 19:48 UTCmonitoring

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

5. 2025年12月10日 16: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.