BT Infinity & FTTx Discussion

Uhtred · 9 Oct 2012 at 18:18

I'm out as well but here's my live graph. Looks ok so far

randal · 9 Oct 2012 at 18:34

Code:

--- battlefield.com ping statistics ---
52 packets transmitted, 52 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 124.805/138.179/229.288/29.355 ms

traceroute to battlefield.com (72.32.103.134), 64 hops max, 52 byte packets
1 api (192.168.100.1) 1.556 ms 1.534 ms 1.411 ms
2 217.32.147.100 (217.32.147.100) 6.849 ms 7.393 ms 7.702 ms
3 217.32.147.126 (217.32.147.126) 22.648 ms 7.370 ms 7.157 ms
4 213.120.181.182 (213.120.181.182) 12.701 ms 12.420 ms 12.716 ms
5 217.41.169.251 (217.41.169.251) 13.786 ms 12.545 ms 12.953 ms
6 217.41.169.109 (217.41.169.109) 12.515 ms 12.531 ms 12.716 ms
7 109.159.251.213 (109.159.251.213) 12.080 ms
109.159.251.249 (109.159.251.249) 12.991 ms 12.397 ms
8 core1-te0-5-0-7.ilford.ukcore.bt.net (109.159.251.149) 26.218 ms
core1-te0-0-0-4.ilford.ukcore.bt.net (109.159.251.153) 25.019 ms
core2-te0-13-0-2.ealing.ukcore.bt.net (109.159.251.139) 31.858 ms
9 peer1-xe4-0-1.redbus.ukcore.bt.net (109.159.255.122) 20.154 ms 20.496 ms 20.458 ms
10 ge-2-1-0.mpr1.lhr2.uk.above.net (195.66.224.76) 23.414 ms 23.177 ms 23.188 ms
11 ge-7-0-0.mpr1.lhr2.uk.above.net (64.125.28.25) 19.797 ms 22.178 ms 20.942 ms
12 xe-5-2-0.cr1.dca2.us.above.net (64.125.26.21) 93.037 ms 105.611 ms 93.976 ms
13 xe-0-2-0.cr1.iah1.us.above.net (64.125.25.114) 125.929 ms 125.635 ms 125.285 ms
14 xe-2-1-0.cr1.dfw2.us.above.net (64.125.30.58) 123.593 ms 124.966 ms 124.788 ms
15 xe-8-2-1.er1.dfw2.us.above.net (64.125.30.85) 124.480 ms 122.262 ms 124.418 ms
16 main1.above.net (209.133.126.42) 126.634 ms 126.698 ms 126.660 ms
17 coreb.dfw1.rackspace.net (74.205.108.40) 124.803 ms
corea.dfw1.rackspace.net (74.205.108.38) 127.483 ms
coreb.dfw1.rackspace.net (74.205.108.40) 127.714 ms
18 core7.dfw1.rackspace.net (74.205.108.15) 127.384 ms
core7.dfw1.rackspace.net (74.205.108.31) 126.802 ms 127.401 ms
19 aggr502a-2-core7.dfw1.rackspace.net (98.129.84.23) 129.485 ms 128.982 ms 128.314 ms
<snip>

Happy days.

kmufc77 · 9 Oct 2012 at 18:43

Hello All,
I work at BT and look after Network Architecture. We are aware of this issue and we have made some changes today, however the upstream has a significant congestion issue in their network (today we don't even reach 60% of our available capacity to the LINX, which is the place where ISP's in the UK exchange traffic).

We have changed our network to directly exchange traffic with rackspace (who host some EA sites) and we have re-routed a number of internet sites via other paths. We have raised this congestion issue with third party.

Regards,
Neil McRae
Network Architecture.

randal · 9 Oct 2012 at 18:44

Nice touch getting an email from someone who knows what they're talking about.

.Griff. · 9 Oct 2012 at 18:46

kmufc77 said:
Hello All,
I work at BT and look after Network Architecture. We are aware of this issue and we have made some changes today, however the upstream has a significant congestion issue in their network (today we don't even reach 60% of our available capacity to the LINX, which is the place where ISP's in the UK exchange traffic).

We have changed our network to directly exchange traffic with rackspace (who host some EA sites) and we have re-routed a number of internet sites via other paths. We have raised this congestion issue with third party.

Regards,
Neil McRae
Network Architecture.

I spotted that and commented..

"However it's concerning and certainly says a lot for BT that their Chief Network Architect has to create an account on a community forum to let us all know what's happening when the BT has had days to update it's status page and/or let us know what the issue was"

That's even assuming it's really the correct Neil McRae and not some troll that's got his details from LinkedIn.

Mana · 9 Oct 2012 at 18:50

lets see what happens around 11pm tonight!

borley · 9 Oct 2012 at 19:41

.Griff. said:
I spotted that and commented..

"However it's concerning and certainly says a lot for BT that their Chief Network Architect has to create an account on a community forum to let us all know what's happening when the BT has had days to update it's status page and/or let us know what the issue was"

That's even assuming it's really the correct Neil McRae and not some troll that's got his details from LinkedIn.

Lol he has over 4,700 posts I don't think he just joined to post about this complaint

kmufc77 · 9 Oct 2012 at 19:48

Not saying its fixed, but tonight is the first night in a while i can access these forums properly and other sites, hows everyone else tonight?

.Griff. · 9 Oct 2012 at 19:53

borley said:
Lol he has over 4,700 posts I don't think he just joined to post about this complaint

"Registered 09-10-2012"

"Posts 2"

MajorPacketLoss-Page22-BTCareCommunityForums_zps5470c964.png

reflux · 9 Oct 2012 at 20:01

Orcvader said:
Last night a lot of websites were loading very slow including the OcUK site. Did a speed test and my speeds and latency was normal. I couldn't even load the BT service status page!

This morning it seems normal now...

I had exactly the same. We got our Infinity installed on the weekend and last night it was pants. Basically a 5mb connection and OCUK kept failing to load.

Tonight however, I'm download Dishonored from Steam @ 8mb/s and it's going to take 10 mins... LUDICROUS SPEED!! Can't believe how fast it is.

Westyfield2 · 9 Oct 2012 at 20:29

Fixed

Hmm, too soon to declare it as fixed?

kmufc77 · 9 Oct 2012 at 20:30

Yeah, ive noticed the forums here are taking a while to refresh/ load again.

Nowhere near as bad as last few nights though.

randal · 9 Oct 2012 at 20:36

randal24 said:
Code:

--- battlefield.com ping statistics --- 52 packets transmitted, 52 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 124.805/138.179/229.288/29.355 ms

traceroute to battlefield.com (72.32.103.134), 64 hops max, 52 byte packets
1 api (192.168.100.1) 1.556 ms 1.534 ms 1.411 ms
2 217.32.147.100 (217.32.147.100) 6.849 ms 7.393 ms 7.702 ms
3 217.32.147.126 (217.32.147.126) 22.648 ms 7.370 ms 7.157 ms
4 213.120.181.182 (213.120.181.182) 12.701 ms 12.420 ms 12.716 ms
5 217.41.169.251 (217.41.169.251) 13.786 ms 12.545 ms 12.953 ms
6 217.41.169.109 (217.41.169.109) 12.515 ms 12.531 ms 12.716 ms
7 109.159.251.213 (109.159.251.213) 12.080 ms
109.159.251.249 (109.159.251.249) 12.991 ms 12.397 ms
8 core1-te0-5-0-7.ilford.ukcore.bt.net (109.159.251.149) 26.218 ms
core1-te0-0-0-4.ilford.ukcore.bt.net (109.159.251.153) 25.019 ms
core2-te0-13-0-2.ealing.ukcore.bt.net (109.159.251.139) 31.858 ms
9 peer1-xe4-0-1.redbus.ukcore.bt.net (109.159.255.122) 20.154 ms 20.496 ms 20.458 ms
10 ge-2-1-0.mpr1.lhr2.uk.above.net (195.66.224.76) 23.414 ms 23.177 ms 23.188 ms
11 ge-7-0-0.mpr1.lhr2.uk.above.net (64.125.28.25) 19.797 ms 22.178 ms 20.942 ms
12 xe-5-2-0.cr1.dca2.us.above.net (64.125.26.21) 93.037 ms 105.611 ms 93.976 ms
13 xe-0-2-0.cr1.iah1.us.above.net (64.125.25.114) 125.929 ms 125.635 ms 125.285 ms
14 xe-2-1-0.cr1.dfw2.us.above.net (64.125.30.58) 123.593 ms 124.966 ms 124.788 ms
15 xe-8-2-1.er1.dfw2.us.above.net (64.125.30.85) 124.480 ms 122.262 ms 124.418 ms
16 main1.above.net (209.133.126.42) 126.634 ms 126.698 ms 126.660 ms
17 coreb.dfw1.rackspace.net (74.205.108.40) 124.803 ms
corea.dfw1.rackspace.net (74.205.108.38) 127.483 ms
coreb.dfw1.rackspace.net (74.205.108.40) 127.714 ms
18 core7.dfw1.rackspace.net (74.205.108.15) 127.384 ms
core7.dfw1.rackspace.net (74.205.108.31) 126.802 ms 127.401 ms
19 aggr502a-2-core7.dfw1.rackspace.net (98.129.84.23) 129.485 ms 128.982 ms 128.314 ms
<snip>

