Live  /  AdGuard  /  Incident

AdGuard: AdGuard DNS - DNS resolution issues in Sydney, London and Amsterdam

AdGuard · adguard.comMinor incidentResolved2026-10-02 15:59 UTC
Public — what happened

Summary

AdGuard reported a minor problem with its AdGuard DNS service on October 2, 2026, beginning at 15:26 UTC, where looking up websites was failing for users connecting through its Sydney, London and Amsterdam locations. The company said the trouble stemmed from shifts in how traffic was being routed across the global network, and that it was redistributing load to get things working again. AdGuard marked the incident as resolved at 15:59, roughly half an hour after it began.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 41, 2026, our weekly internet health report.

The full archive is on the AdGuard status & history page.

Related: AdGuard status & history. SquidGrid is not affiliated with AdGuard.