Slow BT routing - What is up with it?

chris6273

chris6273

chris6273

Associate
Joined
7 Jan 2009
Posts
78
Hi guys,

I have a query. Since around April last year (When I believe my exchange was switched over to IPSC) my ping has more than doubled even though I am still on the same Fastpath profile and still get the same sync.

Here is the problem:


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

1 <1 ms <1 ms <1 ms xxxx
2 <1 ms <1 ms <1 ms xxxx
3 13 ms 13 ms 13 ms 217.47.206.58
4 13 ms 13 ms 13 ms 217.47.206.161
5 21 ms 20 ms 20 ms 213.1.69.42
6 20 ms 20 ms 20 ms 213.120.179.54
7 20 ms 20 ms 20 ms 213.120.179.182
8 20 ms 20 ms 19 ms 109.159.251.233
9 27 ms 27 ms 28 ms core1-te0-4-0-2.ilford.ukcore.bt.net [109.159.251.129]
10 27 ms 25 ms 26 ms core1-pos9-1.telehouse.ukcore.bt.net [194.74.65.114]
11 37 ms 26 ms 26 ms 194.74.65.42
12 26 ms 27 ms 25 ms 212.58.238.153
13 27 ms 26 ms 29 ms rdirslb0.thdo.bbc.co.uk [212.58.224.136]
14 31 ms 25 ms 26 ms virtual3.rbsov.bbc.co.uk [212.58.254.252]

Trace complete.

The hop in bold seems to add another 7ms ping on top of my 13ms ping to the 3rd hop (First BT hop).
I have done some tracerts on some friends' connections who live a few miles away on a different exchange and the 213.1.69.xxx address does not seem to add more than 1ms ping to the route.
I have tried to experiment by modifying the DNS servers on my DG834GT and it resulted in a different IP for the 5th hop in bold but it still had the same delay.

I know this is only 7ms I am talking about but I'm just very curious why there is a delay on that hop.

Does anyone have any idea what BT might have done to it? I used to get 13ms ping to bbc.co.uk but now its more around the 25-27ms range (Around double).


Thanks for your answers
 
Last edited by a moderator:
That's funny because I reside in Somerset ;) Near Bridgwater to be exact.

But why would it be that a connection I tested on an exchange about 3 miles away had no delay on that 213.1.69.xxx hop? Obviously the 2nd hop would be different on different connections but once it enters the 21CN core, it should be in the 1ms range?
 
Last edited:
Looks like your first 213.xxx.xxx.xxx address adds quite a bit of latency. I've just put those DNS servers back and I'm being routed though a different 213 address:

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

1 <1 ms <1 ms <1 ms core1-r-0-0-2.evans6273.homeip.net [10.5.15.253]
2 1 ms 1 ms 1 ms core1-r-0-0-1.evans6273.homeip.net [10.5.14.254]
3 13 ms 13 ms 13 ms 217.47.206.58
4 14 ms 13 ms 13 ms 217.47.72.161
5 20 ms 21 ms 20 ms 213.1.69.46
6 20 ms 20 ms 20 ms 213.120.179.26
7 21 ms 21 ms 20 ms 213.120.179.178
8 28 ms 26 ms 27 ms acc1-10GigE-10-3-0.sf.21cn-ipp.bt.net [109.159.251.97]
9 31 ms 30 ms 27 ms core1-te0-4-0-2.ealing.ukcore.bt.net [109.159.251.1]
10 26 ms 24 ms 25 ms core1-pos1-0-0.telehouse.ukcore.bt.net [62.6.201.82]
11 26 ms 25 ms 25 ms 194.74.65.42
12 27 ms 27 ms 27 ms 212.58.238.153
13 25 ms 26 ms 25 ms rdirslb0.thdo.bbc.co.uk [212.58.224.136]
14 27 ms 26 ms 27 ms virtual3.rbsov.bbc.co.uk [212.58.254.252]

Trace complete.


Still adds around 7ms. This routing is rubbish! 13-14ms to get from the First BT hop (Exchange Router) to the BBC is simply ridiculous!
 
I guess but it shows how messed up these things get around here. I hope this FTTC reaches here soon (Which it probably won't because BT probably class my exchange like most around here - not viable. Maybe that funding for Somerset from the government might help)?
 
Rroff, about your routing - Don't forget that its probably another quarter of the distance on top of that because of the length of the fibres along roads, not just the birds eye distance ;)
 
Hi guys - Update.

The mod I was being helped by was very helpful indeed but as you can probably expect, BT Wholesale didn't do a thing. They claimed the VP at the exchange wasn't being maximised (That's a lie because at peak times, my speed drops like a lead balloon as does other peoples' in the village) and they were not able to find any other problems (Despite me documenting it all and completing failed TAP 1 & 3 tests).

I have been thinking the poor speeds may be related to my exchange being upgraded to 21CN in November but I'm not so sure because the DSLAM I'm on is ATM and not Ethernet (Which the new 21CN equipment is) and therefore, it shouldn't interfere with it.

If there are any more packet-loss problems or silly speed problems, I'll post back ;)
 
Surprise Surprise, BT have done some more changes to my routing for the worse. My ping is now usually 28ms.

I'm currently on a 20CN exchange and it is scheduled to be upgraded to 21CN. When this happens, will the routing be better and quicker because it doesn't have to go from ATM - Ethernet.etc for the route out to the internet (Apart from the connection TO the MSAN)?
 
You must log in or register to reply here.
Back
Top Bottom