BT Infinity & FTTx Discussion
- Thread starter michellez
- Start date
Yep you are crazy, lol but hey if you can afford it, why not?
Just make sure you're not going to move house shortly after. 
For me, I'd probably get a couple of FTTC lines installed and go multi-WAN load-balanced or bonded with pfSense.
150Mb/s download is good enough for me. 
More like £15k installation fee if you're not in an FTTC/FTTP area.
Yay mines finally starting to get back to the speeds just after the Infinity engineer was done
Tho BT's routing is a lol worthy as ever :|
Tho BT's routing is a lol worthy as ever :|
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms local.net [192.168.1.1]
2 6 ms 6 ms 5 ms 217.32.147.106
3 5 ms 6 ms 6 ms 217.32.147.174
4 10 ms 10 ms 10 ms 212.140.206.90
5 9 ms 9 ms 9 ms 217.41.169.209
6 10 ms 10 ms 10 ms 217.41.169.109
7 9 ms 10 ms 9 ms 109.159.251.237
8 23 ms 23 ms 23 ms core2-te-0-13-0-13.ealing.ukcore.bt.net[109.159.251.175]
9 16 ms 19 ms 17 ms peer2-xe3-2-1.telehouse.ukcore.bt.net [109.159.254.225]
10 17 ms 17 ms 17 ms 194.74.65.42
11 * * * Request timed out.
12 17 ms 15 ms 14 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
13 20 ms 19 ms 17 ms 132.185.255.60
14 17 ms 19 ms 17 ms 212.58.241.131
Trace complete.
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms local.net [192.168.1.1]
2 6 ms 6 ms 5 ms 217.32.147.106
3 5 ms 6 ms 6 ms 217.32.147.174
4 10 ms 10 ms 10 ms 212.140.206.90
5 9 ms 9 ms 9 ms 217.41.169.209
6 10 ms 10 ms 10 ms 217.41.169.109
7 9 ms 10 ms 9 ms 109.159.251.237
8 23 ms 23 ms 23 ms core2-te-0-13-0-13.ealing.ukcore.bt.net[109.159.251.175]
9 16 ms 19 ms 17 ms peer2-xe3-2-1.telehouse.ukcore.bt.net [109.159.254.225]
10 17 ms 17 ms 17 ms 194.74.65.42
11 * * * Request timed out.
12 17 ms 15 ms 14 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
13 20 ms 19 ms 17 ms 132.185.255.60
14 17 ms 19 ms 17 ms 212.58.241.131
Trace complete.
You can't see it any more as they've taken to masking the hop since I tried to get it looked at again recently 
but the route is taking a 300 mile detour via sheffield resulting in an extra 10-15ms latency (hop 7->8) - not a huge deal but completely crazy. (I live in Somerset fairly well into the south west).
but the route is taking a 300 mile detour via sheffield resulting in an extra 10-15ms latency (hop 7->8) - not a huge deal but completely crazy. (I live in Somerset fairly well into the south west).Assuming your direct ping to the IP on hop 14 remains at ~17ms, you can all but ignore the 23ms claimed on hop 8 as it's meaningless.
Routers will often show cruddy latencies (or even drop packets as per hop 11) as they will de-prioritise ICMP traffic when passing any sort of load as CPU time is spent routing genuine traffic instead
Routers will often show cruddy latencies (or even drop packets as per hop 11) as they will de-prioritise ICMP traffic when passing any sort of load as CPU time is spent routing genuine traffic instead
Reverse trace shows the hop that no longer shows from my side:
My connection is taking a 300 mile round trip for no good reason other than BT messing up and it is adding to my latency and potentially exposing my connection to faults/traffic around the country for no good reason tho generally BT's core network is good enough thats not a problem.
When I used to route via reading or bletchley park I'd ping bbc.co.uk at 7-8ms.
My connection is taking a 300 mile round trip for no good reason other than BT messing up and it is adding to my latency and potentially exposing my connection to faults/traffic around the country for no good reason tho generally BT's core network is good enough thats not a problem.
When I used to route via reading or bletchley park I'd ping bbc.co.uk at 7-8ms.
Last edited:
Routers will often show cruddy latencies (or even drop packets as per hop 11) as they will de-prioritise ICMP traffic when passing any sort of load as CPU time is spent routing genuine traffic instead
Not always the case, it might just have ping respond turned off. It's very rare that a core network router would drop ICMP traffic.
Last edited:
Pretty happy with this. Had a fault on my line, speed was only running at 25/6ish. Had my line fixed on Wednesday, Openreach around again yesterday as BB went down, then another today as the guy had missed something.
Just left and it's gone from 25/6 as above to this:
Just left and it's gone from 25/6 as above to this:
What is your IP Profile Kol? Use the BT Speed Tester to find out which I assume works for TalkTalk FTTC lines. In my case it lists 68.96/20 Mbps
Also personally I'd recommend Namesco Speed Test I generally find it more accurate for real life usage.
Last Result: Download Speed: 57796 kbps (7224.5 KB/sec ) Upload Speed: 15402 kbps (1925.3 KB/sec )
But in this case they are surprisingly similar.
Also personally I'd recommend Namesco Speed Test I generally find it more accurate for real life usage.
Last Result: Download Speed: 57796 kbps (7224.5 KB/sec ) Upload Speed: 15402 kbps (1925.3 KB/sec )
But in this case they are surprisingly similar.
Last edited:
Soldato
- Joined
- 11 May 2006
- Posts
- 5,786
So would you guys recommend this over VM?
I would go with VM but absolutely hated there traffic management when I was with them a few years ago. I'm currently with bethere internet (who are awesome, no traffic management at all) but a little slow.
I would go with VM but absolutely hated there traffic management when I was with them a few years ago. I'm currently with bethere internet (who are awesome, no traffic management at all) but a little slow.
Yay mines finally starting to get back to the speeds just after the Infinity engineer was done
Tho BT's routing is a lol worthy as ever :|
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms local.net [192.168.1.1]
2 6 ms 6 ms 5 ms 217.32.147.106
3 5 ms 6 ms 6 ms 217.32.147.174
4 10 ms 10 ms 10 ms 212.140.206.90
5 9 ms 9 ms 9 ms 217.41.169.209
6 10 ms 10 ms 10 ms 217.41.169.109
7 9 ms 10 ms 9 ms 109.159.251.237
8 23 ms 23 ms 23 ms core2-te-0-13-0-13.ealing.ukcore.bt.net[109.159.251.175]
9 16 ms 19 ms 17 ms peer2-xe3-2-1.telehouse.ukcore.bt.net [109.159.254.225]
10 17 ms 17 ms 17 ms 194.74.65.42
11 * * * Request timed out.
12 17 ms 15 ms 14 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
13 20 ms 19 ms 17 ms 132.185.255.60
14 17 ms 19 ms 17 ms 212.58.241.131
Trace complete.
your routing and latency look pretty normal. that will get you a 15ms ping if playing games and that is good.
you can always sit there for ages dropping and reconnecting the PPP connection until it gives you a better route
your routing and latency look pretty normal. that will get you a 15ms ping if playing games and that is good.
you can always sit there for ages dropping and reconnecting the PPP connection until it gives you a better route
As I said its not a major issue but it isn't "normal" as such - if it was working properly and routing us directly to London like it used to do it would halve the ping time and reduce the fluctuation a lot - its pretty screwed up in what it does - tho the end result isn't that far from average.
No amount of dropping the PPP connection will get a better route - only (reliable) way to do that would be to change to another ISP and knowing BT will result in a degraded IP profile anyhow.