Server lag

[sweeper]

Hello

I'm wondering if some of you fine gentlemen can help me out a bit. The north american servers are slightly laggy at times and I am wondering if you guys can help me diagnose it. To do this we are going to run a couple simple commands from our command prompt.

The first one is a trace route. We do this by opening the command prompt, Click start>Programs>Accessories>Command prompt. Or you can just click Start>click on the search bar>type cmd.


This is your Command Prompt, it is your best friend.

Now to run the route. This depends on which server you wish to play on. Type in only the stuff in the quotes:
Global-Conflict.org NY - "tracert 74.91.116.142"
Global-conflict.org. Chicago - "tracert 199.21.112.122"

Give it a moment to work, you should come out with something like this. (hopefully with lower pings)

A trace route done.

right click on the CMD box and select "select all" then copy that and paste it here for us to take a look at.

Want to do more to help?

In that same command window type in "ping -t
Global-Conflict.org NY - "ping -t 74.91.116.142"
Global-conflict.org. Chicago - "ping -t 199.21.112.122"

Now leave this running while you are playing. If you experiences lag, rubber-banding or anything else that you might think is lag look at the command window and try to find if there was a spike under "time" If there was post how much for how long or just post that part of the log.

Thanks!

[Ash2Dust]

Sorta same, more in depth.

viewtopic.php?f=309&t=17291&start=15#p186558

[pkrocky]

Microsoft Windows [versie 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle rechten voorbehouden.

H:\Windows\system32>tracert 74.91.116.142

Traceren van de route naar c-74-91-116-142.internap-nyc.nfoservers.com [74.91.11
6.142]
via maximaal 30 hops:

1 7 ms 6 ms 5 ms pascalkemink-PC [0.0.0.0]
2 6 ms 7 ms 8 ms p60221.net.upc.nl [212.142.60.221]
3 11 ms 11 ms 11 ms nl-ams05a-rd2-ae-40-2367.aorta.net [84.116.244.6
9]
4 11 ms 12 ms 12 ms nl-ams09b-ri1-xe-9-2-0.aorta.net [84.116.130.14]

5 16 ms 17 ms 18 ms 213-46-161-146.aorta.net [213.46.161.146]
6 88 ms 89 ms 93 ms xe-11-0-0.nyc30.ip4.tinet.net [213.200.80.58]
7 102 ms 86 ms 87 ms internap-gw.ip4.tinet.net [77.67.70.98]
8 86 ms 87 ms 86 ms border1.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.
78]
9 88 ms 87 ms 87 ms c-74-91-116-142.internap-nyc.nfoservers.com [74.
91.116.142]

De trace is voltooid.

H:\Windows\system32>

[BYN124]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

tracert 74.91.116.142

Tracing route to c-74-91-116-142.internap-nyc.nfoservers.com [74.91.116.142]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 <1 ms <1 ms <1 ms 145.97.222.1
3 31 ms 1 ms <1 ms gw009.net.uu.nl [131.211.0.9]
4 1 ms 1 ms 1 ms GE0-3-0.1115.JNR01.Asd001A.surf.net [145.145.16.
97]
5 16 ms 1 ms 1 ms AE1.500.JNR02.Asd002A.surf.net [145.145.80.69]
6 1 ms 1 ms 1 ms xe-5-3-0.ams10.ip4.tinet.net [77.67.72.109]
7 79 ms 79 ms 79 ms xe-10-1-0.nyc30.ip4.tinet.net [89.149.184.129]
8 83 ms 82 ms 82 ms internap-gw.ip4.tinet.net [77.67.70.98]
9 83 ms 83 ms 83 ms border1.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.
78]
10 82 ms 82 ms 82 ms c-74-91-116-142.internap-nyc.nfoservers.com [74.
91.116.142]

Trace complete.

----------------------------------------------------------------------------
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

tracert 199.21.112.122

Tracing route to chge308.multiplay.co.uk [199.21.112.122]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 <1 ms <1 ms <1 ms 145.97.222.1
3 <1 ms <1 ms <1 ms gw009.net.uu.nl [131.211.0.9]
4 1 ms 1 ms 1 ms GE0-3-0.1115.JNR01.Asd001A.surf.net [145.145.16.
97]
5 1 ms 1 ms 1 ms AE0.500.JNR02.Asd001A.surf.net [145.145.80.77]
6 1 ms 1 ms 1 ms nl-sar.nordu.net [109.105.98.33]
7 76 ms 76 ms 76 ms us-man.nordu.net [109.105.97.45]
8 * * * Request timed out.
9 76 ms 77 ms 76 ms ae1-70g.cr1.ewr1.us.nlayer.net [69.31.95.173]
10 103 ms 102 ms 103 ms xe-5-0-0.cr1.ord1.us.nlayer.net [69.22.142.74]
11 103 ms 103 ms 107 ms ae0-40g.cr2.ord1.us.nlayer.net [69.31.111.154]
12 96 ms 96 ms 110 ms po6.ar2.ord1.us.scnet.net [69.31.111.6]
13 97 ms 96 ms 96 ms 62.po2.ar2.ord6.us.scnet.net [75.102.3.230]
14 97 ms 97 ms 97 ms as36352.po4.ar2.ord6.us.scnet.net [204.93.192.19
0]
15 104 ms 104 ms 104 ms fr171.aggr.chi.colocrossing.com [206.217.133.150
]
16 104 ms 104 ms 104 ms chge308.multiplay.co.uk [199.21.112.122]

