cancel
Showing results for 
Search instead for 
Did you mean: 

Latency and Teamspeak II

Alum

Re: Latency and Teamspeak II

Hi Lighthope,

Sorry for not getting back to you sooner. Most of my inquires on this have gone no where. However I'm going to take another approach and see what can be done. I'll get back to you with some info soon.

Thanks,
Chris
Junior

Re: Latency and Teamspeak II

I ran a traceroute, not to Teamspeak since I don't know what their IP is, but to World of Warcraft that since is a streaming service as well and suffers from terrible latency.

What I don't understand is why I am getting from 666ms to 2180ms from the same address.

Consider these results:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     1 ms    <1 ms    <1 ms  100.107.182.9
  3  1519 ms   777 ms  1276 ms  72.171.194.52
  4   874 ms  1537 ms   879 ms  72.171.196.58
  5  1123 ms     *     1314 ms  198.233.75.217
  6   666 ms  2180 ms  1767 ms  67.14.122.6
Assistant Professor

Re: Latency and Teamspeak II

Taking different routes? The 2180 high is still about 2.2 seconds. Satellite is slow when it comes to latency dependent things. Me being honest.
Junior

Re: Latency and Teamspeak II

Unless the different route is via the moon, there still is no reason why it would take more than 2 seconds.

My *guess* is that there is something happening at the NoC, either traffic shaping or something like that, which is causing the data to have to be resent, which is the cause of the high latency.
Distinguished Professor IV

Re: Latency and Teamspeak II

I just ran two ping tests on 67.14.122.6.

Min 616ms, Max 755ms, Average 659ms

Min 611ms, Max 715ms, Average 656ms

2180ms is pretty high, but I have no idea what would cause that. 


AMD FX-6100 | Samsung 250GB 840 EVO SSD | Western Digital Blue 500GB HDD | 16GB DDR3-1866 | EVGA Geforce GTX 550ti | Windows 10 Pro 64-bit
Junior

Re: Latency and Teamspeak II

Trace a traceroute.
Junior

Re: Latency and Teamspeak II

8322ms latency tonight.

I would be embarrassed to be giving that kind of service, but then that's just me.

One day, a competitor will come to our area, and I will remember this incident.
Distinguished Professor IV

Re: Latency and Teamspeak II

Tracing route to cer-edge-18.inet.qwest.net [67.14.122.6]
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.28.193
  3   559 ms   755 ms   639 ms  dpc6935182050.direcpc.com [69.35.182.50]
  4   596 ms   579 ms   612 ms  dpc6935180058.direcpc.com [69.35.180.58]
  5   568 ms   579 ms   729 ms  63.148.172.121
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9   938 ms   778 ms   579 ms  cer-edge-18.inet.qwest.net [67.14.122.6]

Trace complete.


AMD FX-6100 | Samsung 250GB 840 EVO SSD | Western Digital Blue 500GB HDD | 16GB DDR3-1866 | EVGA Geforce GTX 550ti | Windows 10 Pro 64-bit
Highlighted
Junior

Re: Latency and Teamspeak II

Here are my results.

Tracing route to 67.14.122.6 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.9
  3  1643 ms   817 ms  1032 ms  72.171.194.52
  4  1310 ms  1606 ms  1270 ms  72.171.196.58
  5  1409 ms   826 ms   616 ms  198.233.75.217
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8  1032 ms  2120 ms   738 ms  67.14.122.6

Trace complete.

Six times I got a timeout and 6 times response took over 1000ms with a max of 2120ms.

I think I'll try running this again during primetime and see if there is a difference.

Here are the ping times.


Pinging 67.14.122.6 with 32 bytes of data:
Reply from 67.14.122.6: bytes=32 time=645ms TTL=59
Reply from 67.14.122.6: bytes=32 time=986ms TTL=59
Reply from 67.14.122.6: bytes=32 time=1313ms TTL=59
Reply from 67.14.122.6: bytes=32 time=1354ms TTL=59

Ping statistics for 67.14.122.6:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 645ms, Maximum = 1354ms, Average = 1074ms

And a second try.

Pinging 67.14.122.6 with 32 bytes of data:
Reply from 67.14.122.6: bytes=32 time=652ms TTL=59
Reply from 67.14.122.6: bytes=32 time=1345ms TTL=59
Request timed out.
Reply from 67.14.122.6: bytes=32 time=683ms TTL=59

Ping statistics for 67.14.122.6:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 652ms, Maximum = 1345ms, Average = 893ms

Notice the timeout.
Honorary Alumnus

Re: Latency and Teamspeak II

Lighthope,
Just for giggles do a gateway test from the modems SSC. That will show the ping between your terminal and the gateway ... the "Hughes Loop" if you will., then ping google. We know they have good server response times.