Latency and Teamspeak II

[lighthope1]

Following up on this topic from https://community.myhughesnet.com/hughesnet/topics/latency-and-teamspeak?rfm=1&topic_submit=true

Been testing it over the last couple weeks. Didn't know the thread would be locked.

Anyway, you said that your engineers did some "tweeks" to my site.  I have noticed that, after I stop talking on Teamspeak, the latency drops back down faster.

However, I am still experiencing very high latency when I talk (or transmit data).

Last night I hit 5000 ms latency.

So there still is a problem.

[Chris11]

Hi lighthope,

Thanks for the update. As for the previous thread. I wanted to see if we could get an update, and potentially make more changes to your site. When I didn't hear from you I assumed it no longer was an issue. I'll update our engineers about your current status and get back to you. If anything changes feel free to let me know.

Thank you,
Chris

[El Dorado Netwo]

5,000 ms latency would = five seconds. Is that correct?

Best to check with TeamSpeak since it's their product. They may have experience with customers using their product over a satellite connection. Or be able to explain what you're seeing higher latency when you talk.

I don't think HughesNet will be able to resolve latency issues with a third-party product.
.

[lighthope1]

I've noticed this with any kind of constant streaming, not just TeamSpeak.

[Chris11]

Hi Lighthope,

Haven't forgot about you. Still waiting to hear back. I'll update you once I have more info. 

- Chris

[AvidSurvivalist]

When I try to play Multiplayer Minecraft my initial ping to the server is 800-900ms but when I join and play it goes all the way up to 2000ms!

[lighthope1]

Hit 4700 latency last night.  That was playing World of Warcraft.  I get that satellite is bad for twitch games, but 4700 ms?  Really?

[Chris11]

Hi Lighthope,

Just wanted to check in and see how your experience is so far. Have you noticed any improvement? At this time I have not received an update. I've been on top of our engineers with little luck so far. I'll keep pushing to get something more concrete. Hope to hear from you soon.

Thanks,
Chris

[lighthope1]

Still waiting for a response.

Hit 5100 latency last night with uploads stalled for up to 30 seconds or more.

It isn't just Teamspeak.  Seems to have something to do with streaming data, either voice or data or whatever. Maybe Hughesnet doesn't handle traffic snarls well.

Either way, problem needs to be solved.

[lighthope1]

Still waiting for something to be done about this.  No response for how long?  Three weeks?

I'd abandon HugesNet but there is no other choice in my area. Be glad you're a monopoly.

[Chris11]

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

[lighthope1]

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

[BirdDog]

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.

[lighthope1]

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.

[GabeU]

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. 

[lighthope1]

Trace a traceroute.

[lighthope1]

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.

[GabeU]

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.

[lighthope1]

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.

[Gwalk900]

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.

[lighthope1]

Just for giggles do a gateway test from the modems SSC

Huh?  You'll have to walk me through that.

then ping google.

That I did.  Here are two ping tests for Google.

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=870ms TTL=47
Reply from 8.8.8.8: bytes=32 time=924ms TTL=47
Reply from 8.8.8.8: bytes=32 time=999ms TTL=47
Reply from 8.8.8.8: bytes=32 time=1275ms TTL=47

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 870ms, Maximum = 1275ms, Average = 1017ms

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=619ms TTL=47
Reply from 8.8.8.8: bytes=32 time=976ms TTL=47
Reply from 8.8.8.8: bytes=32 time=2111ms TTL=47
Reply from 8.8.8.8: bytes=32 time=925ms TTL=47

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 619ms, Maximum = 2111ms, Average = 1157ms

Highest result was 2111 ms.