Sysdig US-West-2 Outage History

Sysdig US-West-2 is up right now

Pingoru has recorded 51 incidents for Sysdig US-West-2: 31 in the last 12 months and 10 in the last 90 days.

Source: status-us2.sysdig.com

51incidents recorded
31last 12 months
10last 90 days
24 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct4
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct5%
Pingoru began tracking Sysdig US-West-2 in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026457 of 720 (8%)
May 202611 of 744 (0%)
June 2026459 of 720 (8%)
July 2026227 of 744 (4%)
August 2026374 of 744 (10%)
September 2026314 of 720 (2%)
October 2026424 of 523 (5%)

Incidents, newest first

Major October 11, 2026 Sysdig Cloud Platform Data Ingestion Degradation 11h 14m Sysdig Secure

Started Oct 11, 2026, 03:10 PM UTC· resolved Oct 12, 2026, 02:25 AM UTC

  1. investigating Oct 11, 2026, 03:10 PM UTC

    Sysdig has become aware of a reporting scanning ingestion issue, which may cause some customers to get delayed reports. The rest of Sysdig's features are functioning. We are investigating the issue and will post updates on this page.

  2. identified Oct 11, 2026, 03:58 PM UTC

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

  3. monitoring Oct 11, 2026, 05:00 PM UTC

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

  4. monitoring Oct 11, 2026, 06:31 PM UTC

    The system it's recovering and processing the backlog of items pending, we are still monitoring the situation and waiting for the full recovery

  5. monitoring Oct 11, 2026, 07:07 PM UTC

    The system keeps recovering and processing the backlog of items pending, we are still monitoring the situation and waiting for the full recovery

  6. monitoring Oct 11, 2026, 07:59 PM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Oct 11, 2026, 08:00 PM UTC

    The system keeps recovering and processing the backlog of items pending, we are still monitoring the situation and waiting for the full recovery.

  8. monitoring Oct 11, 2026, 11:27 PM UTC

    The system keeps recovering and processing the backlog of items pending, we are still monitoring the situation and waiting for the full recovery.

  9. monitoring Oct 12, 2026, 01:50 AM UTC

    The system keeps recovering and processing the backlog of items pending, we are still monitoring the situation and waiting for the full recovery.

  10. monitoring Oct 12, 2026, 02:08 AM UTC

    We can resolved this alert and also update status page that issue has been resolved now.

  11. monitoring Oct 12, 2026, 02:14 AM UTC

    We are continuing to monitor for any further issues.

  12. monitoring Oct 12, 2026, 02:16 AM UTC

    We are continuing to monitor for any further issues.

  13. monitoring Oct 12, 2026, 02:20 AM UTC

    We are continuing to monitor for any further issues.

  14. monitoring Oct 12, 2026, 02:20 AM UTC

    We can resolved this alert, the issue has been resolved now.

  15. resolved Oct 12, 2026, 02:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 8, 2026 Alert notifications are delayed in this region, we are investigating the reason 1h 36m Sysdig Monitor

Started Oct 08, 2026, 01:13 AM UTC· resolved Oct 08, 2026, 02:50 AM UTC

  1. investigating Oct 08, 2026, 01:13 AM UTC

    We are currently investigating this issue.

  2. monitoring Oct 08, 2026, 02:37 AM UTC

    A fix has been implemented and we are currently monitoring the results to ensure full recovery.

  3. resolved Oct 08, 2026, 02:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 6, 2026 Sysdig Cloud Platform Alerting Degradation 23m Sysdig Monitor

Started Oct 06, 2026, 12:47 PM UTC· resolved Oct 06, 2026, 01:10 PM UTC

  1. investigating Oct 06, 2026, 12:47 PM UTC

    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. We are investigating the issue and will post updates on this page.

  2. identified Oct 06, 2026, 01:03 PM UTC

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

  3. resolved Oct 06, 2026, 01:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 2, 2026 Cost Advisor degradation 1h 15m Sysdig Monitor

