cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
flamey
Contributor
1,311 Views
Message 31 of 66

Re: BT routing and latency issues

Seems your issue is hop4, I can understand how this would be irritating especially playing latency intensive games such as QL, CS on European servers as whilst 30ms say on fastpath could turn into 50ms with issues such as this.

As a side note I used to have 5-6hops to most UK destinations on sky - unfortunately its pretty widely known BT don't have the most efficient setup.

Comparative trace from essex:

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 5 ms 5 ms 217.32.146.71
3 5 ms 6 ms 5 ms 217.32.146.110
4 6 ms 6 ms 5 ms 213.120.156.42
5 6 ms 6 ms 6 ms 217.41.168.43
6 6 ms 5 ms 6 ms 217.41.168.107
7 6 ms 5 ms 5 ms 109.159.249.64
8 13 ms 7 ms 7 ms core1-te0-15-0-5.faraday.ukcore.bt.net [109.159.
249.31]
9 17 ms 11 ms 11 ms 213.131.193.8
10 7 ms 7 ms 7 ms peer2-xe9-0-0.telehouse.ukcore.bt.net [109.159.2
54.126]
11 8 ms 8 ms 8 ms 194.74.65.42
12 * * * Request timed out.
13 8 ms 7 ms 8 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
14 8 ms 8 ms 9 ms 132.185.255.60
15 7 ms 7 ms 7 ms 212.58.241.131

drizzy
Contributor
1,287 Views
Message 32 of 66

Re: BT routing and latency issues

Thanks for the trace flamey - that's what I sort of expected to get. I'm mostly playing QuakeWorld which is almost entirely played on continental servers 😕 

 

I think I've had a bit of a 'breakthrough' with this - I ran a traceroute from a VPS in London (with Linode) and got this:

 

traceroute to drizzys.ip (x.x.x.x), 30 hops max, 60 byte packets
1 212.111.33.229 (212.111.33.229) 5.175 ms 5.211 ms 5.245 ms
2 212.111.33.233 (212.111.33.233) 0.469 ms 0.518 ms 0.566 ms
3 te3-1-border76-01.lon2.telecity.net (217.20.44.217) 0.664 ms * *
4 85.90.238.45 (85.90.238.45) 0.867 ms * *
5 1-0-peer12-01.lon2.telecity.net (85.90.226.206) 0.862 ms * *
6 linx2.ukcore.bt.net (195.66.236.10) 0.864 ms 0.891 ms 0.862 ms
7 109.159.254.117 (109.159.254.117) 4.028 ms 3.935 ms 3.696 ms
8 acc2-10GigE-1-1-0.sf.21cn-ipp.bt.net (109.159.251.134) 9.648 ms 9.601 ms 9.621 ms
9 core2-gig9-0-0.sheffield.ukcore.bt.net (109.159.251.226) 11.886 ms 11.729 ms 11.795 ms
10 217.41.169.108 (217.41.169.108) 11.548 ms 11.533 ms 11.622 ms
11 217.41.169.232 (217.41.169.232) 9.479 ms 9.418 ms 9.508 ms
12 213.120.181.125 (213.120.181.125) 16.919 ms 213.120.181.173 (213.120.181.173) 16.339 ms 213.120.181.125 (213.120.181.125) 17.121 ms

....

 

Sheffield? I'm routed via sheffield? Perhaps that's what the 'sf' in hop 8 refers to as well. This basically explains it. 😕 We have: 

hop 7 - london somewhere

hop 8-11 - sheffield? based on hop 8/9s name

hop 12 - back into London and my IP follows shortly afterwards.

 

Why am I being routed via sheffield!?

0 Ratings
Webby
Distinguished Sage
1,276 Views
Message 33 of 66

Re: BT routing and latency issues

I believe one of BT's radius servers is located in Sheffield.

The radius server is responsible for allocating your IP address.
If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the the reply answers your question then please mark as ’Mark as Accepted Solution’
0 Ratings
flamey
Contributor
1,269 Views
Message 34 of 66

Re: BT routing and latency issues

That looks likely, i've seen people near London routed via mancs before. I'm guessing you've tried refreshing the ip quite a few times to try and get an alternative route?

 

Some useful information on the 21cn network here - as you can see from my trace I am routed through the faraday core node of London Central.

drizzy
Contributor
1,249 Views
Message 35 of 66

Re: BT routing and latency issues

Yeah, I've tried a few times and ended up with 17ms to BBC at one point - will have to give that more of a go tonight. 

 

