HughesNet Community

Why does this work for latency?

cancel
Showing results for 
Search instead for 
Did you mean: 
lighthope1
Senior

Why does this work for latency?

On EchoStar 19, beam 5.

 

Had impossible latency spikes. Wildly swinging between 700ms and 44000ms. Latency swings are by the second.

 

Unable to determine source of latency. Could be HughesNet or could be CenturyLink. There is one hop that returns No Response From Host, but every once in a while will return an address.  I can't remember what it is, but it is a qwest domain.  When it does return, the ping time is something like 4000ms or so.

 

What is strange is that, if I run a program called WinMTR and put into it the destination IP, the latency disappears for the most part.  It still will rear its ugly head, but only on occassion.  Without running that, latency is almost always there.

 

For those who do not know, WinMTR will continuously run a traceroute or some such every second, testing the ping from each hop.

 

If I run it with an interval > 1 second, the latency returns.

 

Very strange, and I can't figure out why this works.

 

It is imperfect.  Latency still crawls in there, but at least it is something.

23 REPLIES 23
lighthope1
Senior

Have experienced a significant increase in latency the last couple weeks.

 

Terminal/Gateway Connectivity Test

 

IP GatewayJ2SEA005HNSIGW1305
Packet Loss0%
Average Delay792 ms
Minimum Delay590 ms
Maximum Delay1,424 ms

 

WinMTR

WinMTR statistics
Host%SentRecvBestAvrgWrstLast
192.168.42.10151315130050
host174330065208.direcway.com1136413515477374545614
host17433004213.direcway.com2136013445487324621622
tuk-edge-14.inet.qwest.net2136913535467223931626
sea-brdr-03.inet.qwest.net2135213345547314363584
63-235-42-186.dia.static.qwest.net3128612505497304668573
No response from host10030300000
4.7.26.1662135413365807564518650
ae1-br01-csla1.as57976.net2136813535837524677620
No response from host10030300000
et-0-0-2-br01-swlv10.as57976.net9930460463249624628
et-0-0-0-pe01-swlv10.as57976.net2135313375847594618645
137.221.105.22135313365887584622621

 

Notice the first hop, which should always be 0.  Somtimes as high as 5.

 

Ignoring the hops that don't return, see the spikes to almost 5000ms.  Those spikes are happening fairly regularly.  They aren't one-offs.

Yup. More analysis shows lots of slowdowns at the gateway.  5000ms tonight.

Why am I getting any latency at all from 192.168.42.1?