Trace complete.

------------------------------------------------

Hop 8 seems to time-out all the time(did this when the servers were just up too. Any ideas why this is happening?

[Shrapnel]

NY:
Tracing route to c-74-91-116-142.internap-nyc.nfoservers.com [74.91.116.142]
over a maximum of 30 hops:

1 32 ms <1 ms <1 ms api.home [192.168.1.254]
2 14 ms 14 ms 14 ms 217.32.141.128
3 125 ms 15 ms 14 ms 217.32.141.174
4 17 ms 17 ms 16 ms 213.120.161.122
5 17 ms 17 ms 17 ms 217.41.222.50
6 17 ms 18 ms 18 ms 217.41.222.182
7 17 ms 17 ms 17 ms acc2-10GigE-0-7-0-6.bm.21cn-ipp.bt.net [109.159.
248.214]
8 22 ms 23 ms 23 ms core1-te0-15-0-7.ilford.ukcore.bt.net [109.159.2
48.146]
9 21 ms 21 ms 20 ms core1-pos9-0.telehouse.ukcore.bt.net [62.6.201.1
18]
10 83 ms 203 ms 203 ms t2as1-tge4-4.uk-lon1.eu.bt.net [166.49.211.145]

11 23 ms 22 ms 23 ms 166-49-211-38.eu.bt.net [166.49.211.38]
12 94 ms 94 ms 93 ms xe-10-1-0.nyc30.ip4.tinet.net [89.149.184.129]
13 90 ms 90 ms 89 ms internap-gw.ip4.tinet.net [77.67.70.98]
14 91 ms 90 ms 106 ms border1.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.
78]
15 91 ms 90 ms 91 ms c-74-91-116-142.internap-nyc.nfoservers.com [74.
91.116.142]

Trace complete.
------------------------------------------------------

Chicago:

Tracing route to chge308.multiplay.co.uk [199.21.112.122]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms api.home [192.168.1.254]
2 14 ms 14 ms 14 ms 217.32.141.128
3 14 ms 14 ms 14 ms 217.32.141.190
4 17 ms 17 ms 16 ms 213.120.161.122
5 18 ms 17 ms 18 ms 217.41.222.50
6 17 ms 17 ms 17 ms 217.41.222.182
7 17 ms 17 ms 17 ms acc2-10GigE-0-7-0-4.bm.21cn-ipp.bt.net [109.159.
248.198]
8 24 ms 23 ms 23 ms core1-te-0-13-0-4.ilford.ukcore.bt.net [109.159.
248.136]
9 24 ms 23 ms 23 ms core1-pos9-1.telehouse.ukcore.bt.net [194.74.65.
114]
10 23 ms 23 ms 23 ms t2as1-tge4-4.uk-lon1.eu.bt.net [166.49.211.145]

11 22 ms 21 ms 22 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.49]
12 24 ms 24 ms 25 ms xe-3-0-0.cr1.lhr1.uk.nlayer.net [195.66.226.37]

13 22 ms 22 ms 22 ms ae2-70g.cr1.lhr1.uk.nlayer.net [69.22.139.62]
14 90 ms 90 ms 90 ms xe-8-1-0.cr1.nyc2.us.nlayer.net [69.22.142.62]
15 126 ms 112 ms 111 ms xe-3-2-0.cr2.ord1.us.nlayer.net [69.22.142.85]
16 112 ms 124 ms 112 ms po6.ar2.ord1.us.scnet.net [69.31.111.6]
17 113 ms 113 ms 113 ms 62.po2.ar2.ord6.us.scnet.net [75.102.3.230]
18 113 ms 113 ms 113 ms as36352.po4.ar2.ord6.us.scnet.net [204.93.192.19
0]
19 112 ms 112 ms 112 ms fr171.aggr.chi.colocrossing.com [206.217.133.150
]
20 112 ms 113 ms 112 ms chge308.multiplay.co.uk [199.21.112.122]

Trace complete.>

[sweeper]

