Free Allegiance Forums

Posted: **Sun Dec 20, 2009 6:50 pm**

I am not sure if I am posting this into the right forum, but about year and a half ago I always had 40-80 ms ping on GPZ and had no problem at all connecting to it (europe to europe).

On the other hand, nowadays, the packet loss and ping values are insane. I get 400ms on average and get dropped every 5-6 minutes. Its nearlly impossible to play.

I own a server in amsterdam (as I understood that it is the same location for GPZ). And I get 36ms average ping with 0% packet loss pinging it.

What is the problem with GPZ? Is there a way to fix it at all? Pinging GPZ AND my server at the same time gives perfect ping for my server, and packet loss to GPZ. (and same thing if done separately)

Posted: **Sun Dec 20, 2009 7:08 pm**

Please post traceroute results and your ping results.

For example:
ping server.german-borg.de
Antwort von 84.243.253.92: Bytes=32 Zeit=24ms TTL=124
Antwort von 84.243.253.92: Bytes=32 Zeit=23ms TTL=124
Antwort von 84.243.253.92: Bytes=32 Zeit=23ms TTL=124
Antwort von 84.243.253.92: Bytes=32 Zeit=23ms TTL=124

tracert server.german-borg.de
3 14 ms 12 ms 12 ms 145.254.15.93
4 23 ms 22 ms 23 ms 92.79.213.138
5 22 ms 22 ms 22 ms rtr1.ams-ix.AMS-tc2.grafix.nl [195.69.144.239]
6 23 ms 26 ms 23 ms server.german-borg.de [84.243.253.92]

Posted: **Sun Dec 20, 2009 8:38 pm**

I can confirm Troy's experience. Unfortunately I forgot to save traceroutes and as this behaviour is random and erratic (it's been like this since at least early october) can't provide any at the moment.
I am 100% sure though that I experienced major hiccups (packet loss and high ping) between:
"217.118.121.134" and "rtr-1.ams-tc2.grafix.nl [217.67.247.17]". Usually I see over 400ms at 217.67.247.17.

QUOTE *useless info here*

13 ae-2-2.ebr1.Amsterdam1.Level3.net [4.69.133.89]
14 ae-12-51.car2.Amsterdam1.Level3.net [4.69.139.131]
15 212.72.48.162
16 Gi6-0-0.ams-koo-access-1.interoute.net [212.23.41.134]
17 PO10-0.rtm-vla-access-1.interoute.net [212.23.41.205]
18 217.118.121.134 <---- problems here
19 rtr-1.ams-tc2.grafix.nl [217.67.247.17] <---- and here
20 server.german-borg.de [84.243.253.92][/quote]

Gonna update this as soon as I encounter lag again.

Posted: **Sun Dec 20, 2009 10:11 pm**

Yes, I am experiencing the same issue from time to time. I will post again when I have more data.

Posted: **Mon Dec 21, 2009 2:51 pm**

same here ,
I go fro 0 pk loss to 200 pk loss

Posted: **Tue Dec 29, 2009 4:22 pm**

Welcome to SolapWorld... oh wait!

Posted: **Tue Dec 29, 2009 8:31 pm**

===///===

11 45 ms 48 ms 47 ms core1-pos0-8-0-10.ealing.ukcore.bt.net [62.6.201
.65]
12 46 ms 47 ms 48 ms core1-pos5-0-0.telehouse.ukcore.bt.net [194.74.6
5.122]
13 47 ms 48 ms 47 ms 194.74.65.62
14 58 ms 55 ms 55 ms dc-server-14.adam.psi.com [195.81.245.14]
15 54 ms 51 ms 51 ms PO9-0.rtm-vla-access-1.interoute.net [212.23.41.
201]
16 66 ms 63 ms 63 ms 217.118.121.134
17 65 ms * * rtr-1.ams-tc2.grafix.nl [217.67.247.17]
18 67 ms 67 ms 67 ms server.german-borg.de [84.243.253.92]

===///====
11 50 ms 47 ms 47 ms core1-pos0-8-0-10.ealing.ukcore.bt.net [62.6.201
.65]
12 50 ms 47 ms 47 ms core1-pos5-0-0.telehouse.ukcore.bt.net [194.74.6
5.122]
13 46 ms 47 ms 47 ms 194.74.65.62
14 58 ms 55 ms 55 ms dc-server-14.adam.psi.com [195.81.245.14]
15 62 ms 59 ms 60 ms PO9-0.rtm-vla-access-1.interoute.net [212.23.41.
201]
16 63 ms 63 ms * 217.118.121.134
17 61 ms 63 ms 64 ms rtr-1.ams-tc2.grafix.nl [217.67.247.17]
18 70 ms * 69 ms server.german-borg.de [84.243.253.92]

That is the second half of tracert. The first one did not have a single problem.

Posted: **Wed Dec 30, 2009 9:45 am**

I informed pkk, he has the contact to the server hosters.

Posted: **Wed Dec 30, 2009 10:39 am**

Phhhewwww glad Ive never had to deal with this

GPZ

Posted: **Sun Jan 03, 2010 1:39 pm**

