Update - 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.
Feb 19, 2026 - 19:53 UTC
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.
Feb 19, 2026 - 19:53 UTC
Update - Compliance and Inventory data is recovering as expected.
We are actively monitoring the situation and will provide further updates if necessary.
Feb 19, 2026 - 08:58 UTC
We are actively monitoring the situation and will provide further updates if necessary.
Feb 19, 2026 - 08:58 UTC
Update - 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.
Feb 19, 2026 - 00:20 UTC
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.
Feb 19, 2026 - 00:20 UTC
Update - 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.
Feb 18, 2026 - 21:55 UTC
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.
Feb 18, 2026 - 21:55 UTC
Monitoring - 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.
Feb 18, 2026 - 17:11 UTC
The incident status has been moved to Monitoring while we continue validating stability.
Feb 18, 2026 - 17:11 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 18, 2026 - 09:41 UTC
Feb 18, 2026 - 09:41 UTC
Investigating - 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.
Feb 18, 2026 - 07:03 UTC
We are actively investigating the issue.
Feb 18, 2026 - 07:03 UTC
Update - 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.
Feb 17, 2026 - 21:57 UTC
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.
Feb 17, 2026 - 21:57 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 17, 2026 - 21:56 UTC
Feb 17, 2026 - 21:56 UTC
Update - We are continuing to work on a fix for this issue.
Feb 17, 2026 - 17:35 UTC
Feb 17, 2026 - 17:35 UTC
Update - We are continuing to work on a fix for this issue.
Feb 17, 2026 - 16:26 UTC
Feb 17, 2026 - 16:26 UTC
Update - We are continuing to work on a fix for this issue.
Feb 17, 2026 - 14:13 UTC
Feb 17, 2026 - 14:13 UTC
Identified - The issues has been identified and the team is working on a fix
Feb 17, 2026 - 11:58 UTC
Feb 17, 2026 - 11:58 UTC
Investigating - We are currently investigating the issue
Feb 17, 2026 - 09:48 UTC
Feb 17, 2026 - 09:48 UTC
About This Site
The status of Sysdig running in our US-East-1 region.
Interested in the status of Sysdig running in our AP-South-1 region? Go to https://status-in1.sysdig.com
Interested in the status of Sysdig running in our AP-SouthEast-2 region? Go to https://status-au1.sysdig.com
Interested in the status of Sysdig running in our EU-Central-1 region? Go to https://status-eu1.sysdig.com
Interested in the status of Sysdig running in our US-West-1 region? Go to https://status-us4.sysdig.com
Interested in the status of Sysdig running in our US-West-2 region? Go to https://status-us2.sysdig.com
Interested in the status of Sysdig running in our EU-North-1 region? Go to https://status-eu2.sysdig.com
Sysdig Monitor
Operational
Sysdig Secure
Degraded Performance
Sysdig Data Ingestion
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.