| Aspect | Implication at 0.165 | |--------|----------------------| | No compression | Payload bytes = wire bytes. No gain from gzip or video encoding. | | No caching | Every byte is sourced fresh from origin; no local or proxy hits. | | No overhead subtraction | The measured 0.165 is application-layer throughput, not link-layer. |

# Server side (listener) iperf3 -s -p 5201 iperf3 -c <server_ip> -p 5201 -R -t 60 -f m --omit 3

A pure 0.165 download is a niche but precisely defined network state. It is too slow for general web browsing or media streaming but perfectly suited for constrained IoT, low-power telemetry, and rate-shaping validation. When encountered unexpectedly, it points directly to a hard policer, a pathologically small TCP window, or a link operating at its absolute physical floor. Its purity makes it an excellent reference for benchmarking low-bandwidth behavior without the confounding variables of compression, caching, or protocol overhead. Need this adapted for a specific audience (e.g., non‑technical stakeholders, developers, or network engineers)? Let me know and I can re‑layer the explanation.

Expect output similar to: