PDQ experienced a critical incident on April 17, 2026 affecting Deployments and Device Scans and 1 more component, lasting 1d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 17, 2026, 03:48 AM UTC
We are currently experiencing issues with degradation of Connect services. You may experience slower than normal responses for deployments, etc.
- monitoring Apr 17, 2026, 06:07 AM UTC
A fix has been implemented and we are monitoring the results.
- identified Apr 17, 2026, 06:08 AM UTC
The issue has been identified and a fix is being implemented.
- identified Apr 17, 2026, 06:19 AM UTC
We are continuing to work on a fix for this issue.
- identified Apr 17, 2026, 07:57 AM UTC
All Connect services are currently down. We are continuing to work on a fix.
- identified Apr 17, 2026, 08:50 AM UTC
We've applied a fix and we're working to get services back to normal.
- identified Apr 17, 2026, 08:51 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Apr 17, 2026, 09:22 AM UTC
A fix has been implemented and we are monitoring the results.
- identified Apr 17, 2026, 01:59 PM UTC
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.
- identified Apr 17, 2026, 06:32 PM UTC
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
- identified Apr 17, 2026, 08:17 PM UTC
All Connect services are currently down and we are working to restore service. Thank you for your patience.
- identified Apr 17, 2026, 09:09 PM UTC
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.
- monitoring Apr 18, 2026, 03:14 AM UTC
A fix has been implemented and we are monitoring the results
- resolved Apr 18, 2026, 04:07 AM UTC
This incident has been resolved.