Resolved -
This incident has been resolved.
Mar 25, 05:57 PDT
Update -
We are continuing to monitor for any further issues.
Mar 25, 04:43 PDT
Monitoring -
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
Mar 25, 03:51 PDT
Update -
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.
Mar 25, 03:50 PDT
Update -
We are continuing to work on a fix for this issue.
Mar 24, 17:09 PDT
Update -
We are continuing to work on a fix for this issue.
Mar 24, 04:48 PDT
Update -
We are continuing to work on a fix for this issue.
Mar 24, 00:38 PDT
Update -
We are continuing to work on a fix for this issue.
Mar 23, 23:27 PDT
Update -
We are continuing to work on a fix for this issue.
Mar 23, 23:22 PDT
Update -
We are continuing to work on a fix for this issue.
Mar 23, 17:29 PDT
Update -
We are continuing to work on a fix for this issue.
Mar 19, 08:16 PDT
Identified -
The issue has been identified and a fix is being implemented.
Mar 18, 10:14 PDT
Update -
We are continuing to investigate this issue.
Mar 18, 01:28 PDT
Update -
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
Mar 18, 01:28 PDT
Investigating -
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
Mar 17, 00:59 PDT