My new FTTP connection

Hi

I got FTTP 900 installed on Thursday

Speedtest at TB are a bit off but I understand there might be issues with the routing (wired connection)

https://www.thinkbroadband.com/speedtest/15957724326...

Using the installed Ookla I get this;

https://www.speedtest.net/my-result/d/6b01a640-701e-...

I have done a tracert to this site and the results are as follows;

Tracing route to thinkbroadband.co.uk [80.249.99.72]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 2 ms 2 ms 3 ms 172.16.18.108
3 17 ms 17 ms 17 ms 31.55.185.177
4 16 ms 16 ms 16 ms 31.55.185.176
5 16 ms 16 ms 15 ms core1-hu0-2-0-1.colindale.ukcore.bt.net [195.99.127.208]
6 18 ms 18 ms 17 ms peer7-et-4-0-1.telehouse.ukcore.bt.net [194.72.16.122]
7 17 ms 16 ms 16 ms linx-gw1.thn.ncuk.net [195.66.224.240]
8 16 ms 16 ms 16 ms te2-3-14.bdr-rt3.thdo.ncuk.net [80.249.97.112]
9 18 ms 18 ms 18 ms po4-31.core-rs4.thdo.ncuk.net [80.249.97.85]
10 16 ms 16 ms 16 ms ip99-72.thdo.ncuk.net [80.249.99.72]

Trace complete.

Does this look like the correct routing? I am in Belfast

I also didnt receive the hub 2 intime and used a TP link C9 archer router that coped with the speeds but found it had developed weak wifi and was pants.

The SH2 arrived and had the dreaded 50Mb upload glitch so when I phoned the must have updated the profile with a firmware update tho the hub as I know get the proper upload.

Overall I am so pleased as I was stuck before with approx 16Mb down and 1 Mb up!

Edited by deleted (Sun 26-Jul-20 15:20:03)

In reply to a post by NuttyMucker:

Hi

I got FTTP 900 installed on Thursday

Speedtest at TB are a bit off but I understand there might be issues with the routing (wired connection)

https://www.thinkbroadband.com/speedtest/15957724326...

Using the installed Ookla I get this;

https://www.speedtest.net/my-result/d/6b01a640-701e-...

I have done a tracert to this site and the results are as follows;

Tracing route to thinkbroadband.co.uk [80.249.99.72]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 2 ms 2 ms 3 ms 172.16.18.108
3 17 ms 17 ms 17 ms 31.55.185.177
4 16 ms 16 ms 16 ms 31.55.185.176
5 16 ms 16 ms 15 ms core1-hu0-2-0-1.colindale.ukcore.bt.net [195.99.127.208]
6 18 ms 18 ms 17 ms peer7-et-4-0-1.telehouse.ukcore.bt.net [194.72.16.122]
7 17 ms 16 ms 16 ms linx-gw1.thn.ncuk.net [195.66.224.240]
8 16 ms 16 ms 16 ms te2-3-14.bdr-rt3.thdo.ncuk.net [80.249.97.112]
9 18 ms 18 ms 18 ms po4-31.core-rs4.thdo.ncuk.net [80.249.97.85]
10 16 ms 16 ms 16 ms ip99-72.thdo.ncuk.net [80.249.99.72]

Trace complete.

Does this look like the correct routing? I am in Belfast

I also didnt receive the hub 2 intime and used a TP link C9 archer router that coped with the speeds but found it had developed weak wifi and was pants.

The SH2 arrived and had the dreaded 50Mb upload glitch so when I phoned the must have updated the profile with a firmware update tho the hub as I know get the proper upload.

Overall I am so pleased as I was stuck before with approx 16Mb down and 1 Mb up!

Yeah that's correct routing, all UK based ISP's will route you down to London where their BNG's are which is what those 2 31 IP's are. I'm in Scotland on FTTP and hit the exact same ones so you're going the right way.

In reply to a post by max1486:

Yeah that's correct routing, all UK based ISP's will route you down to London where their BNG's are which is what those 2 31 IP's are. I'm in Scotland on FTTP and hit the exact same ones so you're going the right way.

Well doing a Trace Route to the TBB Host it has to go down to London due to the TBB Hosting is located there.

Just like their BQM Service is also located there too, I use to ping that server when I was seeing strange patterns on the BQM.

I think the OP needs to do an IPv4 TBB Speedtest and then right after redo a trace route to the server that was used for the speed test, that way they "should" follow the same route.

Try using something like tracert -4 SERVER_USED
The -4 argument forces it to use IPv4 just in case it tries to use IPv6.

But the pings in the OP Trace Route results seem fine to me going by their location all the way down to London.

But not too sure what is up with the speeds, maybe the routes that its taking is under load, but I would of thought the traceroute would of shown that due to pings are lower on the importance table compared to data traffic.

Paul

I have just completed as what suggested and here are the results. Possibly not the best time to try but will try an early morning one later in the week;

https://www.thinkbroadband.com/_assets/speedtest/but...

Ookla test using a London based server

https://www.speedtest.net/my-result/d/b68aeba7-7c01-...

and here are my tracert results;

C:\WINDOWS\system32>tracert -4 speedtest7.thinkbroadband.com

Tracing route to speedtest7.thinkbroadband.com [80.249.106.133]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 2 ms 1 ms 1 ms 172.16.18.108
3 17 ms 17 ms 17 ms 31.55.185.181
4 16 ms 16 ms 16 ms 31.55.185.188
5 17 ms 16 ms 16 ms core1-hu0-2-0-3.colindale.ukcore.bt.net [195.99.127.210]
6 18 ms 19 ms 18 ms peer7-et-4-1-1.telehouse.ukcore.bt.net [194.72.16.134]
7 16 ms 16 ms 16 ms linx-gw1.thn.ncuk.net [195.66.224.240]
8 16 ms 16 ms 16 ms te2-3-14.bdr-rt3.thdo.ncuk.net [80.249.97.112]
9 20 ms 19 ms 18 ms po4-31.core-rs4.thdo.ncuk.net [80.249.97.85]
10 17 ms 16 ms 17 ms speedtest7.thinkbroadband.com [80.249.106.133]

Trace complete.

In reply to a post by PaulKirby:

In reply to a post by max1486:

Yeah that's correct routing, all UK based ISP's will route you down to London where their BNG's are which is what those 2 31 IP's are. I'm in Scotland on FTTP and hit the exact same ones so you're going the right way.

Well doing a Trace Route to the TBB Host it has to go down to London due to the TBB Hosting is located there.

Just like their BQM Service is also located there too, I use to ping that server when I was seeing strange patterns on the BQM.

I think the OP needs to do an IPv4 TBB Speedtest and then right after redo a trace route to the server that was used for the speed test, that way they "should" follow the same route.

Try using something like tracert -4 SERVER_USED
The -4 argument forces it to use IPv4 just in case it tries to use IPv6.

But the pings in the OP Trace Route results seem fine to me going by their location all the way down to London.

But not too sure what is up with the speeds, maybe the routes that its taking is under load, but I would of thought the traceroute would of shown that due to pings are lower on the importance table compared to data traffic.

Paul

Edited by deleted (Tue 28-Jul-20 23:06:23)