"Sounds like you're saying that if my latency is high, the odds of it being a problem with Hughes is very tiny?"
"Are there any other variables? I know there are variables on my end, I mean otherwise."
Yes. As the website indicates, your mileage may vary depending on
and I get it, 600-700 is normal latency for sat and there's no way around that. I'm just looking to diagnose or understand why I sometimes experience slow or erratic performance, and yet my mbps download speeds are the same as when the performance is normal. So I wanted to figure out how to check latency the next time it happens, to see if that explains it.
No way around the laws of physics, so the latency can't be changed. When you experience slowdowns they're likely related to the other causes on the list, all of them things you have basically no control over.
What do you do when you experience slowdowns? Do you ever try to reboot your modem? That's a strategy that sometimes helps.
How to read:
The number at the left is the hop number.
Hop 1 is 192.168.42.1, your modem.
Hops 2 and 3 are the HughesNet path to the gateway (thought there should be another one somewhere).
Hop 4 is Qwest (now owned by CenturyLink), your gateway provider.
Use 525mS as an easy to remember guide, because the radio path takes that much time to go to from you to the satellite, down to the groundstation, and then the return trip back to you.
These are all showing about 1-1.5 seconds more than that, which sounds to me like either a network compatibility problem or simple network congestion (congestion being too many users, causing a processing/routing backlog). CenturyLink is well-known for sporadic 1-minute gaps in service, not 1 second, so it's not the provider.
It could feasibly be peak time congestion, but it'd have to be pretty congested and I'd have to see what one of these looks like during a non-congested period. If it's that high (readings of 1500-2000mS) during non-peak time, then it's not congestion, it's a network compatibility issue.
But again, I don't know what tracepath is actually doing. I'm working from the assumption that it's something similar to traceroute and I might be wrong.
MarkjFine, So one doesn't add up the ms values on each hop to determine one's total round-trip latency? But rather, the ms value at far right on each of those lines (i.e. 1471.185ms on the third hop 3 line) reperesents a total round trip latency?
When I do a ping command, I get ms numbers on the right of each line in the 600-900 range, which seems more expected. Does that indicate that those 1-1.5 sec. values on each line after a tracepath command are probably not accurate? Or is the ping command not accurate?
When you talk of the possibility of a network compatibility problem, what networks are you talking about? I'm a guy in central florida using my Hughes service to ping amazon.com, why would any of the networks used to execute that very common route for me have incompatibility issues?
Each one on the right is basically a ping from you to that hop's location. It does three to each one so you can get an idea of the variance. In a traceroute, all three are on one line, but these have each on a separate line.
As I said, I don't exactly know what your tracepath is doing. If you can ping to any of those hop locations manually and get lower values, then there's something wrong with tracepath.
Lots of things can cause incompatibilities - packet size, MTU, what the network expects to see versus what you're generating... and when I say 'the network' I mean your local LAN (basically your Chromebook, since that's the only thing on it) versus what HugheNet's WAN expects (everything between the modem and the groundstation), versus what the groundstation's provider (Qwest) and the overall internet expects.
There are basically three different segments I'm grouping into the greater network here - which is why I keep saying knowing what's going on at each node in that chain is important. But if tracepath is broken and you have no access to a working traceroute, then it's just going to give you bad data.
MarkjFine, you said, "If you can ping to any of those hop locations manually," don't know for sure if this is what you mean, but I tried this:
My second hop was host977219357.direpc.com. I tried a ping command to that, then I tried 977219357direpc.com, and finally I tried just direpc.com. All three returned with 'name or service not known.' I also tried a tracepath command with all three of those, same result.
I guess my first problem is nobody in the conversation knows for certain how to do a traceroute with a chromebook. What I found via googling is that tracepath is how you do a traceroute on a chromebook, but I have no expertise to know if that's right, and applies to what we are using it for.
"I guess my first problem is nobody in the conversation knows for certain how to do a traceroute with a chromebook. "
You were told how to run a tracepath on a Chromebook. So yes, we know how to do it; but it's not our fault if the tracepath command may be buggy. That's for Google to fix.
Is there any possibility of borrowing a Windows or Mac based device from someone to run a traceroute? Something seems "off" with those tracepath results, or at least in comparison to your ping tests.
Just for info, my traceroutes and pings are almost always comparable.
It may require superuser access on a Chromebook to run traceroute.
Did you try typing "su" then hitting return before running traceroute, like I said way back?