Qualys incident

US Platform 3: Delay in Data Reflection in UI (IM-12795)

Minor Resolved View vendor source →

Qualys experienced a minor incident on August 11, 2026 affecting Global AssetView (GAV) /CyberSecurity Asset Management (CSAM) and AssetView (AV) and 1 more component, lasting 2d 19h. The incident has been resolved; the full update timeline is below.

Started
Aug 11, 2026, 03:54 PM UTC
Resolved
Aug 14, 2026, 11:14 AM UTC
Duration
2d 19h
Detected by Pingoru
Aug 11, 2026, 03:54 PM UTC

Affected components

Global AssetView (GAV) /CyberSecurity Asset Management (CSAM)AssetView (AV)Cloud Agent (CA)Total CloudVulnerability Management (VM)Unified Dashboard (UD)Qualys Flow (QFLOW)

Update timeline

  1. investigating Aug 11, 2026, 03:54 PM UTC

    Qualys Cloud Platform Operations is currently investigating an issue on US Platform 3 that is causing an indexing delay. Users will notice that information takes longer than expected to become visible within AssetView, VM Dashboard, Cloud Agent UI, CSAM/GAV, and Unified Dashboard. Further updates will be shared as they become available. The ticket reference for this incident is IM-12795

  2. investigating Aug 11, 2026, 09:52 PM UTC

    We are continuing to investigate the issue and are working to identify the underlying cause. We will provide additional updates as more information becomes available.

  3. investigating Aug 12, 2026, 01:41 PM UTC

    Qualys Operations and Engineering teams continue working on the issue that is causing the indexing delay. We will provide additional updates as more information becomes available.

  4. investigating Aug 12, 2026, 05:22 PM UTC

    We are continuing to investigate this issue.

  5. investigating Aug 12, 2026, 05:23 PM UTC

    We are continuing to investigate this issue.

  6. identified Aug 12, 2026, 09:26 PM UTC

    We have identified the underlying cause of the issue and are working to implement a mitigation. We will continue to provide updates on our progress.

  7. monitoring Aug 13, 2026, 03:19 PM UTC

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

  8. resolved Aug 14, 2026, 11:14 AM UTC

    This incident has been resolved.