Resolved -
This incident has been resolved.
Feb 23, 13:05 UTC
Update -
Compliance and Inventory data recovery continues to progress as expected. No new data loss has been detected.
We are closely monitoring recovery to ensure full consistency.
Further updates will be provided as necessary.
Feb 22, 18:37 UTC
Update -
Compliance and Inventory data recovery continues to progress as expected. No new data loss has been detected.
We are closely monitoring recovery to ensure full consistency.
Further updates will be provided as necessary.
Feb 21, 07:24 UTC
Update -
Compliance and Inventory data recovery continues to progress as expected.
Most customer environments have been successfully restored. A subset of customers, primarily in larger environments, may still observe partial data gaps while background processing and scans complete.
No new data loss has been detected. We remain actively engaged and are closely monitoring recovery to ensure full consistency.
Further updates will be provided as necessary.
Feb 20, 22:46 UTC
Update -
Data recovery is progressing across all customer environments. Smaller environments have largely restored, while larger environments continue processing backlog data. The incident remains in Monitoring.
We expect recovery to complete over the weekend. We will validate data completeness on Monday and provide a final update.
Feb 20, 18:48 UTC
Update -
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.
Feb 20, 15:55 UTC
Update -
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.
Feb 20, 10:36 UTC
Update -
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.
Feb 20, 01:05 UTC
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, 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, 08:57 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, 00:21 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, 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, 17:11 UTC
Identified -
The issue has been identified and a fix is being implemented.
Feb 18, 09:40 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, 07:02 UTC
Monitoring -
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, 21:57 UTC
Update -
We are continuing to work on a fix for this issue.
Feb 17, 17:35 UTC
Update -
We are continuing to work on a fix for this issue.
Feb 17, 16:26 UTC
Update -
We are continuing to work on a fix for this issue.
Feb 17, 14:16 UTC
Identified -
The issues has been identified and the team is working on a fix
Feb 17, 11:58 UTC
Investigating -
We are currently investigating the issue.
Feb 17, 09:47 UTC
