How do you tell where BT are routing you?
You can't tell for sure, but tracert gives a pretty good idea.
In the tracert below you will see a jump from 7 to 11 between steps 4 and 5, and another jump from 11 to 16 between 8 and 9.
The figures indicate that machines 5..8 are close to each other, but somewhat remote from machines 4 and 9.
The '.sf' in the name of machine 8 suggests Sheffield; and others have talked about significant BT presence there.
Tracert interpretation is tricky because the numbers are not always very accurate.
You often see values for a machine A some way down the route as
higher than for a machine B further down the route.
In that case you can assume that A is just slow at responding to tracert requests.
I have often seen this for the first ealing machine, though in this particular tracert the figures look pretty clean.
Tracing route to bbc.co.uk [212.58.246.104]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.254
2 6 ms 5 ms 6 ms 172.16.14.14
3 * * * Request timed out.
4 7 ms 7 ms 7 ms 213.120.158.173
5 12 ms 11 ms 11 ms 212.140.206.82
6 11 ms 11 ms 11 ms 217.41.169.223
7 11 ms 11 ms 11 ms 217.41.169.109
8 12 ms 10 ms 11 ms acc2-xe-5-2-2.sf.21cn-ipp.bt.net [109.159.251.247]
9 18 ms 21 ms 16 ms core1-te0-0-0-7.ealing.ukcore.bt.net [109.159.251.33]
10 17 ms 16 ms 17 ms peer2-xe2-0-0.telehouse.ukcore.bt.net [109.159.254.106]
11 22 ms 24 ms 21 ms 194.74.65.42
12 * * * Request timed out.
13 21 ms 20 ms 20 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
14 21 ms 26 ms 22 ms 132.185.255.165
15 19 ms 21 ms 21 ms fmt-vip133.cwwtf.bbc.co.uk [212.58.246.104]
--
Moved (with trepidation turned relief) to BT Infinity 2 for upload speed. Happy BE user for several years.