http://www.dslreports.com/forum/r21699416 en Mon, 14 Dec 2009 18:17:49 EDT Mon, 14 Dec 2009 18:17:49 EDT http://www.dslreports.com/forum/remark,21770043 astokes : It looks like where the gameserver peers with the backbone, some kind of congestion, the two traces both hit the game server host from a differnt edge router, thus the one you pass through looks like its overloaded, the server host needs to contact level3 directly, send them the trace they will get it fixed.]]> http://www.dslreports.com/forum/remark,21770043 Mon, 19 Jan 2009 16:21:01 EDT http://www.dslreports.com/forum/remark,21705377 anon : Thanks for your input wonko3fc,

the high ping on the first hop is not a worry it is to do with the firmware used for the router, if pinged directly it will come up as 1m/s. If it was an issue then hop2 should be 99+m/s.]]> http://www.dslreports.com/forum/remark,21705377 Thu, 08 Jan 2009 18:30:58 EDT http://www.dslreports.com/forum/remark,21702165 wonko3fc : I suspect you may have overlooked something I see as quite worrying. Namely your latency over your first hop:
1 90 ms 99 ms 99 ms api.home »192.168.1.254

You are also correct in your diagnosis of the last two hops:
27 182 ms 754 ms 757 ms lax-misdivision »4.78.195.18
28 756 ms 757 ms 754 ms 67.205.160.122
You have I believe already reported this so lets see what they make of it. Meantime, I would investigate the latency between what I take to be your PC and your router.

As an aside, I used to be with an ISP in the UK who, having 'optimised' their network left me with a higher latency going through their cloud. It was quicker to go around using another ISP! That's just wrong. They were not inclined to listen so it was bye bye high latency ISP.]]> http://www.dslreports.com/forum/remark,21702165 Thu, 08 Jan 2009 09:35:57 EDT http://www.dslreports.com/forum/remark,21699416 anon : Im having a problem with my BT internet using a BT homehub, I co-purchased a gaming server early last year which is located in San Diego, I live in the UK.

All last year my ping to this server averaged approx 205m/s 24hours a day (typical of UK to US) , but having re-visited at the start of this year (could have been before the new year) my ping averages at 350m/s 1200GMT to 2100GMT then at 2200GMT rockets right upto 750m/s. I have absolutely no idea and haven't changed anything router wise.

I have a friend who also uses BT internet and his pings are the same as mine, while another friend in the UK who uses SKY is not affected neither it seems is anyone else that I know who doesn't use BT.

Ive contacted BT about it and they told me about interleaving and switching it off within 2 days , they've failed to switch it off like they said as I believe they've probably just switched it to auto. But I can't see how turning interleaving off would sort this problem anyhow.

Ive also contacted the server people at Zanadoo and they are currently looking into it.

This is totally baffling me and would appreciate some much wiser heads to help me out.
There is some strange issue which I can't understand especially as my ping to other US servers is normal.

Below is a traceroute recorded after 2200GMT you can see it goes as high as 750m/s at lax-misdivision.
Last year my ping was 200-220m/s 24 hours a day.

Everyone else I know in UK/Europe who doesn't use BT Broadband is getting a normal ping (200-230m/s) to this server 24hours a day.

Thanks.

C:\Documents and Settings\Andy>tracert 67.205.160.122

Tracing route to 67.205.160.122 over a maximum of 30 hops

