Is AdGuard DNS down in South Africa today?

DNS Queries Not Resolving at All

If domains stop resolving entirely, the first thing to check is whether the correct DNS server addresses are set. AdGuard DNS uses 94.140.14.14 and 94.140.15.15 for the default profile. If you configured it manually on a router or device and later changed your profile settings, the linked IP might have shifted — go to your dashboard and verify the addresses under ''Setup Guide''.

Specific Sites Suddenly Blocked

This usually means the domain landed on one of the active filterlists in your profile. Open the query log in the web dashboard, find the blocked domain, and check which rule triggered the block. You can add the domain to your allowlist directly from that screen. Keep in mind that some ad-blocking lists aggressively flag CDN endpoints used by streaming services like Twitch or Hulu.

Online Banking App Stops Working

Banking apps often rely on analytics or anti-fraud SDKs that get caught by default filters. If your bank''s app throws a connection error or login fails:

- Temporarily switch your profile to a less strict configuration

- Check the query log filtered by your device to spot what''s being blocked

- Allowlist the specific domains rather than disabling filtering entirely

High Latency on DNS Resolution

If pages feel sluggish and you''ve confirmed the issue is DNS (not your ISP), check which server location is set. Using a geographically distant endpoint adds measurable delay. Switch to the anycast address and run a comparison with ''nslookup'' or ''dig'' to measure actual response time before and after.

Private DNS Profile Not Applying

On Android, the Private DNS (DoT) option sometimes reverts or silently fails after a system update. Go to Network settings, clear the Private DNS field, save, then re-enter your personal AdGuard DNS hostname (found in the dashboard under ''DNS-over-TLS''). A hostname typo — even a single character — will cause silent fallback to your ISP''s resolver.

Query Log Shows No Devices

If the log is empty despite active browsing, the device isn''t actually using your configured profile. This often happens when a local router overrides DNS settings pushed to clients. Check your router''s DHCP configuration and make sure it''s not advertising its own DNS address instead of forwarding to the correct servers.