Solved! Go to Solution.
Straight line distance from New York to Los Angeles is 2,448 miles.
A request and the return reply to/from computers in those cities is less than 5000 miles total.
That same request for a Hughes user is going to be 22,300 miles x 2 = 44,600 miles just for the Hughes portion of the signal travel.
The speed of light being a constant in both cases.
Why do all 15 hops in the tracert from my Hughes home to say Google.com all appear as 600ms or so (exception: my router and Hughes modem hops #1 and #2 are both below 1ms as expected)?
Only some of those very early hops after my modem are dish/satellite -- eventually we get to land and closer and closer to Google and the hops remain at 600 ms -- that means Hughes is throttling me at all those other hops (on uploads) to prevent overloading their weakest link hops. That's disingenuous. It's flat out throttling with Hughes and their service level agreements (SLAs) with other land-based Tier 1 ISPs in the route for the upload speeds. And this has nothing whatsoever to do with whether I signed up for 1mbs download or 2mbs download. They set the SLA to whatever they want to in either direction.Next I go to a Time Warner home and I do tracert in the reverse direction to those satellite IP addresses (hops 3 and 4 from my Hughes home) from a Time Warner home to those satellites I see 90ms which is more appropriate (6,100 miles) -- that is just further proof Hughes is throttling me in only one direction to prevent overloading their weakest link hops. That's disingenuous. They can throttle in either direction and they should not be throttling at all. Give me the 90 ms I see from my Time Warner home when I do my tracert to Google from my Hughes home. And don’t be mealy-mouthed with a lame technical response to an advanced network engineer. Instead, respond in writing “We never throttle our Hughes customers when they do uploads other than making sure they do not exceed the upload mbs they paid for” (by the way 1mbs is 0.125mbytes/sec and with a latency of 500ms my upload speed is going to be based on not on the 1mbs I paid or but on what data I can put into my TCP buffer to travel over that long throttled journey. My data can be uploaded a lot faster when I am not throttled and the 90ms tracert hop time from my Time Warner house to the satellite is proof that my buffers can travel 6 to 7 times faster if Hughes would allow it. That is, for the most part latency and transmission speed are unrelated (until there is congestion or intentional throttling). Transmission latency will be unchanged when you increase the bandwidth.