1 90 ms 99 ms 99 ms api.home »192.168.1.254
2 26 ms 28 ms 27 ms 217.47.204.186
3 27 ms 27 ms 28 ms 217.47.204.161
4 28 ms 29 ms 27 ms 213.123.108.6
5 27 ms 28 ms 27 ms 217.41.173.17
6 28 ms 28 ms 27 ms 217.41.173.66
7 27 ms 27 ms 28 ms 217.41.173.126
8 28 ms 28 ms 27 ms 217.41.173.54
9 27 ms 29 ms 29 ms 217.41.165.241
10 27 ms 28 ms 28 ms core2-pos14-3.manchester.ukcore.bt.net »194.72.2.153
11 35 ms 35 ms 33 ms core2-pos0-6-0-0.ealing.ukcore.bt.net »62.6.204.205
12 35 ms 32 ms 32 ms transit2-gig9-0-0.ealing.ukcore.bt.net »194.72.17.82
13 34 ms 32 ms 33 ms t2c2-ge13-0-0.uk-eal.eu.bt.net »166.49.168.53
14 34 ms 68 ms 33 ms 195.50.91.153
15 47 ms 34 ms 40 ms ae-31-53.ebr1.London2.Level3.net »4.68.117.94
16 35 ms 35 ms 33 ms ae-2.ebr1.London1.Level3.net »4.69.132.146
17 43 ms 36 ms 34 ms ae-2.ebr1.London1.Level3.net »4.69.132.146
18 37 ms 34 ms 34 ms ae-1-100.ebr2.London1.Level3.net »4.69.132.118
19 105 ms 105 ms 107 ms ae-61-61.csw1.NewYork1.Level3.net »4.69.134.66
20 129 ms 115 ms 118 ms ae-61-61.csw1.NewYork1.Level3.net »4.69.134.66
21 179 ms 180 ms 113 ms ae-64-64.ebr4.NewYork1.Level3.net »4.69.134.113
22 182 ms 175 ms 185 ms ae-2.ebr4.SanJose1.Level3.net »4.69.135.185
23 174 ms 178 ms 188 ms ae-84-84.csw3.SanJose1.Level3.net »4.69.134.250
24 182 ms 182 ms 181 ms ae-2.ebr3.LosAngeles1.Level3.net »4.69.132.10
25 185 ms 204 ms 187 ms ae-2.ebr3.LosAngeles1.Level3.net »4.69.132.10
26 183 ms 210 ms 184 ms ae-3-89.edge5.LosAngeles1.Level3.net »4.68.20.139
27 182 ms 754 ms 757 ms lax-misdivision »4.78.195.18
28 756 ms 757 ms 754 ms 67.205.160.122

Trace complete.

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

Below is a non BT Broadband users traceroute

------------------------------------------------------------
Tracing route to 67.205.160.122 over a maximum of 30 hops

01 1 ms 1 ms 1 ms 192.168.123.254
02 1 ms 1 ms 1 ms 169-225.surfsnel.dsl.internl.net »145.99.225.169
03 20 ms 19 ms 20 ms bbned.surfrt.nik-asd.internl.net »217.149.196.54
04 20 ms 20 ms 20 ms ge0-2.surfrt.nik-asd.internl.net »217.149.196.49
05 20 ms 20 ms 20 ms GE1-1-0.2118.JNR01.Asd002A.surf.net »145.145.19.61
06 20 ms 20 ms 20 ms AE0.500.JNR02.Asd002A.surf.net »145.145.80.65
07 21 ms 21 ms 27 ms ge-0-0-0-0-dcr1.amd.cw.net »195.2.21.5
08 28 ms 28 ms 29 ms xe-0-1-0.xcr1.lsw.cw.net »195.2.25.101
09 239 ms 221 ms 31 ms 195.50.118.229
10 28 ms 30 ms 36 ms ae-32-54.ebr2.London1.Level3.net »4.68.116.126
11 102 ms 101 ms 102 ms ae-42-42.ebr1.NewYork1.Level3.net »4.69.137.70
12 107 ms 108 ms 108 ms ae-61-61.csw1.NewYork1.Level3.net »4.69.134.66
13 104 ms 108 ms 108 ms ae-64-64.ebr4.NewYork1.Level3.net »4.69.134.113
14 180 ms 180 ms 181 ms ae-2.ebr4.SanJose1.Level3.net »4.69.135.185
15 189 ms 174 ms 180 ms ae-64-64.csw1.SanJose1.Level3.net »4.69.134.242
16 178 ms 179 ms 180 ms ae-63-63.ebr3.SanJose1.Level3.net »4.69.134.225
17 181 ms 179 ms 180 ms ae-2.ebr3.LosAngeles1.Level3.net »4.69.132.10
18 181 ms 180 ms 180 ms ae-63-63.csw1.LosAngeles1.Level3.net »4.69.137.34
19 178 ms 177 ms 178 ms ae-1-69.edge5.LosAngeles1.Level3.net »4.68.20.11
20 178 ms 178 ms 179 ms lax-misdivision »4.78.195.18
21 179 ms 178 ms 178 ms 67.205.160.122

Trace complete.]]> http://www.dslreports.com/forum/remark,21699416 Wed, 07 Jan 2009 20:14:25 EDT