Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 2 of 2
  1. #1
    Join Date
    August 2014
    Posts
    2

    IPV6 Clients have higher latency

    I personally don't have an IPv6 for some reason TWC seems to just hate me, but most of my clients do have IPv6's and clients that usually have 16 ping. I asked them to try to connect manually through just the regular IPv4 and the ping for them went back to around 16 rather than 64. 64 IS bearable, but i just wanted to make sure teamspeak has a note of this because it can vary for other people that 16 to 64 could turn into 100 to maybe something even higher.

  2. #2
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,368
    This is not related to TeamSpeak at all. It depends on the routing/peering your ISP purchased from the carriers.

    Just use tracert or ping and you will see the routing and pings will be different for servers that have a higher ping (or high packet loss) in TeamSpeak only for IPv6:
    Code:
    C:\Users\Redeemer>tracert -4 ip.yat.qa
    
    Routenverfolgung zu ip.yat.qa [46.182.18.215] über maximal 30 Abschnitte:
    
      1    <1 ms    <1 ms    <1 ms  fritz.box [192.168.178.1]
      2    19 ms    19 ms    19 ms  217.0.117.153
      3    23 ms    20 ms    23 ms  87.186.195.178
      4    24 ms    24 ms    24 ms  217.239.48.198
      5    24 ms    24 ms    24 ms  ae15-0.fra10.core-backbone.com [87.190.233.2]
      6    24 ms    25 ms    24 ms  core-backbone.keyweb.de [81.95.2.110]
      7     *        *        *     Zeitüberschreitung der Anforderung.
      8    34 ms    33 ms    33 ms  core.nbiserv.de [185.58.159.2]
      9    33 ms    33 ms    34 ms  252-19-182-46.NbIServ.com [46.182.19.252]
     10    34 ms    34 ms    33 ms  nusskadse.redeemer.biz [46.182.18.215]
    
    Ablaufverfolgung beendet.
    
    C:\Users\Redeemer>tracert -6 ip.yat.qa
    
    Routenverfolgung zu ip.yat.qa [2a02:2970:1002::9eea] über maximal 30 Abschnitte:
    
    
      1    <1 ms    <1 ms    <1 ms  fritz.box [2003:56:cf1a:8400:3a10:d5ff:fe28:5657
    ]
      2    20 ms    19 ms    20 ms  2003:0:1503:200::1
      3    22 ms    22 ms    24 ms  2003:0:1501:310::2
      4    24 ms    24 ms    24 ms  2003:0:130a:c000::1
      5    25 ms    24 ms    25 ms  2003:0:130a:c01a::2
      6     *        *        *     Zeitüberschreitung der Anforderung.
      7    37 ms   241 ms   241 ms  2001:920:0:1::77
      8    32 ms    32 ms    31 ms  tnk-jen-001-loc.netz.netkom-line.net [2a02:2250:
    100::1]
      9    32 ms    31 ms    31 ms  tnk-jen-001-ipt.netz.netkom-line.net [2a02:2250:
    100::2]
     10    34 ms    35 ms    34 ms  2a02:2250:100:3::2
     11    44 ms    36 ms    34 ms  2a02:2977::2
     12     *        *        *     Zeitüberschreitung der Anforderung.
     13    41 ms    43 ms    38 ms  nusskadse.redeemer.biz [2a02:2970:1002::9eea]
    
    Ablaufverfolgung beendet.
    Is this not a general issue. On my main testing server, routing and pings match for IPv6 and IPv4.
    Code:
    C:\Users\Redeemer>tracert -4 yat.qa
    
    Routenverfolgung zu yat.qa [31.172.95.122] über maximal 30 Abschnitte:
    
      1    <1 ms    <1 ms    <1 ms  fritz.box [192.168.178.1]
      2    19 ms    19 ms    19 ms  217.0.117.153
      3    21 ms    22 ms    23 ms  87.186.195.178
      4    24 ms    24 ms    24 ms  217.239.44.22
      5    24 ms    24 ms    24 ms  87.190.233.116
      6    26 ms    29 ms    31 ms  cr03.fra1.de.first-colo.net [212.224.102.133]
      7    24 ms    24 ms    23 ms  v20576.php-friends.de [31.172.95.122]
    
    Ablaufverfolgung beendet.
    
    C:\Users\Redeemer>tracert -6 yat.qa
    
    Routenverfolgung zu yat.qa [2a01:7e0:0:417:59:1337:cad:5e] über maximal 30 Absch
    nitte:
    
      1    <1 ms    <1 ms    <1 ms  fritz.box [2003:56:cf1a:8400:3a10:d5ff:fe28:5657
    ]
      2    20 ms    19 ms    19 ms  2003:0:1503:200::1
      3    21 ms    23 ms    23 ms  2003:0:1503:210::2
      4    24 ms    24 ms    25 ms  2003:0:130c:8000::1
      5    24 ms    24 ms    26 ms  2003:0:130c:8010::3
      6    24 ms    24 ms    24 ms  2a01:7e0:0:417:59:1337:cad:5e
    
    Ablaufverfolgung beendet.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Is it normal for DPC latency to be higher when running teamspeak?
    By lukeman3000 in forum General Questions
    Replies: 1
    Last Post: March 24th, 2016, 12:48 PM
  2. DPC latency (TS3 3.0.16)
    By KayZze in forum General Questions
    Replies: 1
    Last Post: October 24th, 2014, 07:45 AM
  3. Replies: 4
    Last Post: December 21st, 2013, 08:33 PM
  4. Higher Latency
    By Gamestar in forum Client Support
    Replies: 6
    Last Post: December 28th, 2009, 10:42 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •