BT Infinity & FTTx Discussion

BT Infinity peak-time latency to Valve europe is so poor. It's as low as 25ms during the day and 100ms+ during the evening. :(

Code: 
traceroute 208.78.165.232

traceroute to 208.78.165.232 (208.78.165.232), 30 hops max, 60 byte packets
 1  router (192.168.1.254)  0.349 ms  0.388 ms  0.427 ms
 2  172.16.14.135 (172.16.14.135)  8.230 ms  8.308 ms  8.501 ms
3  * * *
 4  217.41.216.29 (217.41.216.29)  27.233 ms  27.249 ms  27.240 ms
 5  213.120.156.194 (213.120.156.194)  14.139 ms  14.316 ms  14.320 ms
 6  217.41.168.191 (217.41.168.191)  12.525 ms  8.341 ms  17.095 ms
 7  217.41.168.109 (217.41.168.109)  17.155 ms  17.099 ms  17.130 ms
 8  109.159.249.196 (109.159.249.196)  18.714 ms acc2-10GigE-0-2-0-4.l-far.21cn-ipp.bt.net (109.159.249.225)  18.534 ms 109.159.249.234 (109.159.249.234)  16.632 ms
 9  109.159.249.131 (109.159.249.131)  17.394 ms core2-te0-7-0-15.faraday.ukcore.bt.net (109.159.249.143)  18.625 ms core-te0-7-0-6.faraday.ukcore.bt.net (109.159.249.147)  18.449 ms
10  peer1-xe0-0-1.faraday.ukcore.bt.net (213.121.193.193)  18.656 ms host213-121-193-165.ukcore.bt.net (213.121.193.165)  17.282 ms  17.258 ms
11  213.137.183.10 (213.137.183.10)  10.827 ms 213.137.183.20 (213.137.183.20)  10.263 ms 213.137.183.6 (213.137.183.6)  8.281 ms
12  t2c1-ge0-0-0.ie-dub2.eu.bt.net (166.49.208.53)  89.890 ms ixp1-xe-0-0-0-0.us-ash.eu.bt.net (166.49.208.77)  92.521 ms ixp1-xe-0-0-1-0.us-ash.eu.bt.net (166.49.208.43)  86.035 ms
13  166-49-151-134.eu.bt.net (166.49.151.134)  84.429 ms  88.850 ms  87.739 ms
14  * * *
15  65.126.30.62 (65.126.30.62)  84.698 ms  95.043 ms  92.957 ms
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * *^C
 
I've noticed this creep in on a couple of connections. Screenshot below is from a connection without any users on it. Slight blip at 3PM was me accidentally using that connection for a brief minute.

7829cd5a35d498a935eab290fc7f1cea-03-07-2014.png


Congestion somewhere in the BT network during the evenings?
 
KIA said:
BT Infinity peak-time latency to Valve europe is so poor. It's as low as 25ms during the day and 100ms+ during the evening. :(

Code: 
traceroute 208.78.165.232

traceroute to 208.78.165.232 (208.78.165.232), 30 hops max, 60 byte packets
 1  router (192.168.1.254)  0.349 ms  0.388 ms  0.427 ms
 2  172.16.14.135 (172.16.14.135)  8.230 ms  8.308 ms  8.501 ms
3  * * *
 4  217.41.216.29 (217.41.216.29)  27.233 ms  27.249 ms  27.240 ms
 5  213.120.156.194 (213.120.156.194)  14.139 ms  14.316 ms  14.320 ms
 6  217.41.168.191 (217.41.168.191)  12.525 ms  8.341 ms  17.095 ms
 7  217.41.168.109 (217.41.168.109)  17.155 ms  17.099 ms  17.130 ms
 8  109.159.249.196 (109.159.249.196)  18.714 ms acc2-10GigE-0-2-0-4.l-far.21cn-ipp.bt.net (109.159.249.225)  18.534 ms 109.159.249.234 (109.159.249.234)  16.632 ms
 9  109.159.249.131 (109.159.249.131)  17.394 ms core2-te0-7-0-15.faraday.ukcore.bt.net (109.159.249.143)  18.625 ms core-te0-7-0-6.faraday.ukcore.bt.net (109.159.249.147)  18.449 ms