Happy days.

Route has changed slightly again.

raceroute to battlefield.com (72.32.103.134), 64 hops max, 52 byte packets
1 api (192.168.100.1) 5.330 ms 2.181 ms 1.789 ms
2 217.32.147.100 (217.32.147.100) 7.146 ms 7.083 ms 6.901 ms
3 217.32.147.126 (217.32.147.126) 7.253 ms 35.116 ms 8.008 ms
4 213.120.181.182 (213.120.181.182) 12.480 ms 12.526 ms 12.369 ms
5 217.41.169.251 (217.41.169.251) 12.782 ms 12.381 ms 12.311 ms
6 217.41.169.109 (217.41.169.109) 12.526 ms 12.796 ms 12.671 ms
7 109.159.251.197 (109.159.251.197) 12.462 ms
109.159.251.195 (109.159.251.195) 12.387 ms
109.159.251.193 (109.159.251.193) 12.181 ms
8 core1-te0-5-0-7.ilford.ukcore.bt.net (109.159.251.149) 21.152 ms
core2-te0-4-0-2.ealing.ukcore.bt.net (109.159.251.131) 26.569 ms
core2-te0-2-3-0.ealing.ukcore.bt.net (109.159.251.147) 28.019 ms
9 peer1-xe4-0-1.redbus.ukcore.bt.net (109.159.255.122) 20.729 ms 52.224 ms 20.657 ms
10 ge-2-1-0.mpr1.lhr2.uk.above.net (195.66.224.76) 22.666 ms 23.206 ms 23.203 ms
11 ge-6-0-0.mpr1.lhr2.uk.above.net (64.125.24.221) 18.553 ms 23.196 ms 18.848 ms
12 xe-5-2-0.cr1.dca2.us.above.net (64.125.26.21) 91.153 ms 93.444 ms 121.448 ms
13 xe-0-2-0.cr1.iah1.us.above.net (64.125.25.114) 126.228 ms 125.724 ms 125.338 ms
14 xe-1-2-0.cr1.dfw2.us.above.net (64.125.26.129) 125.572 ms 124.086 ms 126.310 ms
15 xe-8-2-1.er1.dfw2.us.above.net (64.125.30.85) 154.552 ms 123.512 ms 124.507 ms
16 main1.above.net (209.133.126.42) 126.581 ms 124.480 ms 124.425 ms
17 coreb.dfw1.rackspace.net (74.205.108.40) 125.230 ms
corea.dfw1.rackspace.net (74.205.108.38) 128.559 ms
coreb.dfw1.rackspace.net (74.205.108.40) 127.933 ms
18 core7.dfw1.rackspace.net (74.205.108.15) 128.332 ms
core7.dfw1.rackspace.net (74.205.108.31) 127.245 ms 124.949 ms
19 aggr502a-2-core7.dfw1.rackspace.net (98.129.84.23) 128.112 ms 127.146 ms 129.142 ms
<snip>

Unless that's a load balanced router or something. Naming convention implies it's close, so probably is thinking about it.

Either way, the numbers are better now.

Code:

52 packets transmitted, 52 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 124.661/129.463/203.441/10.499 ms

borley · 9 Oct 2012 at 21:58

.Griff. said:
"Registered 09-10-2012"

"Posts 2"

Sorry didnt relise the other person was qouting i thought he was the originla poster!

Mana · 9 Oct 2012 at 22:57

ah seems much better tonight woop

Vanhishikha · 10 Oct 2012 at 04:36

Would these packet losses cause loss of connection while using Wi-Fi? At random times (usually later at night), my connection will just drop out and re-connect after a few minutes.

Is this because of the packet loss, or do I have some dodgy hardware?

- Dan.

ChrisD. · 10 Oct 2012 at 06:59

Vanhishikha said:
Would these packet losses cause loss of connection while using Wi-Fi? At random times (usually later at night), my connection will just drop out and re-connect after a few minutes.

Is this because of the packet loss, or do I have some dodgy hardware?

- Dan.

Packet loss within BT's network and your home wifi are two separate things.

Vanhishikha · 10 Oct 2012 at 14:05

MilanoChris said:
Packet loss within BT's network and your home wifi are two separate things.

Hm, I'll give it a week because it's a brand new installation & if it persists, I'll give BT a ring, thank you.

DirtyJester · 10 Oct 2012 at 14:42

So going by the posts, last night was an improvement then?

Working again tonight so I'll be checking in again tomorrow.

ChrisD. · 10 Oct 2012 at 14:43

Yes, much better.