TS³ dropping and bad voice - for German telecom user

[DaFi]

Posting my routing. Flummi said its for german telecom user. Its working again now....


C:\>tracert ts.global-conflict.org

Routenverfolgung zu ts.global-conflict.org [66.150.121.103] über maximal 30 Abs
hnitte:

1 2 ms 1 ms <1 ms speedport.ip [192.168.2.1]
2 15 ms 14 ms 15 ms 87.186.224.54
3 18 ms 18 ms 17 ms 87.186.255.142
4 17 ms 16 ms 17 ms d-ed1-i.D.DE.NET.DTAG.DE [62.154.15.222]
5 17 ms 17 ms 17 ms 194.25.211.130
6 109 ms 109 ms 110 ms xe-4-3-0.nyc32.ip4.tinet.net [89.149.184.221]
7 * * 108 ms internap-gw.ip4.tinet.net [216.221.159.206]
8 * * * Zeitüberschreitung der Anforderung.
9 * 106 ms 107 ms ts.global-conflict.org [66.150.121.103]

Ablaufverfolgung beendet.

[KoffeinFlummi]

That is weird actually.

Since in the past the internap server was the one breaking up for me, I assumed that people with the same ISP would take the same route. But you seem to have the same issue, but on a different route, at the same time...

I'll post your route here nicely formatted for comparison :

DaFi

Code: Select all

  1     2 ms     1 ms    <1 ms  speedport.ip [192.168.2.1]
  2    15 ms    14 ms    15 ms  87.186.224.54
  3    18 ms    18 ms    17 ms  87.186.255.142
  4    17 ms    16 ms    17 ms  d-ed1-i.D.DE.NET.DTAG.DE [62.154.15.222]
  5    17 ms    17 ms    17 ms  194.25.211.130
  6   109 ms   109 ms   110 ms  xe-4-3-0.nyc32.ip4.tinet.net [89.149.184.221]   
  7     *        *      108 ms  internap-gw.ip4.tinet.net [216.221.159.206]
  8     *        *        *     Zeitüberschreitung der Anforderung.
  9     *      106 ms   107 ms  ts.global-conflict.org [66.150.121.103]

Me (at the moment without problems)

Code: Select all

  1     7 ms     3 ms     4 ms  192.168.178.254
  2    18 ms    11 ms    11 ms  217.0.118.83
  3    11 ms    16 ms    12 ms  87.186.243.102
  4    19 ms    19 ms    21 ms  f-ed6-i.F.DE.NET.DTAG.DE [62.156.131.254]
  5    19 ms    29 ms    17 ms  ffm-b12-link.telia.net [213.248.79.201]
  6    18 ms    17 ms    16 ms  ffm-bb1-link.telia.net [213.155.135.8]
  7   180 ms   155 ms   159 ms  nyk-bb1-link.telia.net [213.155.135.61]
  8   112 ms   112 ms   113 ms  nyk-b6-link.telia.net [213.155.130.241]
  9   112 ms   113 ms   114 ms  internap-ic-150761-nyk-b5.c.telia.net [213.248.81.150]
 10   111 ms   112 ms   112 ms  border1.pc1-bbnet1.ext1.nym.pnap.net [216.52.95.14]
 11   112 ms   110 ms   110 ms  v-66-150-121-103.unman-vds.internap-nyc.nfoservers.com [66.150.121.103]

[DaFi]

My working route.
Still goes over Croatia->Moldova->Netherlands->NY (Or something like that). And 100+ms for the US connection seems normal too.
So there is a Problem at my 8th routing point, I guess?!

Code: Select all

  1     1 ms     1 ms     1 ms  speedport.ip [192.168.2.1]
  2    14 ms    15 ms    14 ms  87.186.224.54
  3    19 ms    15 ms    18 ms  87.186.255.142
  4    17 ms    18 ms    17 ms  d-ed1-i.D.DE.NET.DTAG.DE [62.154.15.194]
  5    17 ms    17 ms    17 ms  194.25.211.130
  6   103 ms   103 ms   103 ms  xe-4-3-0.nyc32.ip4.tinet.net [89.149.184.221]
  7   104 ms   104 ms   104 ms  internap-gw.ip4.tinet.net [216.221.159.206]
  8   104 ms   103 ms   103 ms  border1.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.78]
  9   104 ms   103 ms   104 ms  ts.global-conflict.org [66.150.121.103]

[.Sup]

its Hitman's fault

[KoffeinFlummi]

its Hitman's fault

agreed.

[Necromancer]

Ping is the time it takes the packet to go to the server and back.
the more distance it has to travel, the higher the ping. this is normal. however theres normal time, if the packet goes and returns without a problem, and higher ping, if the packet get stuck in an overloaded server, the server also tends to drop a lot of packets due to the overload, which is awful for the end user (you loose a lot of information/packets, and those you get are "outdated")

euro's should have less then 100 to East coast. where is the TS server located? west coast?

[DaFi]

Dont know exactly where the TS Server is. I get New Jersey or Ashburn(Near Washington), when I look for the TS IP.
I dont think 104ms-110ms are bad for this connections.

Had this bug twice now. The first time I restarted my Inet and it was fine. This time it just worked again after 30min or so.