cancel
Showing results for 
Search instead for 
Did you mean: 

Latency and Teamspeak II

Associate Professor

Re: Latency and Teamspeak II

That's modem diagnostics... Something is certainly, terribly, wrong... 30% packet loss on one test with an average delay of 6k? dafuq? That's worse than Spaceway3, and lighthope is on Jupiter...?
Sophomore

Re: Latency and Teamspeak II

My problem doesn't seem to be of real interest to them.
Associate Professor

Re: Latency and Teamspeak II

It's of interest to me though...  You should have numbers closer to what's displayed below...  Though, I am on a totally different gateway than you, there's just no way a Jupiter user could be getting latency from modem diagnostics that's that horrible...  I mean, that's from the terminal, to the gateway it self isn't it?  What do your tracert results to the likes of google.com look like? Care to SS and share that?
Highlighted
Sophomore

Re: Latency and Teamspeak II

Here is a tracert to 8.8.8.8, which is supposedly a good address to use when testing google.com

Tracing route to 8.8.8.8 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     1 ms     1 ms    <1 ms  100.107.182.129
  3   795 ms  1370 ms  1320 ms  72.171.194.52
  4  1331 ms  2160 ms   612 ms  72.171.196.58
  5   890 ms  1073 ms  1066 ms  198.233.75.217
  6  2705 ms  2161 ms  1614 ms  67.14.8.86
  7  1138 ms  1058 ms  1095 ms  216.111.90.126
  8  1028 ms  1081 ms  1066 ms  209.85.244.1
  9  1103 ms  2488 ms  1078 ms  72.14.237.133
 10  1834 ms   635 ms  1080 ms  72.14.232.70
 11  1073 ms  1088 ms  1082 ms  72.14.234.81
 12     *        *        *     Request timed out.
 13   875 ms   798 ms   682 ms  8.8.8.8

For fairness, here is one to google.com, whatever that translated to.

Tracing route to google.com [172.217.4.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    <1 ms     1 ms     1 ms  100.107.182.129
  3   649 ms  1325 ms  1330 ms  72.171.194.52
  4  1370 ms  1326 ms  1324 ms  72.171.196.58
  5  1366 ms  2070 ms   716 ms  198.233.75.217
  6   611 ms   707 ms   768 ms  67.14.8.86
  7   862 ms   699 ms   733 ms  216.111.90.126
  8   733 ms   738 ms   705 ms  108.170.243.225
  9  1185 ms  1079 ms   762 ms  108.170.233.111
 10   839 ms  1070 ms   779 ms  172.217.4.110

Here is the gateway test when I ran this, so you can see what the current state is.  Obviously, more problems with the gateway would result in higher times for the tracert

Packet Loss: 0.00%
Average Delay: 919.00 ms
Minimum Delay: 610.00 ms
Maximum Delay: 1290.00 ms
IP Gateway: RAP43HNSIGW72C001Adv

This is an unusually good run.  Give it about 20 minutes and let's see if it changes.
Associate Professor

Re: Latency and Teamspeak II

To be honest, that run there looked rather normal.  Was there by chance anything being uploaded during the runs you did earlier?  I have noted in the past I get increases in latency when performing uploads on facebook, strangely, it only happens when I do so on facebook... lol
Sophomore

Re: Latency and Teamspeak II

During all tests, I make sure that nothing else is running.  There may have been something during the 30% packet loss run, which is why I retested it.
Sophomore

Re: Latency and Teamspeak II

Another test.
Tracing route to google.com [172.217.4.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     1 ms    <1 ms    <1 ms  100.107.182.129
  3  1853 ms   559 ms   584 ms  72.171.194.52
  4   609 ms   616 ms   639 ms  72.171.196.58
  5   794 ms  1000 ms   749 ms  198.233.75.217
  6   826 ms  1242 ms  1078 ms  67.14.8.86
  7  1289 ms  1590 ms  1249 ms  216.111.90.126
  8   802 ms  1313 ms  1064 ms  108.170.243.225
  9  1267 ms  1058 ms  1315 ms  108.170.233.111
 10  1019 ms  1288 ms  1431 ms  172.217.4.110

Packet Loss: 0.00%
Average Delay: 1381.00 ms
Minimum Delay: 890.00 ms
Maximum Delay: 1790.00 ms

Gateway latency is increasing, so the tracert is increasing as well.
Sophomore

Re: Latency and Teamspeak II

This next test seems to be all over the place.

Tracing route to google.com [172.217.4.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     1 ms    <1 ms     1 ms  100.107.182.129
  3   726 ms  1070 ms  1081 ms  72.171.194.52
  4     *     2871 ms   591 ms  72.171.196.58
  5   643 ms   635 ms   724 ms  198.233.75.217
  6   606 ms   921 ms     *     67.14.8.86
  7  2445 ms   676 ms   722 ms  216.111.90.126
  8   593 ms   582 ms   586 ms  108.170.243.225
  9   668 ms     *     2192 ms  108.170.233.111
 10   642 ms   629 ms   614 ms  172.217.4.110

Trace complete.

Notice the timeouts coupled with other low pings.

Here is the associated gateway test

Packet Loss: 0.00%
Average Delay: 1335.00 ms
Minimum Delay: 910.00 ms
Maximum Delay: 2030.00 ms
IP Gateway: RAP43HNSIGW72C001Adv

Nothing else was running.

Half the internet is unusable for me with these problems.  I think my rates should be cut in half until it is fixed.
Sophomore

Re: Latency and Teamspeak II

This next test seems to be all over the place.

Tracing route to google.com [172.217.4.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     1 ms    <1 ms     1 ms  100.107.182.129
  3   726 ms  1070 ms  1081 ms  72.171.194.52
  4     *     2871 ms   591 ms  72.171.196.58
  5   643 ms   635 ms   724 ms  198.233.75.217
  6   606 ms   921 ms     *     67.14.8.86
  7  2445 ms   676 ms   722 ms  216.111.90.126
  8   593 ms   582 ms   586 ms  108.170.243.225
  9   668 ms     *     2192 ms  108.170.233.111
 10   642 ms   629 ms   614 ms  172.217.4.110

Trace complete.

Notice the timeouts coupled with other low pings.

Here is the associated gateway test

Packet Loss: 0.00%
Average Delay: 1335.00 ms
Minimum Delay: 910.00 ms
Maximum Delay: 2030.00 ms
IP Gateway: RAP43HNSIGW72C001Adv

Nothing else was running.

Half the internet is unusable for me with these problems.  I think my rates should be cut in half until it is fixed.
Associate Professor

Re: Latency and Teamspeak II

TBH, those numbers almost look normal for satellite, 1300ms avg is semi-normal depending on infrastructure load (you may be on a heavily congested beam).  You are certainly getting lower latency in tracerts to outside of the infrastructure most of the time in those rounds...  I suspect the 6k lag spike could have been some form of issue at the gateway, it happens.