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.
Have experienced a significant increase in latency the last couple weeks.
Terminal/Gateway Connectivity Test
IP Gateway | J2SEA005HNSIGW1305 |
Packet Loss | 0% |
Average Delay | 792 ms |
Minimum Delay | 590 ms |
Maximum Delay | 1,424 ms |
WinMTR
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
192.168.42.1 | 0 | 1513 | 1513 | 0 | 0 | 5 | 0 |
host174330065208.direcway.com | 1 | 1364 | 1351 | 547 | 737 | 4545 | 614 |
host17433004213.direcway.com | 2 | 1360 | 1344 | 548 | 732 | 4621 | 622 |
tuk-edge-14.inet.qwest.net | 2 | 1369 | 1353 | 546 | 722 | 3931 | 626 |
sea-brdr-03.inet.qwest.net | 2 | 1352 | 1334 | 554 | 731 | 4363 | 584 |
63-235-42-186.dia.static.qwest.net | 3 | 1286 | 1250 | 549 | 730 | 4668 | 573 |
No response from host | 100 | 303 | 0 | 0 | 0 | 0 | 0 |
4.7.26.166 | 2 | 1354 | 1336 | 580 | 756 | 4518 | 650 |
ae1-br01-csla1.as57976.net | 2 | 1368 | 1353 | 583 | 752 | 4677 | 620 |
No response from host | 100 | 303 | 0 | 0 | 0 | 0 | 0 |
et-0-0-2-br01-swlv10.as57976.net | 99 | 304 | 6 | 0 | 4632 | 4962 | 4628 |
et-0-0-0-pe01-swlv10.as57976.net | 2 | 1353 | 1337 | 584 | 759 | 4618 | 645 |
137.221.105.2 | 2 | 1353 | 1336 | 588 | 758 | 4622 | 621 |
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?