You used the term “NATO stan” and call my response a cliche? I could tell you were a .ml user without even looking at your account.

The irony is entertaining. Thanks for the laugh, tanky

User instance checks out

Ayyyy awesome! Glad to hear you’re getting full speeds now!

I’ve personally run into this before, when I got my first gigabit connection. Definitely took me a long time to track it down, and required someone on SmallNetBuilders forum telling me about it haha

With a gigabit connection, you shouldn’t really need QoS, unless your upstream is getting saturated (since I don’t think the coax gigabit providers offer symmetric up/down). But if you do, you’ll want to get another device to do it, or use more simple approaches like just capping throughput per device. If you don’t already have a homelab server, a recent Raspberry Pi should be able to handle it (and then you’d also be able to set up PiHole and other fun self-hosted services)

Issue 1: Don’t use the speed test on your router. Use OpenSpeedTest on your desktop browser. Router hardware isn’t made for this type of function and can often pass traffic (using hardware acceleration) faster than it can decode packets (using the CPU, required for speed tests).

Issue 2: test at off-peak times of day. Last mile for ISPs can get congested and limit actual speeds

Issue 3: Disable QoS, detailed traffic analysis, or other packet-inspection tech on your router. These often require passing the packets through the CPU which can limit max throughput. Check to be sure that “hardware acceleration” is active if possible for your router (sometimes called “cut through forwarding”). This can impact WAN <=> LAN traffic by not LAN-only as it needs to be bridged in a way that LAN-only traffic doesn’t.