Qualys incident

US Platform 1, US Platform 2, US Platform 3, US Platform 4, EU Platform 1, EU Platform 2, AU Platform 1, UK Platform1, AE Platform 1 : Scheduled Reports Impacted (IM-12593)

Notice Resolved View vendor source →

Qualys experienced a notice incident on April 16, 2026 affecting Vulnerability Management (VM) and Vulnerability Management (VM) and 1 more component, lasting 5d 1h. The incident has been resolved; the full update timeline is below.

Started
Apr 16, 2026, 01:48 PM UTC
Resolved
Apr 21, 2026, 02:54 PM UTC
Duration
5d 1h
Detected by Pingoru
Apr 16, 2026, 01:48 PM UTC

Affected components

Vulnerability Management (VM)Vulnerability Management (VM)Vulnerability Management (VM)Vulnerability Management (VM)Vulnerability Management (VM)Vulnerability Management (VM)Vulnerability Management (VM)Vulnerability Management (VM)Vulnerability Management (VM)Vulnerability Management (VM)

Update timeline

  1. investigating Apr 16, 2026, 01:48 PM UTC

    US Platform 1, US Platform 2, US Platform 3, US Platform 4, EU Platform 1, EU Platform 2, AU Platform 1, UK Platform1, AE Platform 1 are currently experiencing issues where the scheduled report was not launched at the scheduled time. The Qualys Cloud Platform Operations team is actively investigating the issue. Reference Incident: IM-12593

  2. investigating Apr 16, 2026, 02:03 PM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 16, 2026, 02:05 PM UTC

    We are continuing to investigate this issue.

  4. investigating Apr 16, 2026, 02:10 PM UTC

    We are continuing to investigate this issue.

  5. investigating Apr 16, 2026, 02:19 PM UTC

    We are continuing to investigate this issue.

  6. investigating Apr 16, 2026, 02:20 PM UTC

    We are continuing to investigate this issue.

  7. investigating Apr 16, 2026, 02:27 PM UTC

    We are continuing to investigate this issue.

  8. identified Apr 16, 2026, 06:16 PM UTC

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

  9. monitoring Apr 16, 2026, 11:36 PM UTC

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

  10. monitoring Apr 17, 2026, 05:49 PM UTC

    We are continuing to monitor for any further issues.

  11. resolved Apr 21, 2026, 02:54 PM UTC

    This incident has been resolved.