You stated that it is roughly 186,282 mi/s. I must say you are right on with it being exactly 186282.397051 mi/s.
I'm a radio engineer by trade. These are basics.
Would you have any thoughts on my latency problem.
As I mentioned in the same post and previously, I can't determine where the latency problem exists without seeing a traceroute to whatever site you're trying to get to. It could be inside the HughesNet gateway, it could be at the gateway's provider (more than likely), it could be anywhere in the route between the provider and the site you're trying to get to.
Nobody can do this for you, and it's as simple as opening up a command window in Windows and typing something like:
You would have to do it from a desktop because I'm pretty sure your phone doesn't have a command/terminal window.
Secondly, I'm assuming you have a Windows desktop.
Thirdly, if it's a Mac, the command is 'traceroute' instead of 'tracert'.
Lastly, would prefer a screenshot, but not because of potential typing errors. The text spacing in the window will make it hard to read.
This is not telephone support -- it's a higher tier, and yes, for us to see what you see we need a screenshot.
Lastly, a screenshot? I can type the information more quickly and efficiently. Telephone support did not require this of me during the many months of dealing with my dish alignment.
I'm going to request this thread to end. I don't know what you mean by text spacing and being hard to read. What we are doing here is text.
Pasting copied traceroute output from the Command prompt doesn't come across well. It loses its layout, making it difficult to read. This is why Mark recommended a picture.
If you don't have an ethernet cable do it via WiFi, but be aware that, if your WiFi connection is weak, it can cause the results to be highly inaccurate.
And no one is saying you're lying. We're saying your belief is very likely mistaken. BIG difference.
You're making this more difficult than it needs to be.