Hi guys,
This tournament today showed very clearly that my connection don't like our servers. I had a ping between 160 and 200 throughout the tournament but the real problem was the choke and loss I experienced.
Why do I post this here? Well, if it doesn't change it may be a problem to play home matches for me. I do not have this problem on other servers e.g. CoFR or CIGS but only on our three servers.
I have sent an e-mail to my ISP and hope to resolve it through them. I don't think that that is the problem though as my connection behaves on other UK servers.
Well, if no change happens I could either play with it or step down and let someone else be 2iC.
Here is a trace route I have made.
1 1 ms <1 ms <1 ms 192.168.3.1
2 5 ms 27 ms 43 ms 82.182.97.1
3 30 ms 7 ms 5 ms cr1-gig1-3.djakneg16.mlm.bostream.net [82.182.4.13]
4 15 ms 34 ms 44 ms cr2-gig1-1.torgg4.sth.bostream.net [82.182.0.17]
5 28 ms 43 ms 15 ms cr1-gig1-16.torgg4.sth.bostream.net [82.182.0.9]
6 19 ms 17 ms 54 ms ge-2-0-0.401.ar1.ARN1.gblx.net [64.213.23.153]
7 25 ms 27 ms 28 ms pos9-0-2488M.cr1.HAM1.gblx.net [67.17.72.234]
8 136 ms 137 ms 127 ms pos0-0-2488M.cr2.WDC2.gblx.net [67.17.71.26]
9 165 ms 147 ms 133 ms so2-1-0-2488M.ar1.DCA3.gblx.net [67.17.67.57]
10 140 ms 176 ms 158 ms p1-3.pr01.iad01.atlas.psi.net [154.54.10.117]
11 145 ms 132 ms 152 ms p1-1.core01.dca01.atlas.cogentco.com [154.54.1.185]
12 133 ms 191 ms 149 ms p15-0.core02.dca01.atlas.cogentco.com [66.28.4.22]
13 131 ms 131 ms 131 ms p6-0.core01.jfk02.atlas.cogentco.com [66.28.4.82]
14 136 ms 131 ms 130 ms g7.ba21.b001587-2.jfk02.atlas.cogentco.com [66.250.11.206]
15 131 ms 129 ms 129 ms Viatel.demarc.cogentco.com [38.112.0.182]
16 150 ms 144 ms 130 ms pos9-0.core-01.egh.uk.viatel.net [135.196.65.1]
17 130 ms 190 ms 139 ms pos9-1-0.acc-001.tlh.uk.viatel.net [135.196.65.141]
18 148 ms 156 ms 130 ms fa2-0-b1-thn.lon.caladan.net.uk [80.71.4.13]
19 143 ms 147 ms 148 ms itechmedia.mcc.caladan.net.uk [80.71.4.70]
20 141 ms 138 ms 139 ms homer.deadmen.co.uk [193.110.88.20]
Cheers,
7 25 ms 27 ms 28 ms pos9-0-2488M.cr1.HAM1.gblx.net [67.17.72.234]
8 136 ms 137 ms 127 ms pos0-0-2488M.cr2.WDC2.gblx.net [67.17.71.26]
Immediate thoughts, going through Global Crossing's AS you go from Hamburg to Washington DC, not what I would call the optimum route to the UK!!!!
80 - 100ms is the normal delay from Europe to the USA
But what is confusing the hell out of me is why at this point where you eventually reach the UK:
14 136 ms 131 ms 130 ms g7.ba21.b001587-2.jfk02.atlas.cogentco.com [66.250.11.206]
15 131 ms 129 ms 129 ms Viatel.demarc.cogentco.com [38.112.0.182]
16 150 ms 144 ms 130 ms pos9-0.core-01.egh.uk.viatel.net [135.196.65.1]
you don't experience another 80ms jump.
Sadako, can you please post a traceroute to CoFR from your pc, I would like to see a good route.
C:\Documents and Settings\Mats>tracert 82.136.20.11
Tracing route to neo.sov.inetgaming.co.uk [82.136.20.11]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.3.1
2 12 ms 32 ms 6 ms 82.182.97.1
3 14 ms 25 ms 26 ms cr1-gig1-3.djakneg16.mlm.bostream.net [82.182.4.13]
4 14 ms 25 ms 26 ms cr2-gig1-1.torgg4.sth.bostream.net [82.182.0.17]
5 19 ms 50 ms 29 ms cr1-gig1-16.torgg4.sth.bostream.net [82.182.0.9]
6 17 ms 26 ms 27 ms ge-2-0-0.401.ar1.ARN1.gblx.net [64.213.23.153]
7 15 ms 24 ms 44 ms s-b3-pos15-2.telia.net [213.248.101.37]
8 17 ms 42 ms 27 ms s-bb2-pos7-1-0.telia.net [213.248.66.9]
9 50 ms 62 ms 68 ms kbn-bb2-pos0-0-0.telia.net [213.248.65.29]
10 50 ms 68 ms 65 ms ldn-bb2-pos0-1-0.telia.net [213.248.64.66]
11 65 ms 71 ms 65 ms ldn-b1-pos5-0.telia.net [213.248.74.14]
12 53 ms 50 ms 65 ms claranet-01638-ldn-b1.c.telia.net [213.248.75.74]
13 68 ms 81 ms 68 ms fe-4-0-redbus-boomer.router.clara.net [213.253.16.67]
14 65 ms 93 ms 74 ms fe-1-0-hex-niobium.burstfire.net.uk [217.158.78.6]
15 52 ms 78 ms 92 ms 82.136.0.199
16 65 ms 93 ms 67 ms neo.sov.inetgaming.co.uk [82.136.20.11]
Pings about 60
I went onto Global Crossing's Route server route-server.gblx.net and traced to Meat Hook. This proves that you are definately going through the USA before coming to the UK, see hops 15, 16 and 17, same as Sadako's.
route-server.phx1>traceroute 193.110.88.20
Type escape sequence to abort.
Tracing the route to homer.deadmen.co.uk (193.110.88.20)
1 fe0-1.ar1.PHX1.gblx.net (206.132.117.1) 0 msec 0 msec 0 msec
2 pos3-0-155M.cr2.PHX1.gblx.net (67.17.70.106) 4 msec 0 msec 0 msec
3 pos1-0-2488M.cr2.LAX1.gblx.net (67.17.68.134) 8 msec 12 msec 8 msec
4 so1-0-0-2488M.ar1.LAX2.gblx.net (67.17.67.169) 12 msec 12 msec 12 msec
5 208.50.13.198 8 msec 8 msec 12 msec
6 p6-0.core01.lax01.atlas.cogentco.com (154.54.2.209) [AS 16631] 12 msec 12 ms
ec 12 msec
7 p5-0.core01.san01.atlas.cogentco.com (66.28.4.78) [AS 16631] 12 msec 12 msec
12 msec
8 p6-0.core01.iah01.atlas.cogentco.com (66.28.4.5) [AS 16631] 64 msec 68 msec
64 msec
9 p15-0.core01.tpa01.atlas.cogentco.com (66.28.4.46) [AS 16631] 68 msec 68 mse
c 68 msec
10 p5-0.core01.mco01.atlas.cogentco.com (66.28.4.141) [AS 16631] 68 msec 72 mse
c 68 msec
11 p14-0.core01.jax01.atlas.cogentco.com (66.28.4.154) [AS 16631] 72 msec 72 ms
ec 68 msec
12 p5-0.core01.atl01.atlas.cogentco.com (66.28.4.138) [AS 16631] 72 msec 68 mse
c 72 msec
13 p5-0.core02.dca01.atlas.cogentco.com (66.28.4.162) [AS 16631] 68 msec 72 mse
c 68 msec
14 p6-0.core01.jfk02.atlas.cogentco.com (66.28.4.82) [AS 16631] 76 msec 76 msec
76 msec
15 g7.ba21.b001587-2.jfk02.atlas.cogentco.com (66.250.11.206) [AS 16631] 76 mse
c 76 msec 76 msec
16 Viatel.demarc.cogentco.com (38.112.0.182) [AS 16631] 144 msec 144 msec 148 m
sec
17 pos4-0.core-01.tlh.uk.viatel.net (135.196.65.134) [AS 8190] 148 msec 148 mse
c 144 msec
18 pos0-1-0.acc-001.tlh.uk.viatel.net (135.196.65.21) [AS 8190] 148 msec 148 ms
ec 148 msec
19 fa2-0-b1-thn.lon.caladan.net.uk (80.71.4.13) [AS 20834] 220 msec 340 msec 16
8 msec
20 lipex1.lon3.as8553.net (193.109.219.48) [AS 21238] 148 msec 144 msec 148 mse
c
21 fa1-0.lon6.as8553.net (195.10.255.194) [AS 8553] 148 msec 148 msec 148 msec
22 s6-1.bris1.as8553.net (195.10.255.134) [AS 8553] 148 msec 148 msec 152 msec
23 fa0-0-2.bris2.as8553.net (195.10.254.82) [AS 8553] 148 msec 148 msec 152 mse
c
24 s6-0.man1.as8553.net (195.10.255.14) [AS 8553] 152 msec 152 msec 156 msec
25 cwgtway2.crosswired.co.uk (195.10.230.11) [AS 8553] 156 msec 156 msec 152 ms
ec
26 homer.deadmen.co.uk (193.110.88.20) [AS 21448] 244 msec 160 msec 160 msec
Is there anything I can do about it?
5 19 ms 50 ms 29 ms cr1-gig1-16.torgg4.sth.bostream.net [82.182.0.9]
6 17 ms 26 ms 27 ms ge-2-0-0.401.ar1.ARN1.gblx.net [64.213.23.153]
7 15 ms 24 ms 44 ms s-b3-pos15-2.telia.net [213.248.101.37]
This is the point where there is a difference when going to CoFR. Both traceroutes are the same up until hop 6 then when going to MH you continue through the Global Crossing Network which thinks MH can be reached quicker by going to the USA. For CoFR you cross into Telia's network and go direct to the UK.
You need to find out why Crosswired has an optimum route via the USA from your ISP but other UK sites go through Telia. Crosswired should only be routable via the USA when the main European route to London is not available.
We have seen a few routing issues at work for users trying to get to certain web sites and routing through Global Crossing and taking long sub-optimal routes. You could get your ISP to talk to Global Crossing but that is a long shot, ISPs don't really do eachother any favours.
You may find the problem corrects itself over the next few weeks, things like that happen on the Internet from time to time.
Stryker may be able to help you out as it is his address range that is getting routed round the houses and that's not good for business.
route-server.phx1>show ip route homer.deadmen.co.uk
Routing entry for 193.110.88.0/24
Known via "bgp 3549", distance 200, metric 100
Tag 174, type internal
Last update from 206.132.117.1 06:36:29 ago
Routing Descriptor Blocks:
* 206.132.117.1, from 67.17.81.117, 06:36:29 ago
Route metric is 100, traffic share count is 1
AS Hops 5, BGP network version 2394996671
The whole 24 bit subnet is getting the same treatment obviously.