Wrong policy data being reflected in compliance and inventory

Update timeline

1. investigating Feb 17, 2026, 09:48 AM UTC

   We are currently investigating the issue

2. identified Feb 17, 2026, 11:58 AM UTC

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

3. identified Feb 17, 2026, 02:13 PM UTC

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

4. identified Feb 17, 2026, 04:26 PM UTC

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

5. identified Feb 17, 2026, 05:35 PM UTC

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

6. monitoring Feb 17, 2026, 09:56 PM UTC

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

7. monitoring Feb 17, 2026, 09:57 PM UTC

   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.

8. investigating Feb 18, 2026, 07:03 AM UTC

   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.

9. identified Feb 18, 2026, 09:41 AM UTC

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

10. monitoring Feb 18, 2026, 05:11 PM UTC

    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.

11. monitoring Feb 18, 2026, 09:55 PM UTC

    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.

12. monitoring Feb 19, 2026, 12:20 AM UTC

    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.

13. monitoring Feb 19, 2026, 08:58 AM UTC

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

14. monitoring Feb 19, 2026, 07:53 PM UTC

    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.

15. monitoring Feb 20, 2026, 01:05 AM UTC

    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.

16. monitoring Feb 20, 2026, 10:34 AM UTC

    We are continuing to monitor for any further issues.

17. resolved Feb 20, 2026, 10:35 AM UTC

    This incident has been resolved.