Yeah, hopefully next month there will be some noticeable progress. I'm eager to see how the other altnet provider does within the next few years as that could be another option in the future and potentially a better one too.

Regarding the router, most likely the FireBrick FB2900. I have an EdgeRouter 8 Pro too but that's not in use and is primarily a backup option if the FB2900 should for some reason fail.

Hey all.

Finally got my order completed this morning.
All testing fine although I'm thinking my latency is a little high at 18ms from my desktop

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



I'm using an a ubiquiti AmplifiHD as my router and using the inbuilt speed tester, I'm getting 12ms consistantly which is a little better.

Anything to be concerned about? I saw a few of you guys getting 4-6ms

Edited by deleted (Mon 01-Apr-19 16:21:53)

Hi

The single thread download speed is quite a bit lower than the x6, this usually indicates congestion, this means your connection is a bit like a FTTC 40/20 service. Try speedtest.net and pick the "Single" speed test option just to rule out congestion between you and Thinkbroadband, what does this test at?

Regards

Phil

Thanks, just tested with speedtest.net and the single thread test is better at approx 113Mbps.
Ping is steady at 12ms.

Trace route to BBC is 11ms for the 2nd hop to Cerberus

Edited by deleted (Mon 01-Apr-19 16:37:41)

In reply to a post by 1nfern0:

I saw a few of you guys getting 4-6ms

Depends on how far away you are from London, where your ISP's POP is likely to be, as is whatever it is you're pinging.

Light in a fibre optic travels at about 200,000 km/s. So every 100km further away you are adds another 1ms to the round-trip time.

Fairpoint, I'm in Durham so could add 4ms
So this looks fairly reasonable to bbc.co.uk

1 <1 ms 1 ms 1 ms amplifi.lan []
2 13 ms 11 ms 11 ms lo-3-thn-lns07.cerberus.net.uk
3 12 ms 11 ms 13 ms 46-37-35-130.dsl.cnl.uk.net
4 11 ms 11 ms 12 ms ip81-59.fastly-gw1.lonap.net
5 13 ms 12 ms 11 ms

I am in London which is why I get a low 3ms ping. My single threaded speed test is the same as my x6 test so not sure why yours would be so low.

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

Edited by brookheather (Mon 01-Apr-19 17:30:45)

In reply to a post by candlerb:

In reply to a post by 1nfern0:

I saw a few of you guys getting 4-6ms

Depends on how far away you are from London, where your ISP's POP is likely to be, as is whatever it is you're pinging.

Light in a fibre optic travels at about 200,000 km/s. So every 100km further away you are adds another 1ms to the round-trip time.

I am on FTTP and about 3.5 miles (bird's-eye view) from Telehouse and I get the following:

Traceroute

tracert -4 bbc.co.uk

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

  1    <1 ms    <1 ms    <1 ms  Yazoo [192.168.2.253]
  2     1 ms     1 ms     1 ms  172.16.10.194
  3     2 ms     2 ms     2 ms  31.55.186.181
  4     3 ms     2 ms     2 ms  31.55.186.188
  5     3 ms     2 ms     2 ms  host213-121-192-68.ukcore.bt.net [213.121.192.68]
  6     2 ms     2 ms     2 ms  peer7-et-4-0-3.telehouse.ukcore.bt.net [194.72.16.126]
  7     3 ms     3 ms     3 ms  peer5-te0-9-0-32.telehouse.ukcore.bt.net [195.99.126.81]
  8     2 ms     3 ms     2 ms  151.101.0.81

Trace complete.

Ping

ping -4 bbc.co.uk

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=2ms TTL=57
Reply from 151.101.0.81: bytes=32 time=2ms TTL=57
Reply from 151.101.0.81: bytes=32 time=2ms TTL=57
Reply from 151.101.0.81: bytes=32 time=3ms TTL=57

Ping statistics for 151.101.0.81:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 3ms, Average = 2ms

Both traceroutes and pings fluctuate by +- 1 to 2 ms, but mostly the above.

Paul

Edited by PaulKirby (Mon 01-Apr-19 17:33:23)

The one-year anniversary of my order has been and gone, with little sign of immediate progress. After being told that some new ducting was needed, it now seems Openreach are going to instead try again at squeezing the cabling through the existing duct. The snag is that the council will only let any digging / traffic control works take place during half-terms, meaning that the chance of it being done during the Easter holidays is now receding - meaning May or even July is now increasingly likely.

It's not Cerberus' fault, of course, but after a flurry of activity several months ago by the overhead cabling teams, the whole process now seems to have slowed down markedly.

Ouch, that's worse than my situation recently for sure. That's unfortunate. Hopefully something will happen soon.

I've just had a fleet of Openreach vans turn up around the back of the house where the DP is, they appear to be going over the various cables and equipment. Initially there were four vans, there's still one here currently and they appear to be busy working on the pole and in the underground cable chamber.