Started Oct 02, 2026, 09:21 AM UTC· resolved Oct 02, 2026, 10:37 AM UTC

  1. investigating Oct 02, 2026, 09:21 AM UTC

    Customers can observe Cost Advisor data to be missing for Azure clusters. We are currently investigating the issue.

  2. identified Oct 02, 2026, 09:32 AM UTC

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

  3. resolved Oct 02, 2026, 10:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 30, 2026 degradation in the processing of CSPM scans 13h 41m Sysdig Secure

Started Sep 30, 2026, 07:44 PM UTC· resolved Oct 01, 2026, 09:25 AM UTC

  1. investigating Sep 30, 2026, 07:44 PM UTC

    We are experiencing some degradation in the processing of CSPM scans, which may result in inconsistencies on the Inventory and Compliance Findings pages. We are actively working on a fix to restore CSPM data to normal and expect to provide an update in the coming hours.

  2. monitoring Oct 01, 2026, 01:00 AM UTC

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

  3. resolved Oct 01, 2026, 09:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 28, 2026 Vulnerability data ingestion delay impacting Vulnerability Overview, Findings and Reporting 3h 27m Sysdig Secure

Started Sep 28, 2026, 10:17 AM UTC· resolved Sep 28, 2026, 01:44 PM UTC

  1. investigating Sep 28, 2026, 10:17 AM UTC

    We are currently investigating this issue.

  2. monitoring Sep 28, 2026, 01:01 PM UTC

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

  3. resolved Sep 28, 2026, 01:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 11, 2026 Customer may experience missing cloud resources in Inventory 6h 6m Sysdig Secure

Started Sep 11, 2026, 11:12 AM UTC· resolved Sep 11, 2026, 05:19 PM UTC

  1. investigating Sep 11, 2026, 11:12 AM UTC

    We are currently investigating this issue.

  2. investigating Sep 11, 2026, 12:05 PM UTC

    We are continuing to investigate this issue.

  3. identified Sep 11, 2026, 01:34 PM UTC

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

  4. identified Sep 11, 2026, 04:05 PM UTC

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

  5. monitoring Sep 11, 2026, 04:55 PM UTC

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

  6. resolved Sep 11, 2026, 05:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 14, 2026 KSPM Scan Degradation 3d Sysdig Secure

Started Aug 14, 2026, 07:11 PM UTC· resolved Aug 17, 2026, 07:48 PM UTC

  1. identified Aug 14, 2026, 07:12 PM UTC

    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. monitoring Aug 14, 2026, 10:04 PM UTC

    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. monitoring Aug 17, 2026, 04:17 PM UTC

    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. resolved Aug 17, 2026, 07:48 PM UTC

    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.

Read the full incident report →

Major August 4, 2026 Delay in detection of policy events 31m Sysdig Secure

Started Aug 04, 2026, 09:17 AM UTC· resolved Aug 04, 2026, 09:48 AM UTC

  1. investigating Aug 04, 2026, 09:17 AM UTC

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

  2. monitoring Aug 04, 2026, 09:28 AM UTC

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

  3. resolved Aug 04, 2026, 09:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 3, 2026 Customers may experience issues in CSPM scans 54m Sysdig Secure

Started Aug 03, 2026, 09:36 AM UTC· resolved Aug 03, 2026, 10:30 AM UTC

  1. investigating Aug 03, 2026, 09:36 AM UTC

    We are currently investigating the issue

  2. resolved Aug 03, 2026, 10:30 AM UTC

    This incident has been resolved.

  3. postmortem Aug 03, 2026, 03:59 PM UTC

    During this incident, CSPM services were unable to process scans due to a service startup failure due to connectivity issues to an external provider. As a result, scan jobs queued up and were not processed for the duration of the outage. After the affected services have been restored, the backlog of pending scans is expected to drain automatically, with normal scanning functionality resuming progressively.

Read the full incident report →

Minor July 3, 2026 Delay in Vulnerability Scan 8h 46m Sysdig Secure, Sysdig Data Ingestion

Started Jul 03, 2026, 02:30 AM UTC· resolved Jul 03, 2026, 11:16 AM UTC

  1. investigating Jul 03, 2026, 06:01 AM UTC

    We are currently investigating this issue.

  2. identified Jul 03, 2026, 06:01 AM UTC

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

  3. identified Jul 03, 2026, 06:03 AM UTC

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

  4. identified Jul 03, 2026, 10:24 AM UTC

    We have a fix in place we are working on processing the backlog of data and verifying that the fix it's correct.

  5. monitoring Jul 03, 2026, 10:56 AM UTC

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

  6. resolved Jul 03, 2026, 11:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 1, 2026 Vulnerability Management Reporting Experiencing Processing Issues 18h 31m Sysdig Secure

Started Jul 01, 2026, 11:29 PM UTC· resolved Jul 02, 2026, 06:00 PM UTC

  1. investigating Jul 01, 2026, 11:29 PM UTC

    We are investigating an issue impacting the Vulnerability Management Reporting feature. Customers may experience delays and missing vulnerability data in VM Reporting due to an issue affecting the processing of scan results. Our investigation indicates the issue is related to reduced processing throughput in the underlying search infrastructure. Other Sysdig features are not impacted. We are actively investigating the scope of the impact and will provide another update as soon as more information becomes available.

  2. identified Jul 02, 2026, 01:29 AM UTC

    We have identified the cause of the issue impacting the Vulnerability Management Reporting feature and are seeing improvements. Processing has resumed and scan result messages are no longer being lost. However, customers may continue to experience delays in vulnerability data appearing in VM Reporting while we process the backlog of queued scan results. We are actively working to restore normal processing and will provide another update as progress continues.

  3. monitoring Jul 02, 2026, 08:16 PM UTC

    Mitigation measures have been successfully implemented and the issue causing delays in Vulnerability Management Reporting has been resolved. We are monitoring the recovery as the remaining backlog of scan results is processed. Customers may continue to experience delayed updates until the backlog has fully cleared. No new data loss is occurring.

  4. resolved Jul 03, 2026, 05:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 23, 2026 KubeWorkload Vulnerability 360 Drawer Issue 18h 25m Sysdig Secure

Started Jun 23, 2026, 11:17 PM UTC· resolved Jun 24, 2026, 05:42 PM UTC

  1. identified Jun 23, 2026, 11:17 PM UTC

    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. identified Jun 24, 2026, 12:28 AM UTC

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

  3. monitoring Jun 24, 2026, 01:46 AM UTC

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

  4. monitoring Jun 24, 2026, 04:26 AM UTC

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

  5. monitoring Jun 24, 2026, 09:48 AM UTC

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

  6. monitoring Jun 24, 2026, 01:58 PM UTC

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

  7. monitoring Jun 24, 2026, 05:41 PM UTC

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

  8. resolved Jun 24, 2026, 05:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 23, 2026 Mass Data Export Delays 2d 1h Sysdig Secure

Started Jun 23, 2026, 02:50 PM UTC· resolved Jun 25, 2026, 04:14 PM UTC

  1. investigating Jun 23, 2026, 02:50 PM UTC

    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. investigating Jun 23, 2026, 04:07 PM UTC

    We are continuing to investigate the issue.

  3. identified Jun 23, 2026, 04:16 PM UTC

    We are continuing to investigate the issue.

  4. identified Jun 23, 2026, 04:51 PM UTC

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

  5. identified Jun 23, 2026, 05:55 PM UTC

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

  6. identified Jun 23, 2026, 06:56 PM UTC

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

  7. monitoring Jun 23, 2026, 08:05 PM UTC

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

  8. identified Jun 23, 2026, 10:02 PM UTC

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

  9. identified Jun 23, 2026, 11:04 PM UTC

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

  10. identified Jun 24, 2026, 12:04 AM UTC

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

  11. monitoring Jun 24, 2026, 01:20 AM UTC

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

  12. monitoring Jun 24, 2026, 04:38 AM UTC

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

  13. monitoring Jun 24, 2026, 09:39 AM UTC

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

  14. monitoring Jun 24, 2026, 01:59 PM UTC

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

  15. monitoring Jun 24, 2026, 05:41 PM UTC

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

  16. monitoring Jun 24, 2026, 07:43 PM UTC

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

  17. monitoring Jun 25, 2026, 12:22 AM UTC

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

  18. monitoring Jun 25, 2026, 01:23 AM UTC

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

  19. monitoring Jun 25, 2026, 07:52 AM UTC

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

  20. monitoring Jun 25, 2026, 12:02 PM UTC

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

  21. resolved Jun 25, 2026, 04:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 16, 2026 Investigating potential delay in Vulnerability Management updates 6h 9m Sysdig Data Ingestion