Thanks for posting these! It looks like Ash and I are onto the same thing.

What I am seeing is it appears that their servers suffer from congestion, Lets take the Chicago server for example. The important part of these logs shows up around this point
12 24 ms 24 ms 25 ms xe-3-0-0.cr1.lhr1.uk.nlayer.net [195.66.226.37]
9 76 ms 77 ms 76 ms ae1-70g.cr1.ewr1.us.nlayer.net [69.31.95.173]
It looks like there is some congestion between nlayer's nodes. There is not much we can do about this.

The same goes for NY server. Here you can see the trade off from the ISP to the first node. This seems to be the main point where we have an issue.

9 21 ms 21 ms 20 ms core1-pos9-0.telehouse.ukcore.bt.net [62.6.201.118]
10 83 ms 203 ms 203 ms t2as1-tge4-4.uk-lon1.eu.bt.net [166.49.211.145]

For testing methods I traced the uk server as it seems to have few issues.

Tracing route to host-85-236-100-91.multiplay.co.uk [85.236.100.91]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 7 ms 6 ms 7 ms 10.125.112.1
3 15 ms 15 ms 15 ms gw01.mtun.phub.net.cable.rogers.com [66.185.89.4
1]
4 7 ms 7 ms 7 ms kitchener1.cable.teksavvy.com [24.246.55.38]
5 13 ms 13 ms 13 ms kitchener1.cable.teksavvy.com [24.246.55.33]
6 34 ms 12 ms 13 ms peer1.bdr02.tor.packetflow.ca [64.34.236.121]
7 * * * Request timed out.
8 * * * Request timed out.
9 105 ms 105 ms 106 ms linx1.multiplay.co.uk [195.66.224.224]
10 103 ms 105 ms 105 ms host-85-236-100-91.multiplay.co.uk [85.236.100.9
1]

Trace complete.

Here we can see an interesting development, The server has the least issues also has the least jumps between nodes. Circumstantial? probably. But if you consider that ever jump made creates another point for ether packet loss or issues with latency. It would not be that crazy to consider this as an option for why some of us experience rubber banding and general laggyness when our ping's are not that bad.

So does this really help us? a little bit. It gives a good starting point to do further research into solving the issue with the two us servers.

[madcow]

NFO NY

Tracing route to c-74-91-116-142.internap-nyc.nfoservers.com [74.91.116.142]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms
2 <1 ms <1 ms <1 ms
3 2 ms 2 ms 2 ms
4 1 ms <1 ms <1 ms
5 3 ms 3 ms 2 ms gi0-6-0-26.londsh-rbr1.ja.net [146.97.136.253]
6 4 ms 3 ms 3 ms ae3.lond-sbr1.ja.net [146.97.35.145]
7 68 ms 3 ms 4 ms ae13.lond-sbr4.ja.net [146.97.33.134]
8 3 ms 4 ms 3 ms so-2-0-0.lon12.ip4.tinet.net [77.67.76.221]
9 75 ms 75 ms 113 ms xe-10-1-0.nyc30.ip4.tinet.net [89.149.184.129]
10 75 ms 75 ms 75 ms internap-gw.ip4.tinet.net [77.67.70.98]
11 76 ms 76 ms 76 ms border1.pc1-bbnet1.ext1.nym.pnap.net [216.52.95.14]
12 74 ms 74 ms 74 ms c-74-91-116-142.internap-nyc.nfoservers.com [74.91.116.142]

Multiplay Chicago

Tracing route to chge308.multiplay.co.uk [199.21.112.122]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms
2 <1 ms <1 ms <1 ms
3 2 ms 2 ms 2 ms
4 <1 ms <1 ms <1 ms
5 3 ms 3 ms 2 ms gi0-6-0-26.londsh-rbr1.ja.net [146.97.136.253]
6 3 ms 2 ms 2 ms ae3.lond-sbr1.ja.net [146.97.35.145]
7 3 ms 3 ms 3 ms ae13.lond-sbr4.ja.net [146.97.33.134]
8 4 ms 3 ms 3 ms ae0.lond-gw-ixp4.ja.net [146.97.35.182]
9 7 ms 4 ms 7 ms xe-0-3-0.cr1.lhr1.uk.nlayer.net [195.66.224.37]
10 5 ms 3 ms 3 ms ae2-70g.cr1.lhr1.uk.nlayer.net [69.22.139.62]
11 71 ms 83 ms 71 ms xe-11-3-1.cr1.nyc3.us.nlayer.net [69.22.142.132]
12 93 ms 71 ms 70 ms ae2-70g.cr1.ewr1.us.nlayer.net [69.31.95.145]
13 88 ms 88 ms 89 ms xe-5-0-0.cr1.ord1.us.nlayer.net [69.22.142.74]
14 90 ms 90 ms 89 ms ae0-40g.cr2.ord1.us.nlayer.net [69.31.111.154]
15 90 ms 90 ms 89 ms po6.ar2.ord1.us.scnet.net [69.31.111.6]
16 91 ms 91 ms 91 ms 62.po2.ar2.ord6.us.scnet.net [75.102.3.230]
17 89 ms 89 ms 89 ms as36352.po4.ar2.ord6.us.scnet.net [204.93.192.190]
18 91 ms 91 ms 91 ms fr171.aggr.chi.colocrossing.com [206.217.133.150]
19 89 ms 90 ms 90 ms chge308.multiplay.co.uk [199.21.112.122]

