Live / AdGuard / Incident
AdGuard: AdGuard DNS - no fresh query logs
AdGuard · adguard.comResolved2026-11-03 23:07 UTC
Public — what happened
Summary
AdGuard said its AdGuard DNS service was not showing recent query logs, and it began looking into the problem at 20:29 UTC on 2026-11-03. By 20:55 UTC the company reported a temporary fix and said users might still see a gap of roughly six hours in their logs, though it said no data was actually lost. At 22:40 UTC it said it was filling in the missing logs, and the incident was marked resolved at 23:07 UTC.
Affected
AdGuard DNS
Timeline
- Started — 2026-11-03 20:29 UTC
- Investigating — 2026-11-03 20:29 UTC
- Identified — 2026-11-03 20:55 UTC (2 updates)
- Resolved — 2026-11-03 23:07 UTC · 2h 38m 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 AdGuard 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 AdGuard: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the AdGuard report →
More from AdGuard
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.