[stevebarnes15]

Hi guys, we rent a cod 4 server off eg-servers.co.uk, since saturday all our european customers pings have shot through the roof making the game unplayable for them.

After doing a tracert command to eg-servers.co.uk from spain where one of our members is based,and then pinging each hop individually, the only 2 problems we had were with killercreation which was returning all 4 packets lost, and above.net which was timing out and not returning any results.

Is there anything you guys can do as we are starting to lose custom,which a large percentage is european.
We have had server config problems lately and have just started getting custom back,we cannot afford to have a high latency problem.

Many Thanks,

[Nadir]SKL.

[KC-Justin]

Hi

To be able to help diagnose and hopefully resolve the issue we'll need a trace route from the end user and his or her IP.

[stevebarnes15]

Ok here is the tracert results,by the way thanks for a speedy reply.



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

C:\Documents and Settings\Antony>tracert eg-servers.co.uk

Tracing route to eg-servers.co.uk [217.146.91.33]
over a maximum of 30 hops:

1 62 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 31 ms 31 ms 31 ms 172.31.255.254
3 31 ms 31 ms 31 ms 62.36.71.177
4 31 ms 31 ms 31 ms 62.36.203.129
5 39 ms 39 ms 39 ms 62.36.203.153
6 39 ms 39 ms 39 ms 62.36.187.69
7 40 ms 40 ms 40 ms 193.251.247.25
8 39 ms 39 ms 39 ms ge-4-3-0-0.madcr2.Madrid.opentransit.net [193.25
1.128.178]
9 65 ms 66 ms 66 ms ft-above-3.fr.above.net [84.207.21.194]
10 65 ms 64 ms 66 ms pnias5511-ge9-3.mpr9.cdg2.fr.above.net [84.207.2
1.193]
11 64 ms 64 ms 64 ms te3-2.mpr2.cdg2.fr.above.net [64.125.23.18]
12 122 ms 121 ms 122 ms ge4-7.er2a.cdg2.fr.above.net [64.125.23.22]
13 123 ms 123 ms 124 ms abovenet.killercreation.co.uk [79.141.38.132]
14 124 ms 123 ms 123 ms web.alpha-networks.co.uk [217.146.91.33]

Trace complete.

I'm assuming that his ip is the first result in the tracert.

[KC-Justin]

Hi

The issue is in the back route to the end user, see below:

[root@kc-89-4 ~]# traceroute 62.36.71.177
traceroute to 62.36.71.177 (62.36.71.177), 30 hops max, 38 byte packets
1 gateway (81.19.219.1) 0.363 ms 0.309 ms 0.237 ms
2 abovenet (79.141.38.130) 1.238 ms 1.228 ms 1.238 ms
3 * so-7-2-0-0.loncr1.london.opentransit.net (193.251.250.189) 50.155 ms *
4 * * *
5 pos0-9-4-0.pastr1.paris.opentransit.net (193.251.242.250) 59.839 ms pos0-1-0-0.pastr1.paris.opentransit.net (193.251.128.222) 58.681 ms pos0-9-4-0.pastr1.paris.opentransit.net (193.251.242.250) 59.194 ms
6 po9-0.barcr1.barcelona.opentransit.net (193.251.242.38) 75.932 ms 76.183 ms 77.068 ms
7 * * *
8 * * *

This is almost an identical problem seen with a Polish ISP this morning. The Opentransit network seems to have some issues at the mo. If you find the end users IP we can see about trying to avoid the Opentransit network.

[KC-Justin]

That's a local IP there, need his real world ip. Get him to go here http://www.ip-adress.com/

If another route is available to that specific ISP which avoids opentransit then yes it will help users on that ISP.

[KC-Justin]

Ok, ask him to run another trace route and copy it in here please. I've made a few changes to the outbound route so we'll see if this has a positive effect or not.

[stevebarnes15]

ok buddy,here it is:



C:\Documents and Settings\Antony>tracert eg-servers.co.uk

Tracing route to eg-servers.co.uk [217.146.91.33]
over a maximum of 30 hops:

1 45 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 32 ms 31 ms 32 ms 172.31.255.254
3 32 ms 32 ms 31 ms 62.36.70.177
4 39 ms 38 ms 39 ms 62.36.203.153
5 39 ms * * 62.36.187.69
6 39 ms 40 ms 49 ms tengige0-3-0-2.madtr1.Madrid.opentransit.net [19
3.251.251.177]
7 40 ms 39 ms 39 ms ge-3-0-0-0.madcr2.Madrid.opentransit.net [193.25
1.242.102]
8 65 ms 64 ms 64 ms ft-above-gige-1.mpr1.cdg2.fr.above.net [208.184.
210.234]
9 64 ms 63 ms 64 ms above-ft-gige-1.mpr1.cdg2.fr.above.net [208.184.
210.233]
10 64 ms 64 ms 64 ms te3-2.mpr2.cdg2.fr.above.net [64.125.23.18]
11 120 ms * * ge4-7.er2a.cdg2.fr.above.net [64.125.23.22]
12 82 ms 83 ms 83 ms abovenet.killercreation.co.uk [79.141.38.132]
13 83 ms 81 ms 82 ms web.alpha-networks.co.uk [217.146.91.33]