problem back again:

QUOTE Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

Tracing route to server.german-borg.de [84.243.253.92]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 192.168.0.1
2 13 ms 13 ms 12 ms kiel-ru1.neo.tpnet.pl [213.25.2.185]
3 13 ms 12 ms 15 ms kiel-r2.tpnet.pl [212.160.0.181]
4 16 ms 15 ms 15 ms war-r1.tpnet.pl [194.204.175.141]
5 37 ms 38 ms 38 ms war-b2-link.telia.net [213.248.89.85]
6 36 ms 36 ms 39 ms ffm-bb1-link.telia.net [80.91.251.215]
7 37 ms 36 ms 36 ms ffm-b10-link.telia.net [80.91.251.248]
8 38 ms 39 ms 38 ms xe-4-2-0.edge4.Frankfurt1.level3.net [4.68.63.121]
9 41 ms 38 ms 51 ms vlan79.csw2.Frankfurt1.Level3.net [4.68.23.126]
10 38 ms 39 ms 40 ms ae-92-92.ebr2.Frankfurt1.Level3.net [4.69.140.29]
11 42 ms 42 ms 43 ms ae-2-2.ebr1.Dusseldorf1.Level3.net [4.69.132.137]
12 41 ms 42 ms 42 ms ae-1-100.ebr2.Dusseldorf1.Level3.net [4.69.141.150]
13 51 ms 47 ms 47 ms ae-2-2.ebr1.Amsterdam1.Level3.net [4.69.133.89]
14 121 ms 166 ms 245 ms ae-12-51.car2.Amsterdam1.Level3.net [4.69.139.131]
15 49 ms 49 ms 48 ms 212.72.48.162
16 50 ms 50 ms 49 ms Gi6-0-0.ams-koo-access-1.interoute.net [212.23.41.134]
17 50 ms 50 ms 48 ms PO10-0.rtm-vla-access-1.interoute.net [212.23.41.205]
18 267 ms 272 ms 271 ms 217.118.121.134
19 269 ms 273 ms 269 ms rtr-1.ams-tc2.grafix.nl [217.67.247.1]
20 274 ms 272 ms 269 ms server.german-borg.de [84.243.253.92]

Trace complete.

Tracing route to server.german-borg.de [84.243.253.92]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 13 ms 13 ms 14 ms kiel-ru1.neo.tpnet.pl [213.25.2.185]
3 12 ms 13 ms 13 ms kiel-r2.tpnet.pl [212.160.0.181]
4 15 ms 15 ms 15 ms war-r1.tpnet.pl [194.204.175.141]
5 37 ms 39 ms 37 ms war-b2-link.telia.net [213.248.89.85]
6 37 ms 36 ms 36 ms ffm-bb1-link.telia.net [80.91.251.215]
7 36 ms 37 ms 36 ms ffm-b10-link.telia.net [80.91.251.120]
8 38 ms 38 ms 38 ms te-9-3-0.edge4.Frankfurt1.level3.net [4.68.111.101]
9 52 ms 38 ms 50 ms vlan79.csw2.Frankfurt1.Level3.net [4.68.23.126]
10 38 ms 38 ms 39 ms ae-72-72.ebr2.Frankfurt1.Level3.net [4.69.140.21]
11 42 ms 42 ms 42 ms ae-2-2.ebr1.Dusseldorf1.Level3.net [4.69.132.137]
12 42 ms 41 ms 43 ms ae-1-100.ebr2.Dusseldorf1.Level3.net [4.69.141.150]
13 47 ms 48 ms 47 ms ae-2-2.ebr1.Amsterdam1.Level3.net [4.69.133.89]
14 48 ms 47 ms 47 ms ae-12-51.car2.Amsterdam1.Level3.net [4.69.139.131]
15 48 ms 48 ms 108 ms 212.72.48.162
16 50 ms 50 ms 50 ms Gi6-0-0.ams-koo-access-1.interoute.net [212.23.41.134]
17 48 ms 49 ms 49 ms PO10-0.rtm-vla-access-1.interoute.net [212.23.41.205]
18 271 ms 269 ms 271 ms 217.118.121.134
19 270 ms 267 ms 272 ms rtr-1.ams-tc2.grafix.nl [217.67.247.17]
20 275 ms 275 ms 272 ms server.german-borg.de [84.243.253.92]

Trace complete.

Tracing route to server.german-borg.de [84.243.253.92]
over a maximum of 30 hops:

*CUT*

16 49 ms 50 ms 49 ms Gi6-0-0.ams-koo-access-1.interoute.net [212.23.41.134]
17 49 ms 49 ms 49 ms PO10-0.rtm-vla-access-1.interoute.net [212.23.41.205]
18 269 ms 273 ms 272 ms 217.118.121.134
19 277 ms 317 ms 271 ms rtr-1.ams-tc2.grafix.nl [217.67.247.17]
20 275 ms * 535 ms server.german-borg.de [84.243.253.92]

Trace complete.[/quote]

Randomly occuring since october. High ping + packet loss = unplayable. Should be around ~70ms

Free Allegiance Forums

GPZ pings and packet loss