Is AdGuard DNS down today?

DNS queries not resolving at all

If sites stop opening completely after switching to AdGuard DNS, the most likely cause is a misconfigured resolver address. Double-check that you''re using the correct IP: 94.140.14.14 and 94.140.15.15 for the default server, or the addresses from your Personal dashboard if you''re on a linked profile. On Windows, flush the DNS cache after any change: run ipconfig /flushdns in an elevated command prompt, then test again.

Banking site or app gets blocked

Online banking apps like Chase, Revolut, or HSBC sometimes fail to load because their anti-fraud or telemetry domains end up on a blocklist. Open the AdGuard DNS dashboard, go to Query Log, and filter by ''Blocked''. Find the domain the app is trying to reach and add it to your personal Allowlist. If you don''t have a linked account, switch temporarily to the Non-filtering server (94.140.14.140) to confirm the blocker is the culprit.

Specific websites load, others don''t

- Check the Query Log — the blocked domain shows up with a red label

- Add the domain to the Allowlist under Settings → Filters

- If the site uses a CDN, you may need to allowlist several related domains

- Clear browser cache after making changes — stale records can persist for minutes

High latency on DNS lookups

Ping times above 80–100 ms usually mean your device is hitting a geographically distant server. AdGuard DNS routes automatically, but if you''re using a hardcoded IP in router settings, try switching to the DoH or DoT endpoint instead — these support proper anycast routing and typically drop latency significantly.

Dashboard login errors

If the personal dashboard at adguard-dns.io refuses your credentials, try a different browser first — extensions from other security tools occasionally interfere with the auth flow. If the issue persists, use the ''Forgot password'' flow; the reset email sometimes lands in spam. Session tokens also expire after long inactivity, so simply logging out and back in resolves most ''access denied'' errors.

Filtering rules not applying

- New blocklists take up to 24 hours to propagate after enabling

- Custom rules in the User Rules section apply immediately — use these for urgent fixes

- Syntax errors in custom rules silently break the entire rule set; validate format against AdGuard DNS documentation

- Devices linked to a profile inherit its settings only after a DNS cache flush on the device side