Climbing Latency

[#1]

Is anyone from the Plusnet side able to do a check of my line, as my latency seems to be climbing out of control.

A few weeks ago it was about 17-18ms, it jumped to 26-27ms and after a high number of connection drops on Saturday is now up to 33ms.

Would it just be better to go through the fault checker process, as it seems there might be an issue, but obviously it keeps getting stabilised and so currently I assume fault checking is going to say everything is fine.

Thanks in advance
Mark

[#2]

Here are the BQM snapshots for the last couple of latency "jumps"

• BQM 22nd February 
• BQM 28th March 

On the days preceding these there were quite a few drops in the connection, and it seems that upping the base latency is stabilising, but how far cab that go?

BTW this is not just BQM, I'm also seeing the same on the stats from my Unifi router,

[#3]

And current line stats

 ---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
  Running Mode            :      17A       State                : SHOWTIME
  DS Actual Rate          : 32400000 bps   US Actual Rate       :  6149000 bps
  DS Attainable Rate      : 44701656 bps   US Attainable Rate   :  6277390 bps
  DS Path Mode            :  Interleave    US Path Mode         :  Interleave
  DS Interleave Depth     :     1557       US Interleave Depth  :      129
  NE Current Attenuation  :       23 dB    Cur SNR Margin       :        7  dB
  DS actual PSD           :     4. 9 dB    US actual PSD        :    12. 4  dB
  NE CRC Count            :       16       FE CRC Count         :    12122
  NE ES Count             :        1       FE  ES Count         :     6444
  Xdsl Reset Times        :        0       Xdsl Link  Times     :       24
  ITU Version[0]          : fe004452       ITU Version[1]       : 41590000
  VDSL Firmware Version   : 05-07-06-0D-01-07   [with Vectoring support]
  Power Management Mode   : DSL_G997_PMS_L0
  Test Mode               : DISABLE
-------------------------------- ATU-C Info ---------------------------------
  Far Current Attenuation :       33 dB    Far SNR Margin       :        6  dB
  CO ITU Version[0]       : b5004946       CO ITU Version[1]    : 544ed086
  DSLAM CHIPSET VENDOR    : < IFTN >

[#4]

So CS people did a GEA test and say that there is no issue, can anyone give a second opinion?

KBD

Test Outcome	Pass
Test Outcome Code	GTC_FTTC_SERVICE_0000
Description	GEA service test completed and no fault found .
Main Fault Location	OK
Sync Status	In Sync
Downstream Speed	32.4 Mbps
Upstream Speed	6.1 Mbps
Appointment Required	N
Fault Report Advised	N
NTE Power Status	PowerOn
Voice Line Test Result	Pass
Radio Frequency Ingress	Not Detected
Repetitive Electrical Impulse Noise	Not Detected
Cross Talk	Not Detected
Estimated Line Length In Metres	854.2
Upstream Rate Assessment	Reasonable
Downstream Rate Assessment	Low
Interference Pattern	Regular Interference Observed Daily
Service Impact	No Impact Observed
Interference Duration Longest Occurrence	From09:00to07:00
Interference Location	Customer Premise
Interference Observed In Days	0
Home Wiring Problem	Not Detected
Downstream Policing Discard Rate	0.0
Customer Traffic Level	Upstream and Downstream traffic detected
Technology	VDSL
DP Type	External
Profile Name	0.128M-35M Downstream, Interleaving High - 0.128M-7.2M Upstream, Error Protection Off
Time Stamp	2021-03-24T03:00:00

0.0

Parameters	MIN	MAX	AVG
Down Stream Line Rate	7.0 Mbps	34.9 Mbps	32.7 Mbps
Up Stream Line Rate	2.2 Mbps	7.1 Mbps	6.4 Mbps
Up Time	754.0 Sec	900.0 Sec	899.1 Sec
Retrains	0.0	6.0

GEA Test Detail
Circuit ID	NA	Service ID	BBEU18111332

They also seem to perfectly time it when there were no drops, there have been 2 in the last couple of days

[#5]

2 drops in a couple of days is not an issue.

Have you tried the basics to see why interleaving is so high? Is the phone line quiet? Dial 17070 option 2.

Did you ask for a Radius server graph to see the drops pattern?

What speeds should your line be getting, enter your phone number in the BT Wholesale DSL checker and post the results.

Did you ask for the line to be unbranded?

[#6]

I realise 2 drops is not really an issue, but it shows that even after all the measures that seem to have been put in place have still not left me a fully stable line, and has left me with a much higher baseline latency, so will that continue, or is my line just going to carry on degrading?

Yes I did quiet line test and all was fine. CS did a radius test and managed to miss any drops as they seemed to pick the day after more measures had been added.

I've had FTTC since it was first available, and at first I got about 45meg download, and over the years that has gradually degraded and now it's around 32meg. The house is 10 years old and there are no internal issues. The checker says:

Featured Products	Downstream Line Rate(Mbps)		Upstream Line Rate (Mbps)		Downstream Handback Threshold(Mbps)	WBC FTTC Availability Date	WBC SOGEA Availability Date	Left in Jumper
	High	Low	High	Low
VDSL Range A (Clean)	43.4	34.2	8.2	5	30.3	Available	Available	--
VDSL Range B (Impacted)	42.4	30	8	4.8	25	Available	Available	--

And in doing that it also has:

Observed Speeds	VDSL
Max Observed Downstream Speed	25.71
Max Observed Upstream Speed	5.29
Observed Date	2021-04-07

Sorry not sure why the line is banded, or why I would ask for that to be removed, might that help?

[#7]

Ah, where to start!

So the dsl check now shows your sync speed has fallen further to 25ish. The kbd test is dated nearly 10 days ago, a system limitation presumably, or was that when it was done?

DLM has banded your line due to the condition of the line, but as the sync speed is even lower you would not benefit from it being removed at this time. Not sure what measures you have done to date, but with that sync speed PN should still be investigating/getting Openreach to do so.

[#8]

Thanks  Mustrum, I think I'll push to get an engineer out. BTO came out a couple of years ago and put yet another new faceplate on and said he'd done the best he could at the time and things were good for a year or so, but it's back to where it was again at that time now.