10  peer1-xe0-0-1.faraday.ukcore.bt.net (213.121.193.193)  18.656 ms host213-121-193-165.ukcore.bt.net (213.121.193.165)  17.282 ms  17.258 ms
11  213.137.183.10 (213.137.183.10)  10.827 ms 213.137.183.20 (213.137.183.20)  10.263 ms 213.137.183.6 (213.137.183.6)  8.281 ms
12  t2c1-ge0-0-0.ie-dub2.eu.bt.net (166.49.208.53)  89.890 ms ixp1-xe-0-0-0-0.us-ash.eu.bt.net (166.49.208.77)  92.521 ms ixp1-xe-0-0-1-0.us-ash.eu.bt.net (166.49.208.43)  86.035 ms
13  166-49-151-134.eu.bt.net (166.49.151.134)  84.429 ms  88.850 ms  87.739 ms
14  * * *
15  65.126.30.62 (65.126.30.62)  84.698 ms  95.043 ms  92.957 ms
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * *^C
Click to expand...

it looks like that is off to USA not europe! a 90-100ping is quite normal.

Tracing route to 208.78.165.232 over a maximum of 30 hops

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 5 ms 4 ms 4 ms 172.16.15.3
3 * * * Request timed out.
4 6 ms 6 ms 6 ms 213.120.158.157
5 10 ms 10 ms 10 ms 212.140.235.138
6 11 ms 11 ms 11 ms 213.120.180.171
7 11 ms 10 ms 10 ms 217.41.169.109
8 10 ms 10 ms 10 ms acc2-xe-4-2-0.sf.21cn-ipp.bt.net [109.159.251.22
9]
9 23 ms 16 ms 18 ms core1-te-0-4-0-17.ealing.ukcore.bt.net [109.159.
251.57]
10 34 ms 23 ms 18 ms acc1-10GigE-0-5-0-5.l-far.21cn-ipp.bt.net [109.1
59.254.106]
11 19 ms 17 ms 18 ms t2c3-xe-1-1-3-0.uk-lon1.eu.bt.net [166.49.211.18
2]
12 85 ms 83 ms 83 ms ixp1-xe-1-0-0-0.us-nyc.eu.bt.net [166.49.208.41]

13 * * * Request timed out.
14 85 ms 83 ms 84 ms he-1-14-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.87.109]
15 95 ms 100 ms 95 ms he-4-13-0-0-cr01.ashburn.va.ibone.comcast.net [6
8.86.85.97]
16 97 ms 97 ms 99 ms be-17-pe03.350ecermak.il.ibone.comcast.net [68.8
6.82.222]
17 96 ms 96 ms 96 ms as32590-1-c.ashburn.va.ibone.comcast.net [173.16
7.56.170]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 ^C
 
So I've noticed a new green powered cabinet next to my old exisiting cab and Openreach were feeding fibre through over the road the other day.

How soon do you think it would go live?
 
tribz said:
So I've noticed a new green powered cabinet next to my old exisiting cab and Openreach were feeding fibre through over the road the other day.

How soon do you think it would go live?
Click to expand...

Don't be sure that the relative distance means it will serve you.

One green fibre cabinet across the road from me, only 100ft, doesn't serve me. The one that's 1.1 miles away does. Last year I couldn't get anyone to confirm which one I should be watching for until the engineer came out that day to install and activate fibre.

I was checking with samknows and that confirmed I could get it but didn't point the right cabinet number. Find out with BT's checker, and FTTC Check.
 
Is there any way to find out what's going on with a cabinet now that the old NGA email doesn't work?

The FTTC cab for my house has been in place for nigh on a year and a half now and every month or two there are roadworks scheduled for it and 2 other cabinets near it but the switch on never seems to arrive. Every other cabinet around them and even on this side of the whole town have been live since last year and it's getting frustrating.
 
The cabinet for our office has been upgraded, so we ordered FTTC as a backup for our 100Mbps leased line. BT engineer ran this morning to say he would be switching us over. About an hour he rings back to report there isn't a link cable between the NGA cab and the regular cab.

Doh.
 
It's been a while since i posted here last but anyways since the road was closed the other week to install fibre optic lines i was just wondering how long will it be until i can order my BT infinity 76/20. Ive checked the various postcode and phone number fttc checkers and they just say FTTC is not available without even a date set.

Does anyone have a rough estimate on how long they will be? a new cab hasn't popped up yet by the way.
 
I don't think there's any set in stone timescale Pete. If you look at my post above i've been waiting a year and a half since the FTTC cab was installed and still don't have it.
 
Don't use SamKnows for it use the BT one as it updates quicker and the Samknows one tends to go off exchange rather than cabs https://www.dslchecker.bt.com/ just make sure you do it by phone number or address and not postcode.

Even it takes some time to update so don't be disheartened.
 
Another few months down the line and still no sign of fibre.

Not sure why, but when I put my phone number in to the DSL checker it does not recognise it. I'm with Sky so the line is provided by BT. Stick my address in and it comes back with 31st July, which was Nov 2013, then Jan 2014, then May and now July. Odds are good it will be shifted again, I haven't seen any Openreach at what I believe is my cab.
 
You must log in or register to reply here.
Back
Top Bottom