Multiplay EU

Tracing route to host-85-236-100-91.multiplay.co.uk [85.236.100.91]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms
2 <1 ms <1 ms <1 ms
3 2 ms 2 ms 2 ms
4 <1 ms <1 ms <1 ms
5 3 ms 3 ms 2 ms gi0-6-0-26.londsh-rbr1.ja.net [146.97.136.253]
6 2 ms 3 ms 2 ms ae3.lond-sbr1.ja.net [146.97.35.145]
7 3 ms 3 ms 4 ms ae13.lond-sbr4.ja.net [146.97.33.134]
8 3 ms 3 ms 3 ms ae0.lond-gw-ixp4.ja.net [146.97.35.182]
9 4 ms 3 ms 3 ms linx1.multiplay.co.uk [195.66.224.224]
10 3 ms 3 ms 3 ms host-85-236-100-91.multiplay.co.uk [85.236.100.91]


I like the EU server the best.

[sweeper]

3ms? Jesus man do you have the server directly beside you?

[Hitman47]

NY

Tracing route to c-74-91-116-142.internap-nyc.nfoservers.com [74.91.116.142]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms SE555 [192.168.2.1]
2 * * * Request timed out.
3 6 ms 6 ms 6 ms 172.29.16.129
4 17 ms 17 ms 17 ms pos13-1.milano8.mil.seabone.net [195.22.196.105]

5 18 ms 18 ms 18 ms te1-3.milano52.mil.seabone.net [195.22.196.183]

6 33 ms 33 ms 33 ms xe-1-1-0.mil10.ip4.tinet.net [213.200.68.61]
7 124 ms 124 ms 123 ms xe-9-1-0.nyc30.ip4.tinet.net [213.200.81.126]
8 120 ms 119 ms 120 ms internap-gw.ip4.tinet.net [77.67.70.98]
9 244 ms 368 ms 213 ms border2.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.
79]
10 119 ms 119 ms 119 ms c-74-91-116-142.internap-nyc.nfoservers.com [74.
91.116.142]

Trace complete.

Chicago

Tracing route to chge308.multiplay.co.uk [199.21.112.122]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms SE555 [192.168.2.1]
2 * * * Request timed out.
3 7 ms 6 ms 6 ms 172.29.16.129
4 36 ms 36 ms 35 ms pos13-3.milano8.mil.seabone.net [195.22.205.109]

5 51 ms 51 ms 50 ms cor1-core.pos9-3.swip.net [195.22.210.34]
6 66 ms 66 ms 66 ms xe-0-0-2.cr1.cdg1.fr.nlayer.net [69.22.139.49]
7 118 ms 136 ms 118 ms xe-11-3-0.cr1.nyc2.us.nlayer.net [69.22.142.128]

8 119 ms 118 ms 119 ms ae1-70g.cr1.ewr1.us.nlayer.net [69.31.95.173]
9 135 ms 134 ms 135 ms xe-5-0-0.cr1.ord1.us.nlayer.net [69.22.142.74]
10 135 ms 135 ms 136 ms po6.ar1.ord1.us.scnet.net [69.31.111.58]
11 136 ms 136 ms 137 ms 61.po1.ar1.ord6.us.scnet.net [75.102.3.226]
12 137 ms 138 ms 137 ms as36352.po4.ar1.ord6.us.scnet.net [204.93.192.18
6]
13 136 ms 136 ms 136 ms fr171.aggr.chi.colocrossing.com [206.217.133.150
]
14 136 ms 136 ms 137 ms chge308.multiplay.co.uk [199.21.112.122]

Trace complete.

[madcow]

3ms? Jesus man do you have the server directly beside you?

The server is in London and I live in London with a 100Mbit pipe.

[styphon]

3ms? Jesus man do you have the server directly beside you?

The server is in London and I live in London with a 100Mbit pipe.

Yes, he lives right next to the server.

As for timeouts, and it's one of two things. Most likely the specific router is configured to not respond to ping tests, or the router is having issues. If you're not experiencing any issues playing games or browsing the interwebz then it's most likely the former.