Qualys incident

Multiple Shared Platforms: Qualys Cloud Agent Stuck In Provisioning State Using Azure Extension (IM-12495)

Minor Resolved View vendor source →
Started
Feb 09, 2026, 08:08 PM UTC
Resolved
Feb 09, 2026, 10:57 PM UTC
Duration
2h 48m
Detected by Pingoru
Feb 09, 2026, 08:08 PM UTC

Affected components

Cloud Agent (CA)Cloud Agent (CA)Cloud Agent (CA)Cloud Agent (CA)Cloud Agent (CA)Cloud Agent (CA)Cloud Agent (CA)Cloud Agent (CA)Cloud Agent (CA)Cloud Agent (CA)Cloud Agent (CA)Cloud Agent (CA)Cloud Agent (CA)Cloud Agent (CA)

Update timeline

  1. 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

  2. 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.

  3. resolved Feb 09, 2026, 10:57 PM UTC

    This incident has been resolved.

Looking to track Qualys downtime and outages?

Pingoru polls Qualys's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Qualys reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Qualys alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Qualys for free

5 free monitors · No credit card required