Live / PDQ / Incident
PDQ: Automations are falling behind for some customers
PDQ · pdq.comResolved2026-10-20 18:02 UTC
Public — what happened
Summary
PDQ said that automations were running behind for some of its customers, though it did not say how many were affected. The company reported the problem beginning at 17:22 UTC on 2026-10-20, and said it had dealt with a backup and found a possible solution while it watched the situation. At 17:46 UTC PDQ said it was rolling out a fix for the root cause it had identified, and the incident was marked resolved at 18:02.
Affected
Automations
Timeline
- Started — 2026-10-20 17:22 UTC
- Monitoring — 2026-10-20 17:22 UTC (2 updates)
- Resolved — 2026-10-20 18:02 UTC · 40 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach PDQ against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for PDQ: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the PDQ report →
More from PDQ
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.