Fibre help

Just wondering if anyone can point us in the right direction, Plusnet have been good at trying to sort this issue, but any help appreciated.

We had fibre installed in July and we got 38MB, and then when the 80/20 trial was available we got up to around 46MB.

I think our problem started when Plusnet changed the packages and made the 80/20 a permanent product, since then our service has been going downhill.

The speed seems to be fluctuating, from 45MB, down to 5.5MB on Plusnets own speed tester, we have had BT out numerous times, they seem to be picking up numerous minor niggling faults, cables in water in the cabinet, slight interference, but nothing major that they have told us about.

BT where out yesterday, he looked at the copper wire on the pole, do not know if he changed it, but he may have done, made some phone calls, and was told by his end that the best we could get was 25MB, this was based on us being 600mtrs from the cabinet, the BTW system says we should get 44MB, and we have had and held 44MB before.

When he left, we where synced at 42MB, now the strange thing is we always are, but hours after they leave our profile at BT always changes to 31.36MB, and today has been a nightmare, webpages taking several minutes to load, and our download has averaged around 13MB, we have had the router changed and two different Openreach modems, but all to no avail, this has been going on now for around five weeks.

I am at my wits end, and the only thing I can link it to is when Plusnet changed there tariffs, anyone any ideas what we could try?

Lisa

Plusnet Speed checks


Today 23:13 12354 kbps (1.54MB/s) 1646 kbps (206kB/s) Share
Today 22:47 11712 kbps (1.46MB/s) 582 kbps (72.8kB/s) Share
Today 21:59 5586 kbps (698kB/s) 810 kbps (101kB/s) Share
Today 21:59 6159 kbps (770kB/s) 539 kbps (67.4kB/s) Share
Today 08:55 13048 kbps (1.63MB/s) 612 kbps (76.5kB/s) Share
Today 08:15 11443 kbps (1.43MB/s) 1769 kbps (221kB/s) Share
Today 08:09 13464 kbps (1.68MB/s) 772 kbps (96.5kB/s) Share
Today 08:06 13224 kbps (1.65MB/s) 1745 kbps (218kB/s) Share
Today 08:04 13260 kbps (1.66MB/s) 1767 kbps (221kB/s) Share
Today 07:53 13525 kbps (1.69MB/s) 1762 kbps (220kB/s) Share
Today 07:49 13281 kbps (1.66MB/s) 604 kbps (75.5kB/s) Share
Yesterday 19:41 14680 kbps (1.84MB/s) 2480 kbps (310kB/s) Share
Yesterday 19:37 16801 kbps (2.1MB/s) 2287 kbps (286kB/s) Share
Yesterday 19:32 16865 kbps (2.11MB/s) 600 kbps (75kB/s) Share
Yesterday 09:03 28535 kbps (3.57MB/s) 8339 kbps (1.04MB/s) Share
Sunday 20:06 30095 kbps (3.76MB/s) 7375 kbps (922kB/s) Share
Saturday 17:38 28866 kbps (3.61MB/s) 7201 kbps (900kB/s) Share
Friday 18:32 28094 kbps (3.51MB/s) 8219 kbps (1.03MB/s) Share
Friday 18:16 36002 kbps (4.5MB/s) 1203 kbps (150kB/s) Share
Sep 17, 16:17 27399 kbps (3.42MB/s) 7648 kbps (956kB/s) Share
Sep 10, 14:23 37166 kbps (4.65MB/s) 5870 kbps (734kB/s) Share
Sep 9, 18:35 11276 kbps (1.41MB/s) 8473 kbps (1.06MB/s) Share
Sep 9, 00:20 40939 kbps (5.12MB/s) 8450 kbps (1.06MB/s) Share
Sep 8, 18:49 40949 kbps (5.12MB/s) 8109 kbps (1.01MB/s) Share
Sep 8, 18:10 37689 kbps (4.71MB/s) 8033 kbps (1MB/s) Share
Sep 7, 11:42 34114 kbps (4.26MB/s) 8909 kbps (1.11MB/s) Share
Sep 7, 11:29 37762 kbps (4.72MB/s) 8892 kbps (1.11MB/s) Share
Aug 31, 23:54 33574 kbps (4.2MB/s) 7668 kbps (959kB/s) Share
Aug 31, 13:44 36775 kbps (4.6MB/s) 7665 kbps (958kB/s) Share
Aug 31, 12:40 37375 kbps (4.67MB/s) 7697 kbps (962kB/s) Share

