Qualys incident
Multiple Shared Platforms: Qualys Cloud Agent Stuck In Provisioning State Using Azure Extension (IM-12495)
Qualys experienced a minor incident on February 9, 2026 affecting Cloud Agent (CA) and Cloud Agent (CA) and 1 more component, lasting 2h 48m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Feb 09, 2026, 08:08 PM UTC
Qualys Cloud Operations has identified an issue where Qualys Cloud Agents attempting to be installed with the Azure Extension are stuck in the provisioning stage of the lifecycle. This appears to be the result of installing agents from the Azure Details section of an Activation Key within our newest Activation Key Tab (new UI). As a workaround, please install new Azure agents from within the activation key tab of Agent Management within our normal UI instance. Qualys Cloud Operations has identified a fix and is currently being tested. The ticket reference for this incident is IM-12495
- identified Feb 09, 2026, 08:18 PM UTC
We are continuing to test the fix. It has been deemed that the platforms below that have switched status from DEGRADED to OPERATIONAL are not impacted.
- resolved Feb 09, 2026, 10:57 PM UTC
This incident has been resolved.