Trace complete.

Just to let you know also that his ping has dropped from 130-140 to 84.

good job,

[tentative]

Hello, here is another Tracert that one of our server regulars sent in:

[KC-Justin]

Hi

High latency on the last few hops normally suggests an issue in the back trace. I'll need the end users IP to diagnose this.

[Wooza]

Good Evening,

I have also the same problem now since the last 2 days. My IP is: xx.xxx.xx.xxat the moment (will be renewed every day) and here my tracert:

C:\Users\Wooza>tracert 81.19.219.82

Routenverfolgung zu gameserver.killercreation.co.uk [81.19.219.82] über maximal
30 Abschnitte:

  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2    46 ms    45 ms    46 ms  217.0.116.32
  3    45 ms    45 ms    45 ms  217.0.66.86
  4    62 ms    62 ms    62 ms  217.239.37.50
  5    63 ms    63 ms   150 ms  217.243.218.146
  6   143 ms   144 ms   148 ms  abovenet.killercreation.co.uk [79.141.38.132] (its normaly above 290ms)
  7   149 ms   151 ms   153 ms  gameserver.killercreation.co.uk [81.19.219.82] (its normaly above 290ms)

Ablaufverfolgung beendet.

C:\Users\Wooza>

This post has been edited by Wooza: 14 March 2009 - 03:57 PM

[KC-Justin]

Hi

The issue is in the back route to your ISP, please see below:

traceroute to 84.176.57.28 (84.176.57.28), 30 hops max, 38 byte packets
1 gateway (81.19.219.1) 0.266 ms 0.308 ms 0.237 ms
2 telewest (194.117.147.65) 1.609 ms 1.228 ms 1.237 ms
3 popl-t3core-1b-ge-210-0.network.virginmedia.net (62.255.81.125) 1.360 ms 1.355 ms 1.613 ms
MPLS Label=124336 CoS=5 TTL=1 S=0
4 pop-bb-b-as2-0.network.virginmedia.net (213.105.174.238) 1.602 ms 1.228 ms 1.239 ms
5 so-7-0-0-dcr1.tsd.cw.net (166.63.211.129) 1.483 ms 1.605 ms 1.498 ms
6 so-3-0-0-dcr2.amd.cw.net (195.2.10.106) 11.594 ms 11.724 ms 11.478 ms
7 as0-dcr1.amd.cw.net (195.2.10.153) 11.729 ms 11.721 ms 11.609 ms
8 so-6-0-0-zcr1.dus.cw.net (195.2.10.238) 15.097 ms so-3-0-0-zcr1.dus.cw.net (195.2.10.17) 14.847 ms so-6-0-0-zcr1.dus.cw.net (195.2.10.238) 14.971 ms
9 ae1-zcr2.dus.cw.net (195.2.10.206) 78.931 ms 77.685 ms 78.444 ms
10 dtag.dus.cw.net (195.2.2.70) 209.357 ms 207.856 ms 209.491 ms
11 f-eb1-i.f.de.net.dtag.de (62.154.16.238) 210.361 ms 208.110 ms 208.488 ms
12 217.0.66.81 (217.0.66.81) 212.611 ms 210.609 ms 206.358 ms

The high latency is falling within your ISP's network (Deutsche Telekom AG). Unfortunately there is not a lot we can do other than suggesting contacting your ISP.

[KC-Justin]

To follow this up, I've found a way around the problem hop using another of our transit peers AboveNet instead of Telewest, please see below:

traceroute to 84.176.57.28 (84.176.57.28), 30 hops max, 38 byte packets
1 gateway (81.19.219.1) 0.336 ms 0.310 ms 0.238 ms
2 abovenet (79.141.38.130) 1.483 ms 1.353 ms 1.238 ms
3 217.243.218.145 (217.243.218.145) 1.233 ms 1.232 ms 1.362 ms
4 f-eb1-i.f.de.net.dtag.de (62.154.16.234) 19.974 ms 19.468 ms 19.101 ms
5 217.0.66.81 (217.0.66.81) 20.348 ms 25.720 ms 20.098 ms

Hopefully the forward trace should be a lot better.

[Wooza]

Ah. ok Thanks for the Info! At the Moment (~5pm) is the Latency normally, i hope it will be stable in the Future. Thank you for your fast answer!