Speed tests on their own can't be relied upon as so many factors can affect them.

BT's IP Profile can't be 100% relied upon either as it only changes when a new PPP session is initiated, so can end up being stuck at either too high or too low a level.

You really need to unlock, or obtain a spare modem & unlock it to be able to see your connection stats & also identify exactly how often the connection resyncs (possibly detecting a time of day/weather changes pattern).

Plusnet's own logs don't always pick up on how often a connection resyncs as many of the "on the fly" resyncs are too quick to be detected & they don't force a new PPP session.

DLM sees them though & clobbers your connection speeds in response.

If, & only if, your connection is genuinely stable with lowish error counts can you push this back as a potential routing, capacity or profiling problem.

I suspect though that your connection is exhibiting the symptoms of an intermittent fault that is not detected via various BT line tests, or it could simply be that Plusnet's line profile needs adjusting.

What is your current line speed as reported by Plusnet, & have they detected many disconnections?

I experienced the intermittent faults issues & it took 11 months to resolve (once we eventually got over the hurdle of both Plusnet & BT claiming my connection was physically perfect & was "performing within acceptable limits").

mybroadbandspeed is the most unreliable tester there is - especially for those on fibre!

In reply to a post by jelv:

mybroadbandspeed is the most unreliable tester there is - especially for those on fibre!

BT speedtester

Download speedachieved during the test was - 18.61 Mbps
For your connection, the acceptable range of speedsis 12 Mbps-31.36 Mbps .
Additional Information:
IP Profile for your line is - 31.36 Mbps

Web browsing is still nearly non existent, Plusnet still waiting for the fault report of BT

Look at my Speedtest below, that is what it should be like

L

In reply to a post by lisaj:

In reply to a post by jelv:

mybroadbandspeed is the most unreliable tester there is - especially for those on fibre!

BT speedtester

Download speedachieved during the test was - 18.61 Mbps
For your connection, the acceptable range of speedsis 12 Mbps-31.36 Mbps .
Additional Information:
IP Profile for your line is - 31.36 Mbps

Web browsing is still nearly non existent, Plusnet still waiting for the fault report of BT

Look at my Speedtest below, that is what it should be like

L

The BT test was done connected with a short cable to the TEST socket?

(edit, just noticed the poor speed logs.)

Edited by Apprentice (Wed 26-Sep-12 18:57:18)

In reply to a post by Apprentice:

In reply to a post by lisaj:

In reply to a post by jelv:

mybroadbandspeed is the most unreliable tester there is - especially for those on fibre!

BT speedtester

Download speedachieved during the test was - 18.61 Mbps
For your connection, the acceptable range of speedsis 12 Mbps-31.36 Mbps .
Additional Information:
IP Profile for your line is - 31.36 Mbps

Web browsing is still nearly non existent, Plusnet still waiting for the fault report of BT

Look at my Speedtest below, that is what it should be like

L

The BT test was done connected with a short cable to the TEST socket?

(edit, just noticed the poor speed logs.)

We have the brand new BT socket, installed a few weeks ago, the speed is all over the place all day long, constantly around 13MB on speedtest.net and even lower using the BT over 24MB beta test.

My main concern is web browsing is dam near impossible, websites are taking over a minute to load in some circumstances, others are just really lagging, Plusnet bless them have just quoted us the SLA as BT have still not reported on the problem, the kids at the moment trying to do there homework is a nightmare with the browsing speed.

