Sysdig Us West 2 장애 기록

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.

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

This incident has been resolved.

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.

We are continuing to investigate the issue.

We are continuing to investigate the issue.

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

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 processing delay in the data ingestion pipeline is currently impacting vulnerability page visibility for US2 customers, with a fix deployed and full recovery expected

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

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

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.

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

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.

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.

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.

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

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

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

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. The issue was solved at 12.18pm UTC

We are currently investigating the issue

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

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

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

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.

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

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.

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.

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.

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

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.

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.

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.

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.

We are experiencing degraded performance in the creation of Jira tickets as part of our Vulnerability Management automation. A fix is being deployed and investigation is ongoing.

We continue to observe delays in the Jira ticket creation workflow used in our vulnerability management automation and our team is actively investigating. We will share more information as the analysis progresses.

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

We have identified that the delays in Jira ticket creation are caused by slow query execution in our backend data service. The team has applied a temporary mitigation by reducing the query timeframe, which has improved success rates partially, but the issue is not fully resolved. We are continuing to work on optimizations to restore normal performance. Further updates will be provided as progress is made.

A partial mitigation is in place that allows Jira ticket creation to succeed intermittently, reducing user impact. Performance is still not fully stable, and our team is continuing work on the underlying query optimization. We will provide further updates as improvements are made.

We've implemented a backend query optimization that has already improved Jira ticket creation performance, with early results showing noticeably faster execution times. We're continuing to monitor behaviour across all regions, while our teams validate the fix, review data consistency, and assess stability before making further changes. We'll share additional updates as we confirm sustained improvement.

We have identified the root cause of the delays in Jira ticket creation and deployed a fix to address the related issue. The update is now live in all affected regions. Our teams are actively monitoring the environment to ensure the service remains stable and fully restored. We will provide further updates as we confirm full resolution.

Recent backend efficiency enhancements have been deployed, and early results show improved stability. Our teams continue to monitor the system closely to ensure consistent behavior across all environments. Further updates will be shared as we validate full resolution.

We are continuing to monitor for any further issues.

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 currently investigating an issue causing Cloud Metrics in Azure to be unavailable due to upstream service failures at Microsoft Azure.

We are continuing to investigate this issue.

Upon further investigation, the unavailability alert was triggered by a single customer integration that was manually disabled at 19:56 UTC. No broader customer impact has been observed, and Azure services continue to recover as expected. This incident is now considered a false positive alert, and Cloud Metrics functionality remains healthy for all active integrations. We will continue to monitor Azure’s recovery progress, but no active degradation is present on our side.