There's a whole bunch of nodes that would make more sense geographically - Guildford (25mi), Slough (17mi), Southbank (8 miles!) are the obvious ones. 

 

If reconnecting at peak this evening doesn't make any difference I'll try reconnecting at 2am when there might theoretically be fewer people connected (?). 

 

 

 

 

0 Ratings
Webby
Distinguished Sage
1,239 Views
Message 36 of 66

Re: BT routing and latency issues

Actual distance to the server doesn't always dictate how fast of a response you'll get. It depends on how you're routed.
If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the the reply answers your question then please mark as ’Mark as Accepted Solution’
0 Ratings
Wizen
Aspiring Expert
1,229 Views
Message 37 of 66

Re: BT routing and latency issues

I've found that spoofing a new MAC address a few times will usually get me a new IP in a different block and get me routed through Ealing (5 minutes up the road) as opposed to Gloucester or Reading. This usually cuts my latency by 3-4ms.

 

It's not much, but when you're struggling to get response times to London servers under 35ms, every little bit helps.

 

We've got 2 load balanced BT ADSL2+ connections in the office, and routing isn't any better than at home on the Infinity connection. I've just accepted that BT/BT Business must be uniformally **bleep** at routing customers in west London.

 

Connection 1:

 

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

  1    21 ms    22 ms    22 ms  217.32.145.232
  2    22 ms    21 ms    20 ms  217.32.145.232
  3    21 ms    22 ms    25 ms  217.32.146.30
  4    28 ms    30 ms    29 ms  213.120.181.86
  5    26 ms    26 ms    26 ms  217.41.169.239
  6    26 ms    28 ms    28 ms  217.41.169.109
  7    29 ms    26 ms    86 ms  acc2-10GigE-0-3-0.sf.21cn-ipp.bt.net [109.159.25
1.210]
  8    36 ms    34 ms    35 ms  core1-te0-2-2-0.ilford.ukcore.bt.net [109.159.25
1.145]
  9    33 ms    33 ms    34 ms  peer2-xe10-0-0.telehouse.ukcore.bt.net [109.159.
254.128]
 10    34 ms    34 ms    34 ms  194.74.65.42
 11     *        *        *     Request timed out.
 12    34 ms    32 ms    32 ms  ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
 13    34 ms    35 ms    35 ms  132.185.255.60
 14    34 ms    32 ms    32 ms  212.58.241.131

Trace complete.

 

Connection 2:

 

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

  1    18 ms    17 ms    17 ms  217.32.145.232
  2    18 ms    18 ms    18 ms  217.32.145.232
  3    17 ms    16 ms    17 ms  217.32.146.46
  4    21 ms    22 ms    23 ms  213.120.181.134
  5    24 ms    22 ms    22 ms  217.41.169.231
  6    21 ms    22 ms    24 ms  217.41.169.109
  7    68 ms    21 ms    31 ms  109.159.251.229
  8    34 ms    33 ms    34 ms  core2-te0-5-0-7.ealing.ukcore.bt.net [109.159.25
1.151]
  9    28 ms    32 ms    29 ms  peer2-xe10-0-0.telehouse.ukcore.bt.net [109.159.
254.128]
 10    34 ms    33 ms    63 ms  194.74.65.42
 11     *        *        *     Request timed out.
 12    31 ms    30 ms    31 ms  ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
 13    33 ms    32 ms    34 ms  132.185.255.60
 14    31 ms    32 ms    34 ms  212.58.241.131

Trace complete.

 

 

drizzy
Contributor
1,203 Views
Message 38 of 66

Re: BT routing and latency issues

Reconnecting a few times this morning didn't really make much difference - it bounced around between 17 and 21-22ms to bbc.co.uk. 

 

I've found a post on another forum of someone from the southwest (Somerset I think) also getting routed via Sheffield. Their post was dated a year ago! Surely this should be considered a fault? It's utter idiocy 😕

 

 

0 Ratings
Jonny
Contributor
1,176 Views
Message 39 of 66

Re: BT routing and latency issues

How do you save the tracert in DOS Command prompt?

 

Just got a corker 145msecs plus a time out, reported problems twice and twice marked as 'solved' by BT when nothing been done.

 

 

0 Ratings
Bullitt
Distinguished Expert
1,171 Views
Message 40 of 66

Re: BT routing and latency issues

press the top lh square [C:\] to access the edit menu then select all and copy