Here is what she looks like currently. Not much of an issue with RTT but some of the experienced latency is quite significant. It showed nothing when I started an hour or so ago. It wasn't until I ran the latency test on testmy.net that it stimulated something. If you read what it says in the latency test, it makes sense to me that it is a better gage of web page latency (TCP; layer 4) than ICMP layer 3 messages like tracert and ping. It feels more like what I experience in usage too. TCP latency to multiple sites, 20 reps each. Since I don't just believe what I read, I ran tracert to many of those same sites in parallel so it could be captured in the wireshark trace I was running. The pcapng file has this kind of gorey detail on the comms through my ethernet port: Wireshark is a free network analysis tool (https://www.wireshark.org/) with awesome trace capability. Is anybody at Hughesnet interested in looking at my trace to see what the source of my frustratingly laggy performance is? I'd be glad to email it to you. Ultimately, the experience of the user is what HN delivers, not statistics, but stats help us troubleshoot techical issues. My router seems to say I don't have RTT issues (at least not bad enough to trigger the built in fault) and tracert shows quite good response (albeit optimistic layer 3 and below), SO... whatever my issue is seems to be in the TCP layer above it or in the gateway or the external site. Since I captured tracerts to those same sites and they too show <1000ms speeds unless they just bombed ("*"), this would say the connection to them is fast enough (by ICMP judgement). And yet TCP is laggy. All the data is in the PCAPNG file. I'm really not trying to be a jerk. I'm just an engineer looking for answers based on data.
... View more