Sysdig US-West-2 had 27 outages in the last 2 years totaling 702h 5m of downtime — averaging 1.1 incidents per month.
There were 27 Sysdig US-West-2 outages since October 22, 2025 totaling 702h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
A fix has been implemented and we are currently monitoring the results to ensure full recovery.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Customers can observe Cost Advisor data to be missing for Azure clusters. We are currently investigating the issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
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
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.
Customers may observe delays and/or misses in stateful detection policy events. We are currently investigating the issue.
A fix has been implemented and we are monitoring the recovery.
This incident has been resolved.
We are currently investigating the issue
This incident has been resolved.
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.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We have a fix in place we are working on processing the backlog of data and verifying that the fix it's correct.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
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.
This incident has been resolved.
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.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
The fix is working as expected and we're actively monitoring until full recovery.
We're actively monitoring the recovery and will provide further updates as necessary.
We're actively monitoring the recovery and will provide further updates as necessary.
We're actively monitoring the recovery and will provide further updates as necessary
This incident has been resolved.
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.
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
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.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor recovery of the system.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue that may affect report generation. In some cases, reports may be created without displaying data.
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.
A fix has been implemented and we are monitoring the results.
We are currently monitoring the system to ensure report generation is functioning as expected. Updates will be shared as needed.
We are continuing to monitor for any further issues.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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
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.
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.
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.
Log ingestion is functional. We are currently processing the accumulated event backlog.
Our monitoring confirms that log ingestion is functioning as expected and no further delays or drops are occurring. We are now closing the incident.
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
A fix has been implemented and we are monitoring the results.
This incident has been resolved.