The tests are being done with a short Ethernet cable to the router

Latest Namesco (BBMAX) speedtest

Download Speed: 9535 kbps (1191.9 KB/sec ) Upload Speed: 1694 kbps (211.8 KB/sec )
L

Edited by deleted (Wed 26-Sep-12 19:10:23)

Web browsing should not be impossible with an 18Meg throughput.

Have you tried tools like ping to see what packet loss is like?

ping -t www.plus.net in a command window and what do you see?

In reply to a post by MrSaffron:

Web browsing should not be impossible with an 18Meg throughput.

Have you tried tools like ping to see what packet loss is like?

ping -t www.plus.net in a command window and what do you see?

Constant 19/20 milliseconds

Lisa

In reply to a post by MrSaffron:

Web browsing should not be impossible with an 18Meg throughput.

Have you tried tools like ping to see what packet loss is like?

ping -t www.plus.net in a command window and what do you see?

tracert to BBC

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.90]
over a maximum of 30 hops:

1 112 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 14 ms 13 ms 14 ms lo0-central10.pcl-ag02.plus.net [195.166.128.183
]
3 13 ms 12 ms 19 ms link10-central10.pcl-gw02.plus.net [84.93.249.50
]
4 13 ms 13 ms 12 ms xe-0-2-0.pcl-cr02.plus.net [212.159.1.2]
5 13 ms 14 ms 13 ms ae1.ptw-cr02.plus.net [195.166.129.2]
6 13 ms 13 ms 12 ms ae2.ptw-cr01.plus.net [195.166.129.4]
7 13 ms 13 ms 13 ms kingston-gw.thdo.bbc.co.uk [212.58.239.6]
8 * * * Request timed out.
9 14 ms 14 ms 15 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
10 17 ms 17 ms 14 ms 132.185.255.165
11 14 ms 13 ms 14 ms bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]

Trace complete.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

tracert www.evertonfc.com

Tracing route to rb-efc-main-200663015.eu-west-1.elb.amazonaws.com [54.247.174.1
84]
over a maximum of 30 hops:

1 132 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 16 ms 17 ms 13 ms lo0-central10.pcl-ag02.plus.net [195.166.128.183
]
3 13 ms 13 ms 13 ms link8-central10.pcl-gw02.plus.net [84.93.249.46]

4 13 ms 13 ms 12 ms xe-0-2-0.pcl-cr02.plus.net [212.159.1.2]
5 13 ms 12 ms 13 ms ae2.pcl-cr01.plus.net [195.166.129.6]
6 13 ms 12 ms 13 ms xe-11-2-0.edge3.London2.Level3.net [212.187.201.
213]
7 19 ms 13 ms 16 ms ae-0-11.edge4.London2.Level3.net [4.69.200.126]

8 13 ms 13 ms 13 ms ae-3-3.ebr1.London1.Level3.net [4.69.141.189]
9 36 ms 24 ms 24 ms ae-1-8.bar1.Dublin1.Level3.net [4.69.153.230]
10 25 ms 24 ms 24 ms 213.242.106.86
11 26 ms 25 ms 25 ms 178.236.0.128
12 25 ms 26 ms 26 ms 178.236.0.125
13 27 ms 28 ms 36 ms ec2-79-125-0-132.eu-west-1.compute.amazonaws.com
[79.125.0.132]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

ping -t www.evertonfc.com

Pinging rb-efc-main-200663015.eu-west-1.elb.amazonaws.com [46.137.177.216] with
32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

>ping -t www.aol.co.uk

Pinging portal.aol.eu.aol.akadns.net [205.188.18.209] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

>ping -t www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.246.94] with 32 bytes of data:
Reply from 212.58.246.94: bytes=32 time=30ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=13ms TTL=54
Reply from 212.58.246.94: bytes=32 time=13ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54

Edited by deleted (Wed 26-Sep-12 22:54:59)

In reply to a post by lisaj:

1 112 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]

Takes a long time to get a response from the 1st hop.