Networking → Loss problem, interpretation of pathping

on some german servers, i get loss in-game on a computer game i play...

Here i pathping'ed one of those servers. Could you tell me what the problem is?

C:\Documents and Settings\Menace>pathping 193.192.58.150

Rute spores til 193.192.58.150 over et maksimum af 30 hop

0 dennis-90639a1f.opasia.dk [80.164.3.104]
1 lo1.abnxx10.ip.tele.dk [80.166.136.29]
2 ge1-0-40.1000M.abnxg4.ip.tele.dk [83.88.9.1]
3 pos6-0.2488M.abnxg1.ip.tele.dk [83.88.15.65]
4 pos0-0-3-1.2488M.kd4nqh1.ip.tele.dk [83.88.12.89]
5 pos0-1-3-0.9953M.alb2nqh1.ip.tele.dk [83.88.27.25]
6 te3-2.10G.alb2nxc7.ip.tele.dk [83.88.23.58]
7 cph10.ip.tiscali.net [195.215.109.102]
8 xe-0-0-0.fra20.ip.tiscali.net [89.149.186.65]
9 80.95.144.192
10 193.192.58.150

Beregner statistik i 250 sekunder...
Kilde tilher Dette node/Dette link
Hop RTT Tabt/Sendt = Pct Tabt/Sendt = Pct Adresse
0 dennis-90639a1f.opasia.dk [80.164.
3.104]
0/ 100 = 0% |
1 33ms 0/ 100 = 0% 0/ 100 = 0% lo1.abnxx10.ip.tele.dk [80.166.136
.29]
0/ 100 = 0% |
2 15ms 0/ 100 = 0% 0/ 100 = 0% ge1-0-40.1000M.abnxg4.ip.tele.dk [
83.88.9.1]
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% pos6-0.2488M.abnxg1.ip.tele.dk [83
.88.15.65]
0/ 100 = 0% |
4 19ms 0/ 100 = 0% 0/ 100 = 0% pos0-0-3-1.2488M.kd4nqh1.ip.tele.d
k [83.88.12.89]
0/ 100 = 0% |
5 22ms 0/ 100 = 0% 0/ 100 = 0% pos0-1-3-0.9953M.alb2nqh1.ip.tele.
dk [83.88.27.25]
0/ 100 = 0% |
6 22ms 0/ 100 = 0% 0/ 100 = 0% te3-2.10G.alb2nxc7.ip.tele.dk [83.
88.23.58]
0/ 100 = 0% |
7 22ms 0/ 100 = 0% 0/ 100 = 0% cph10.ip.tiscali.net [195.215.109.
102]
3/ 100 = 3% |
8 --- 100/ 100 =100% 97/ 100 = 97% xe-0-0-0.fra20.ip.tiscali.net [89.
149.186.65]
0/ 100 = 0% |
9 33ms 3/ 100 = 3% 0/ 100 = 0% 80.95.144.192
3/ 100 = 3% |
10 33ms 6/ 100 = 6% 0/ 100 = 0% 193.192.58.150

The 3rd to last hop appears to not really be responding to ICMP at all. The second to last and last hop are both appearing to have some packet loss. Whether that is related to the 3rd to last hop or not is anyone's guess. But it is definitely suspect.

What should I do? call my isp and tell them to fix it?

Its not your ISP's fault they cant do anything, the only people that can call to get it fixed it are the ones paying them for transit (the server admin of the game server).

but its not the destination hop that is the major problem aparently, but the third to last one? what control does the game server have over that.

Sorry for my lack of knowledge

That is true, then you'll just have to wait till it gets noticed and fixed, most likely they know about it.

p.s: I just pinged 89.149.186.65 directly and im getting 0% loss.. same with 80.95.144.192 and 193.192.58.150

I get that too when i don't use pathping.....0 loss, but with pathping i get this result everytime.

if its on my end i'm only happy, because that should mean that there would be a possible solution?

goto the CMD window and run (without "") "ping -n 500 193.192.58.150" and post the summery.

Ping-statistics for 193.192.58.150:
Packages: Send = 500, arrived = 487, lost = 13 (2% tab),
Beregnet tid for rundtur i millisekunder:
Minimum = 29ms, Maksimum = 44ms, avarage = 30ms

But here it still goes through the weird 100/100 tiscali hop right? or is this directly?

I just did the same with the hop i'm having issues with.

and I got 0 loss. Isnt that very strange considering pingpath still shows the 100/100 result?

guess people know nothing o.O

or simply don't care.

Ping losses in the middle mean absolutely nothing if not reflected at the destination.

but all servers that go through that hop in the middle ends up giving me loss...

So there must be a connection.

The reason that you will see latency and packet loss in a traceroute but not when pinging the destination directly is because they use different mechanisms. When you do a traceroute, it is simply sending ICMP response packets to the final destination IP with incrementing TTL values. When the packet arrives to a hop with a TTL of 1, that router needs to decrement the TTL to 0 and, since it will not forward it, it replies back to the source IP with an "ICMP TTL exceeeded" packet. These exceeded packets are give a very low priority on some routers, ezpecially Cisco. If you try sending a ping directly to that IP address, it now will send back a different type of packet, an "ICMP reply". This type of packet does not suffer the same deprioritization and you will get more accurate results.

In the TC's first post, the results show that the game server is at fault. The 3rd-to-last hop results should be discarded, or send pings directly to it for accurate results.