Next Doors PN Fibre is over 11mb faster than mine

[#1]

When I joined plusnet fibre a few years back I was told that my Estimated speed would be around 40mbs which I have never got over the years the speed has been decreasing and is now at 23.24mbs,

I have had Openreach out to check the line and said they had tried different things but basically said in the end they would not waste any more money on trying to improve my speed.

My next door neighbour signed up to PlusNet Fibre in November 2016 and his line runs next to mine to the same pole across the road which connects to the same cabinet, but his line is syncing at 34.47 Mbps, which is over 11mbs faster than mine.

Considering our cables connect to the same pole their must be some problem with my line, can anyone shed some light on what would cause such a speed difference in two lines which run to the same pole.

Got these details for both our lines from Mouselike.org 

Mine
The current Downstream BRAS rate is: 23.24 Mbps
The current Upstream BRAS rate is: 10 Mbps

Neighbours
The current Downstream BRAS rate is: 34.47 Mbps
The current Upstream BRAS rate is: 2 Mbps

Plusnets website (https://portal.plus.net/my.html?action=data_transfer_speed) tells me the following which is obviously wrong

Estimated line speed: There's no speed estimate currently held on your account.
Current line speed:78 Mb 

[#2]

What are the router stats for both lines?

[#3]

Attached is a screenshot of my modem stats and my neighbours router stats

[#4]

This is a bit of a guess but your problem appears to be the very high HEC count causing the system to either band the line or increase the noise margin (banding seems more likely)

Have you tried the test socket with a filter

[#5]

Yes Openreach in the past have said they are getting the same speed at the bottom of the pole so I know that the slow down is caused by something on the D-Side rather than internal or the overhead cable to the pole.

Can anyone from PN tell me if my line has been banded?

[#6]

On your neighbours router if you click the troubleshootiong tab then helpdesk that will show stats which are more useful for comparison purposes although first glance at yours shows a horrendously high noise margin.

Trying the test socket would be very useful if you could also supply the router stats once you're connected there.

[#7]

Tried removing the faceplace and plugging in a filter to the test socket but it would not even sync, tried another filter still wont sync, I seem to remember when the REIN engineer visited a few years back he put a filter box to the left of the master socket this could be the reason why it wont sync when plugged into the test socket.

Please see the attached photos showing what I have tried.

After re-syncing when I disconnected the cable from the top socket and put it back I have found got a slight improvement on the speed but still not got anywhere near my neighbours speed (please see attached stats after re-sync)

[#8]

I think the reason it would not sync in the first 2 attempts is because you were actually plugging the filter into an already filtered socket. If you had removed that socket also, you would then have a test socket that would be unfiltered.

Plugging your modem into the top socket is a good test though, and it would be good to see signal to noise margins and attainable rates from there.

[#9]

I notice from the photo that the first faceplate (the one you removed) didn't have any extension wiring attached to it. Ar there no other phones or phone sockets anywhere else in the house?

[#10]

There are no other sockets in the house only this socket.

I have attached the stats which show the results with it connected to the top socket, I have also posted my Neighbours helpdesk extended stats.

[#11]

hello,

sorry to hijack your thread but assuming you are using a unlocked HG612's GUI to check the line stats I find that they are wildly inaccurate.  As such you will get more accurate information via telnetting in to the modem and running a xdslcmd command.

My HG612 GUI shows, very similar and in some sections the same errors as yours.  When you check via telnet you get info that is much more accurate as you can see from the attached images.

[#12]

Thanks I will give that a go!

[#13]

sorry for also hijacking

1) you said a REIN engineer installed a box along from the NTE5 master socket in the past...these are usually RF filters used to remove or reduce noise on problematic lines,  could this be causing an issue with the higher frequencies of VDSL (i'm assuming it was fitted when you had ADSL) ? - try removing it and see what you get?

2) the fact it reports NO NOISE MARGIN AT ALL for the upload and has so many HEC errors on the upload definitely shows something's not right (be it poor reporting or a bad line)

just out of interest, have you tried another router? - a different chipset may produce a better result?

[#14]

@snadge The Filter was fitted by Openreach after the Fibre was fitted, I haven't tried another Modem as in the past Openreach have said they are getting the same speeds from the bottom of the pole across the road. 

Have run telnet as suggested and here are my stats, just wondered if anyone can shed some light on the problem from this:

# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 4
Last initialization procedure status:   0
Max:    Upstream rate = 4554 Kbps, Downstream rate = 29716 Kbps
Bearer: 0, Upstream rate = 4579 Kbps, Downstream rate = 27399 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State:       L0
Mode:                   VDSL2 Annex B
VDSL2 Profile:          Profile 17a
TPS-TC:                 PTM Mode(0x0)
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        7.8             5.8
Attn(dB):        25.8            0.0
Pwr(dBm):        10.4            7.0
                        VDSL2 framing
                        Bearer 0
MSGc:           -6              26
B:              228             143
M:              1               1
T:              0               35
R:              10              14
S:              0.2647          0.9961
L:              7224            1269
😧              2               1
I:              239             79
N:              239             158
Q:              2               0
V:              1               0
RxQueue:                132             0
TxQueue:                33              0
G.INP Framing:          18              0
G.INP lookback:         31              0
RRC bits:               0               24
                        Bearer 1
MSGc:           90              -6
B:              0               0
M:              2               0
T:              2               0
R:              16              0
S:              10.6667         0.0000
L:              24              0
😧              1               0
I:              32              0
N:              32              0
Q:              0               0
V:              0               0
RxQueue:                0               0
TxQueue:                0               0
G.INP Framing:          0               0
G.INP lookback:         0               0
RRC bits:               0               0
                        Counters
                        Bearer 0
OHF:            0               1339410
OHFErr:         960             906
RS:             931989464               2507132
RSCorr:         1129106         708
RSUnCorr:       0               0
                        Bearer 1
OHF:            21616248                0
OHFErr:         1               0
RS:             129697121               0
RSCorr:         5586            0
RSUnCorr:       1               0

                        Retransmit Counters
rtx_tx:         103543467               0
rtx_c:          6777881         0
rtx_uc:         171371          0

                        G.INP Counters
LEFTRS:         5340            0
minEFTR:        27396           0
errFreeBits:    1378291         0

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    1111374665              0
Data Cells:     283459977               0
Drop Cells:     0
Bit Errors:     0               0

                        Bearer 1
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    0               0
Data Cells:     0               0
Drop Cells:     0
Bit Errors:     0               0

ES:             15439           8397
SES:            173             8
UAS:            265             247
AS:             347218

                        Bearer 0
INP:            51.00           0.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            8.74
OR:             0.01            29.25
AgR:            27579.23        4608.22

                        Bearer 1
INP:            2.50            0.00
INPRein:        2.50            0.00
delay:          0               0
PER:            16.06           0.01
OR:             47.81           0.01
AgR:            47.81   0.01

Bitswap:        266957/266959           520/522

Total time = 1 days 17 hours 20 min 39 sec
FEC:            103338535               27453
CRC:            31624           9153
ES:             15439           8397
SES:            173             8
UAS:            265             247
LOS:            0               0
LOF:            12              0
LOM:            12              0
Latest 15 minutes time = 5 min 39 sec
FEC:            87              0
CRC:            0               3
ES:             0               3
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 15 minutes time = 15 min 0 sec
FEC:            483             3
CRC:            0               1
ES:             0               1
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 1 day time = 17 hours 20 min 39 sec
FEC:            153875          101
CRC:            313             97
ES:             124             94
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 1 day time = 24 hours 0 sec
FEC:            287227          254
CRC:            281             444
ES:             83              431
SES:            1               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Since Link time = 4 days 26 min 57 sec
FEC:            1129106         708
CRC:            960             906
ES:             299             856
SES:            1               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0

[#15]

HI

Maybe not in you case, but, I wouldn't believe an BTOR engineer about readings unless I seen his/hers JDSU myself...not saying they are liars but I've had to deal with some iffy ones that where trying to say anything to get me to stop!

you might get better help at KITZ dedicated broadband fault fixing forum, where there are BTOR engineers a plenty that can help (good ones that know more than most) - and are very skilled with FTTC. Personally I'm new to FTTC...but I have about 8 years of experience working with ADSL/2/2+ which is basically similar except more frequencies are used and the fibre is closer to your home.

1)  the first thing I can see is your on profile 17a (80/20) so they may have the "taps opened right up" which may be causing an issue if your line cant support speeds faster than 40Mb anyway?, they should have you on a 8 Profile (40Mb) if that's all you can get.

2) I can also see that your MAX line speed, it reports your current line to able to go no faster than 29Mb hence the 27Mb sync.

3) another thing I can see is your upstream is syncing higher than the reported MAX LINE SPEED?? - it may be just 25Kbps but its still wrong.

4) Its now showing an SNRM for upload at 5.8db....BUT... it reports ZERO for Line Attenuation????  , seems unable to measure it? - Line Attenuation basically is the measurement that determines the length & quality of your phone line & how much the signal is likely to degrade on it, the lower it is - the closer you are to the Cab(FTTC) / Exchange(ADSL) and/or the better quality of line is there (you could live next door too the cab/exchange but have loads of aluminium wiring along rusty joints which would degrade your line / connection qualuty...hence the Attenuation number goes up).

5) your on VDSL2 AnnexB which means your on an "impacted" line which could possibly have some fault/noise/issues/long line etc that could cause a lower sync speed on that line.... I'm on Plusnet Annex B - and my max is 67Mb, and I am circa 200m from the cab...hence 65Mbps sync would be 100% spot on for my line according to many websites, rather I'm on 40/2 though and get 39,999k sync

6) the Retrain Reason (last time it started up) at no:4 means Loss Of Signal, but this could just be you killing power at the plug for few seconds to reboot, if not then it lost the signal and retrained the line, I dont know if manually rebooting would report 4...it would seem daft to do so...

As for the rest of the report such as framing and counter numbers, you would get much better help from more FTTx experienced BTOR's and Broadband Engineers on KITZ... but:-

Since Link time = 4 days 26 min 57 sec
FEC:            1129106         708
CRC:            960             906
ES:             299             856
 I think the bolded ones might be a little high for 4 days uptime - especially the upload which has more retransmits (CRC) and errored seconds (ES) than it has corrected errors (FEC)

The fact your upload shows ZERO Line Attenuation says to me there is either a fault on the line...OR...they have you on the incorrect profile for your line..or possibly both - sounds to me like BTOR have been out to yours a few times (same here in 2012 ...7 visits in 3 months with Sky) and the last one (who fixed it) said the same as yours...BT wont do any more to try and fix your line (before he started)...

If I where you I would head over to KITZ, make a post and get onto the phone to plusnet, ask them to send out a Broadband Engineer

 EDIT: you never mentioned how far from the cabinet you are roughly, or what your speed was from day one - also, it does decrease over time as more people sign up to fibre in your street due to crosstalk from the high frequencies - BT are working on something called VECTORING to cancel this out.