PDQ incident
Connect Incident - Delayed processing of Device Vulnerabilities
PDQ experienced a minor incident on July 14, 2026 affecting Automations and Deployments and 1 more component, lasting 1d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 14, 2026, 08:21 PM UTC
Connect is currently experiencing long delays in updating device group counts and Connect application data. We are currently investigating the issue. Thank you for your patience.
- identified Jul 14, 2026, 08:36 PM UTC
The issue has been identified and a fix is being implemented.
- identified Jul 14, 2026, 08:55 PM UTC
The issue has been identified and we're working on a fix. Thank you for your patience.
- identified Jul 14, 2026, 09:22 PM UTC
A fix has been implemented and things are trending back to looking normal.
- monitoring Jul 14, 2026, 09:26 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jul 14, 2026, 09:30 PM UTC
We are continuing to monitor for any further issues.
- monitoring Jul 14, 2026, 10:06 PM UTC
Due to patch Tuesday, Vulnerabilities backlog is still catching up in workload and will likely take a while to catch up. More updates to come.
- identified Jul 15, 2026, 12:36 PM UTC
Vulnerability results in PDQ Connect are currently delayed by up to ~3 hours. Newly detected vulnerabilities may appear late, patched ones may take longer to show as resolved, and vulnerability counts/groups may be briefly out of date. No data is lost and no action is needed. Deployments, device inventory & scans, and application scans are operating normally.
- identified Jul 15, 2026, 04:41 PM UTC
Our engineering team continues to actively work on this issue. We've deployed several optimizations today and have additional fixes under review that we expect to further reduce processing time.
- monitoring Jul 15, 2026, 08:47 PM UTC
This afternoon our engineering team deployed a series of fixes that reduced unnecessary database load from vulnerability processing, which has allowed us to more than double our processing throughput. The vulnerability queue is now draining rapidly, and we expect vulnerability data to be fully caught up within the next several hours.
- resolved Jul 15, 2026, 11:15 PM UTC
This incident has been resolved.