Started Jun 16, 2026, 12:13 PM UTC· resolved Jun 16, 2026, 06:22 PM UTC

  1. investigating Jun 16, 2026, 12:13 PM UTC

    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. identified Jun 16, 2026, 01:53 PM UTC

    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. monitoring Jun 16, 2026, 03:24 PM UTC

    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. resolved Jun 16, 2026, 06:22 PM UTC

    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.

Read the full incident report →

Minor June 16, 2026 Vulnerability data ingestion delay impacting Vulnerability Overview and Findings 3h 48m Sysdig Secure, Sysdig Data Ingestion

Started Jun 16, 2026, 02:33 AM UTC· resolved Jun 16, 2026, 06:22 AM UTC

  1. identified Jun 16, 2026, 02:33 AM UTC

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

  2. monitoring Jun 16, 2026, 02:42 AM UTC

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

  3. monitoring Jun 16, 2026, 06:00 AM UTC

    We are continuing to monitor recovery of the system.

  4. resolved Jun 16, 2026, 06:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 6, 2026 Delay in Vulnerability Scan Results — US2 Region 1h 1m Sysdig Secure

Started May 06, 2026, 11:08 PM UTC· resolved May 07, 2026, 12:10 AM UTC

  1. investigating May 06, 2026, 11:08 PM UTC

    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. identified May 06, 2026, 11:22 PM UTC

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

  3. monitoring May 06, 2026, 11:46 PM UTC

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

  4. resolved May 07, 2026, 12:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 27, 2026 Report Generation Degradation 10h 23m Sysdig Secure

Started Apr 27, 2026, 09:11 PM UTC· resolved Apr 28, 2026, 07:34 AM UTC

  1. investigating Apr 27, 2026, 09:11 PM UTC

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

  2. identified Apr 27, 2026, 10:22 PM UTC

    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. monitoring Apr 28, 2026, 12:28 AM UTC

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

  4. monitoring Apr 28, 2026, 02:44 AM UTC

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

  5. monitoring Apr 28, 2026, 04:12 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Apr 28, 2026, 07:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 3, 2026 Degraded Performance for Agentless Scanning 1d 22h Sysdig Secure

Started Apr 03, 2026, 08:31 AM UTC· resolved Apr 05, 2026, 06:53 AM UTC

  1. investigating Apr 03, 2026, 08:31 AM UTC

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

  2. investigating Apr 03, 2026, 08:57 AM UTC

    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. investigating Apr 03, 2026, 11:34 AM UTC

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

  4. investigating Apr 03, 2026, 03:44 PM UTC

    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. monitoring Apr 03, 2026, 05:17 PM UTC

    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. monitoring Apr 03, 2026, 11:13 PM UTC

    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.

  7. monitoring Apr 04, 2026, 07:10 AM UTC

    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.

  8. monitoring Apr 04, 2026, 12:20 PM UTC

    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.

  9. monitoring Apr 04, 2026, 04:19 PM UTC

    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.

  10. monitoring Apr 04, 2026, 08:04 PM UTC

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

  11. monitoring Apr 04, 2026, 08:04 PM UTC

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

  12. monitoring Apr 04, 2026, 08:05 PM UTC

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

  13. monitoring Apr 05, 2026, 12:04 AM UTC

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

  14. monitoring Apr 05, 2026, 04:59 AM UTC

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

  15. resolved Apr 05, 2026, 06:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 17, 2026 Wrong policy data being reflected in compliance and inventory 3d 6h Sysdig Secure

