Historial de interrupciones de Sysdig Us East 1

We are investigating an issue impacting the processing of Posture and Compliance data. Customers may experience delays in new Posture and Compliance results appearing in dashboards and reports. Previously collected data remains available. We are actively investigating the issue and working to restore normal processing. We will provide another update as more information becomes available.

We have deployed a fix and processing of Posture and Compliance data has resumed successfully. New Posture and Compliance results are now being processed and should appear normally in dashboards and reports. We are continuing to monitor the service to ensure processing remains stable and will provide another update as appropriate.

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 an issue affecting the Risk feature, which is currently unavailable. Our team is working to resolve the issue and will provide updates as soon as more information becomes available.

The issue affecting the Risk feature has been resolved. We are continuing to monitor to ensure stability.

We are currently investigating the issue.

Sysdig has become aware of an alerting issue which may cause customers to not receive triggered alerts since alert notifications are being dropped. We are actively investigating the issue and will post further updates.

A fix has been implemented and alerting is functional again. We are actively monitoring the situation to ensure continued stability.

This incident has been resolved.

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.

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

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 continuing to monitor for any further issues.

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.

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.

VM Overview and Threats Overview pages are not showing data in dashboards. Our team has identified the issue and is actively working on a fix.

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.

We are experiencing problems with login to secure. We have identified the problem and are working on a fix.

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.

from 7:30am to 9:30am UTC because of a problem with our upstream cloud provider

We have identified an issue causing delays in risk updates. Customers may experience degraded performance with automated risk-related operations. Our team is actively deploying a fix and we will provide updates as recovery 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 experiencing degraded performance with alert calculations and dashboards because of delayed metrics ingestion. Our team has identified the issue and is actively working on a fix.

This incident has been resolved.

We are currently investigating this issue.

Detection notifications were sent once and will not reoccur.

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.

Resource Type: Image drawer not available under “Inventory” in Sysdig Secure, we are currently working on a fix

This incident has been resolved.

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

This incident has been resolved.

Sysdig has become aware of a data ingestion issue, which may cause some customers to experience gaps in populated graphs, network timeouts while communicating with the cloud platform, or alerts triggered incorrectly. 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.

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 identified as a problem with EPSS score. Our team is working on a fix, and we are targeting the beginning of next week for full resolution.

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

This incident has been resolved.