[AdGuard] DoH and DoT slow esponse time

Flint 2 running 4.8.3 and latest AGH version (v0.107.69)

Quad9 DoH

PING dns.quad9.net (149.112.112.112): 56 data bytes
64 bytes from 149.112.112.112: seq=0 ttl=54 time=7.484 ms
64 bytes from 149.112.112.112: seq=1 ttl=54 time=8.564 ms
64 bytes from 149.112.112.112: seq=3 ttl=54 time=8.335 ms
64 bytes from 149.112.112.112: seq=4 ttl=54 time=10.632 ms
64 bytes from 149.112.112.112: seq=5 ttl=54 time=8.281 ms
64 bytes from 149.112.112.112: seq=6 ttl=54 time=8.264 ms
64 bytes from 149.112.112.112: seq=7 ttl=54 time=8.505 ms
^C
--- dns.quad9.net ping statistics ---
8 packets transmitted, 7 packets received, 12% packet loss
round-trip min/avg/max = 7.484/8.580/10.632 ms

Cloudflare DoH

PING dns.cloudflare.com (172.64.41.8): 56 data bytes
64 bytes from 172.64.41.8: seq=0 ttl=53 time=3.753 ms
64 bytes from 172.64.41.8: seq=1 ttl=53 time=5.440 ms
64 bytes from 172.64.41.8: seq=2 ttl=53 time=5.432 ms
64 bytes from 172.64.41.8: seq=3 ttl=53 time=5.056 ms
64 bytes from 172.64.41.8: seq=4 ttl=53 time=4.986 ms
64 bytes from 172.64.41.8: seq=5 ttl=53 time=4.820 ms
^C
--- dns.cloudflare.com ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 3.753/4.914/5.440 ms

Rethink DoH

PING basic.rethinkdns.com (104.18.1.48): 56 data bytes
64 bytes from 104.18.1.48: seq=0 ttl=53 time=5.421 ms
64 bytes from 104.18.1.48: seq=1 ttl=53 time=4.974 ms
64 bytes from 104.18.1.48: seq=2 ttl=53 time=5.074 ms
64 bytes from 104.18.1.48: seq=3 ttl=53 time=4.886 ms
64 bytes from 104.18.1.48: seq=4 ttl=53 time=5.905 ms
64 bytes from 104.18.1.48: seq=5 ttl=53 time=5.612 ms
^C
--- basic.rethinkdns.com ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 4.886/5.312/5.905 ms

Any idea why AGH reports such high numbers in the interface for encrypted protocols?

Hi

This appears to be a known issue with AdGuard Home:
Very slow and increasing "Average upstream response time" · Issue #6818 · AdguardTeam/AdGuardHome · GitHub

Please try restarting the router to clear the AdGuard Home logs and then observe whether the slowdown continues.
If you are using the admon script and have enabled persistent logs, be sure to delete the stored log files as well.

If DoH/DoT response times are still slow afterward, you can SSH into router, measure the actual query processing time with the commands below and check if it matches what ADG Home displays.
If it does, it may be a network issue.

For DoH:

while true; do /usr/bin/time -f "Query Time: %e seconds" dig +https @cloudflare-dns.com google.com > /dev/null ; sleep 1; done

For DoT:

while true; do /usr/bin/time -f "Query Time: %e seconds" dig +tls @one.one.one.one google.com > /dev/null ; sleep 1; done