Critical incident

PDQ: Connect Incident - Intermittent Connect Outages

Affected: Deployments, Device Scans, Package Library, Vulnerability Management

Current status of PDQ: Operational — live PDQ status

Timeline

1. Apr 17, 2026, 03:48 UTC
   investigating
   We are currently experiencing issues with degradation of Connect services. You may experience slower than normal responses for deployments, etc.
2. Apr 17, 2026, 06:07 UTC
   monitoring
   A fix has been implemented and we are monitoring the results.
3. Apr 17, 2026, 06:08 UTC
   identified
   The issue has been identified and a fix is being implemented.
4. Apr 17, 2026, 06:19 UTC
   identified
   We are continuing to work on a fix for this issue.
5. Apr 17, 2026, 07:57 UTC
   identified
   All Connect services are currently down. We are continuing to work on a fix.
6. Apr 17, 2026, 08:50 UTC
   identified
   We've applied a fix and we're working to get services back to normal.
7. Apr 17, 2026, 08:51 UTC
   identified
   We are continuing to work on a fix for this issue.
8. Apr 17, 2026, 09:22 UTC
   monitoring
   A fix has been implemented and we are monitoring the results.
9. Apr 17, 2026, 13:59 UTC
   identified
   Connect is currently experiencing issues with Deployments and other services. We're working on a fix for the issue and hope to have things back up and running soon.
10. Apr 17, 2026, 18:32 UTC
    identified
    Connect is experiencing intermittent outages and service degradation. We're working on a fix for the issue and hope to have things back up and running soon
11. Apr 17, 2026, 20:17 UTC
    identified
    All Connect services are currently down and we are working to restore service. Thank you for your patience.
12. Apr 17, 2026, 21:09 UTC
    identified
    PDQ Connect is currently experiencing a service disruption that began at approximately 12:00 AM ET (04:00 UTC) April 17th. The issue is related to an unexpected database problem that has caused the application to be intermittently unavailable and has resulted in delays in deployment and device data processing. Our team is actively working to resolve the issue and restore full service. We apologize for the disruption and will provide updates as they become available.
13. Apr 18, 2026, 03:14 UTC
    monitoring
    A fix has been implemented and we are monitoring the results
14. Apr 18, 2026, 04:07 UTC
    resolved
    This incident has been resolved.

Updates as published by PDQ (original).