Datapacket's IP belongs to their own Autonomous system and 18.104.22.168 belongs to AdGuard's AS. We use different tweaks for our IP addresses to fix routing issues (i.e. a user routed to some server located far away) so the it's natural that the route for you to our AS is different from...
Datapacket.com is a hosting service that we rent AdGuard DNS servers from.
Any real server is located in some data center owned by some hosting company, that's how it works.
DNS servers are located all over the world, please check out the map on https://adguard-dns.io/
The problem with HTTP3 is that AdGuard cannot yet filter it so instead of that we suppress it and therefore the apps fallback to H2.
We're going to add full QUIC filtering capabilities in the future, though.
Could you please try installing the nightly version of AdGuard and check if the issue goes away.
One more thing, you may also need to do the following to "cure" the problem:
1. Open the new tab
2. Settings -> More Tools -> Developer Tools
3. Switch to the "Application" tab there
@SullyTheUnusual if the issue is still not resolved, could you please contact us at email@example.com?
We'll assign a developer that could try troubleshooting this issue one-on-one.
We'd prefer to escalate it to the developers team right away. macOS Monterey was just released and from our...
Okay, wait, I was too fast to judge. Actually, we fixed the issue from v7.6.
Here's how things are now:
1. Cosmetic filtering works in IE11.
2. Extended CSS rules work only partly in IE11.
3. Legacy AdGuard Assistant does not work in IE11 and we're not going to change this.
Hmm, that's quite weird that your organization decided to do that.
In theory, we have backup domains, but there's currently no way to switch to them manually.
We'll think about a solution, thank you for reporting this!