Live / AdGuard / Incident
AdGuard: AdGuard DNS - DNS resolution issues in Amsterdam
AdGuard · adguard.comMinor incidentResolved2026-10-08 15:07 UTC
Public — what happened
Summary
AdGuard reported a minor problem with its AdGuard DNS service in which servers located in Amsterdam had trouble resolving DNS requests, starting at 11:55 UTC on October 8, 2026. The company said the trouble stemmed from abrupt shifts in global network routing, and that it was redistributing traffic load to get the service working normally again. The incident was marked resolved at 15:07 the same day.
Affected
AdGuard DNS
Timeline
- Started — 2026-10-08 11:55 UTC
- Investigating — 2026-10-08 11:55 UTC
- Resolved — 2026-10-08 15:07 UTC · 3h 12m 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 42, 2026, our weekly internet health report.