Started Feb 17, 2026, 09:47 AM UTC· resolved Feb 20, 2026, 03:55 PM UTC

  1. investigating Feb 17, 2026, 09:47 AM UTC

    We are currently investigating the issue

  2. identified Feb 17, 2026, 11:58 AM UTC

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

  3. identified Feb 17, 2026, 02:16 PM UTC

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

  4. identified Feb 17, 2026, 04:26 PM UTC

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

  5. identified Feb 17, 2026, 05:35 PM UTC

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

  6. monitoring Feb 17, 2026, 09:57 PM UTC

    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

  7. investigating Feb 18, 2026, 07:03 AM UTC

    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.

  8. identified Feb 18, 2026, 09:42 AM UTC

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

  9. monitoring Feb 18, 2026, 05:12 PM UTC

    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.

  10. monitoring Feb 18, 2026, 09:55 PM UTC

    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.

  11. monitoring Feb 19, 2026, 12:21 AM UTC

    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.

  12. monitoring Feb 19, 2026, 08:58 AM UTC

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

  13. monitoring Feb 19, 2026, 07:53 PM UTC

    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.

  14. monitoring Feb 20, 2026, 01:05 AM UTC

    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.

  15. monitoring Feb 20, 2026, 10:36 AM UTC

    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.

  16. resolved Feb 20, 2026, 03:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 15, 2026 Partial Impact in Cost Metric Ingestion 1h 6m Sysdig Data Ingestion

Started Jan 15, 2026, 09:07 AM UTC· resolved Jan 15, 2026, 10:14 AM UTC

  1. monitoring Jan 15, 2026, 09:07 AM UTC

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

  2. resolved Jan 15, 2026, 10:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 13, 2026 Some AWS account CIEM scans are failing, impacting the freshness of CIEM insights 5h 9m Sysdig Secure

Started Jan 13, 2026, 03:21 PM UTC· resolved Jan 13, 2026, 08:30 PM UTC

  1. investigating Jan 13, 2026, 03:21 PM UTC

    We are currently investigating this issue.

  2. identified Jan 13, 2026, 05:13 PM UTC

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

  3. monitoring Jan 13, 2026, 06:40 PM UTC

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

  4. resolved Jan 13, 2026, 08:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 17, 2025 Attack Path visualization was down –

Started Dec 17, 2025, 02:00 PM UTC· resolved Dec 17, 2025, 02:00 PM UTC

  1. resolved Dec 17, 2025, 02:37 PM UTC

    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

Read the full incident report →

Minor December 1, 2025 Cloud Log Ingestion Failure from AWS us-east-1 workloads 8d 22h Sysdig Data Ingestion

Started Dec 01, 2025, 06:42 PM UTC· resolved Dec 10, 2025, 04:56 PM UTC

  1. investigating Dec 01, 2025, 06:42 PM UTC

    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. identified Dec 02, 2025, 06:39 PM UTC

    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. identified Dec 03, 2025, 05:19 PM UTC

    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. monitoring Dec 04, 2025, 07:48 PM UTC

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

  5. resolved Dec 10, 2025, 04:56 PM UTC

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

Read the full incident report →

Minor November 29, 2025 Delays in detection of policy events 18h 23m Sysdig Secure

Started Nov 29, 2025, 06:15 PM UTC· resolved Nov 30, 2025, 12:39 PM UTC

  1. investigating Nov 29, 2025, 06:15 PM UTC

    Customers may observe delays and/or misses in stateful detection policy events. The issue has been acknowledged, and our team is working to restore normal performance

  2. monitoring Nov 29, 2025, 06:37 PM UTC

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

  3. resolved Nov 30, 2025, 01:06 AM UTC

    This incident has been resolved.

Read the full incident report →