Qualys incident

US POD 1, US POD 2, US POD 3, EU POD 1, EU POD 2, CA POD 1, IN POD 1: External WAS scans that are configured with custom or standard authentication are encountering an error (IM-12547)

Major Resolved View vendor source →

Qualys experienced a major incident on March 17, 2026 affecting Web Application Scanning (WAS) and Web Application Scanning (WAS) and 1 more component, lasting 8d 4h. The incident has been resolved; the full update timeline is below.

Started
Mar 17, 2026, 07:59 AM UTC
Resolved
Mar 25, 2026, 12:57 PM UTC
Duration
8d 4h
Detected by Pingoru
Mar 17, 2026, 07:59 AM UTC

Affected components

Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)Web Application Scanning (WAS)

Update timeline

  1. investigating Mar 17, 2026, 07:59 AM UTC

    Qualys Cloud Operations is currently investigating an issue affecting external WAS scans configured with custom or standard authentication, which are encountering errors. Further updates will be shared as they become available. The ticket reference for this incident is IM-12547

  2. investigating Mar 18, 2026, 08:28 AM UTC

    We are continuing to investigate this issue. Further updates will be shared as they become available. The ticket reference for this incident is IM-12547

  3. investigating Mar 18, 2026, 08:28 AM UTC

    We are continuing to investigate this issue.

  4. identified Mar 18, 2026, 05:14 PM UTC

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

  5. identified Mar 19, 2026, 03:16 PM UTC

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

  6. identified Mar 24, 2026, 12:29 AM UTC

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

  7. identified Mar 24, 2026, 06:22 AM UTC

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

  8. identified Mar 24, 2026, 06:27 AM UTC

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

  9. identified Mar 24, 2026, 07:38 AM UTC

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

  10. identified Mar 24, 2026, 11:48 AM UTC

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

  11. identified Mar 25, 2026, 12:09 AM UTC

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

  12. identified Mar 25, 2026, 10:50 AM UTC

    Fix has been deployed on EU1, EU2, CA, US1, US2, US3 and IN POD. We will update once the fix is deployed on pending PODs.

  13. monitoring Mar 25, 2026, 10:51 AM UTC

    Fix has been deployed on EU1, EU2, CA, US1, US2, US3, and IN PODs. As this issue was observed after the Portal 3.23.1.0 Deployment, and for the rest of the pods fix will go alongside the Portal 3.23.1.0 Deployment as scheduled

  14. monitoring Mar 25, 2026, 11:43 AM UTC

    We are continuing to monitor for any further issues.

  15. resolved Mar 25, 2026, 12:57 PM UTC

    This incident has been resolved.