If Sky are saying the line is good and you still get the minimum speed, they won't do much more. From the first two graphs you showed, it does look like a contention/bandwidth issue. Maybe you have a few heavy business users on your cabinet. Do what I did and contact Openreach, they can at least monitor the DSLAM for a few days and rule out bandwidth issues there, give them copies of the BTW speed tester reports. If they say all is well, then it has to be an exchange issue. Your sync speed is maxed out, low noise margin etc, so your copper line to the cab seems good.

In my case I didn't even notice high latency really, the DSLAM was just straight up dropping packets at peak times and the ISP's didn't seem to know about it, BT claimed their SVLAN utilization rate was 20% and that there was no congestion issues. It was only Openreach who monitored the DSLAM and found an issue after I contacted them.

Email the CEO with the reports at different times of day and explain to them that Sky will do no more and that you have had engineer visits to check your line. It then puts it on them to find out what's wrong, especially if Sky is saying they are not having congestion issues at the SVLAN. Might be worth getting Sky to check their SVLAN reports for congestion first.

My guess is that the reason they won't offer people the 80/20 is due to bandwidth issues at the cabinet, the new Ofcom rules mean ISP's can only advertise average speeds, that includes peak time congestion, so if the average is lower then 70, they just wont offer the 80/20 package. Most of the cabinets still work off 1G links for 200-300 connections. Even a maxed out cab with a 6G fibre link back to the exchange only gives a guarentee of 20mb. You only need 50 or 60 users to be downloading a game at the same time to fill that bandwidth. So a speed drop from 80 to 50 wouldnt actually take much if the cabinet fibre links are low or the cab is full.

Edited by deleted (Sat 12-Sep-20 13:27:04)

You are on a Huawai all in one, thus contention will be an issue, likely at the cab side, especially if the cab is nearly full at 70 premises.

In reply to a post by Taras:

You are on a Huawai all in one, thus contention will be an issue, likely at the cab side, especially if the cab is nearly full at 70 premises.

Why would an All in One make contention an issue?
They are 100% identical to the smaller Huawei cabinets, with a Huawei MA5616 inside.
They can handle 256 lines no problem.

The OP's cabinet has 70 homes connected to it. Contention definitely shouldn't be an issue.

Is there anything here from a change of router that might help diagnose my connection ?

VDSL Training Status: Showtime
Mode: VDSL2 Annex B
VDSL Profile: Profile 17a
Traffic Type: PTM Mode
Link Uptime: 0 day: 22 hours: 15 minutes

VDSL Port Details Upstream Downstream
Line Rate: 20.063 Mbps 79.998 Mbps
Actual Net Data Rate: 19.999 Mbps 79.999 Mbps
Trellis Coding: ON ON
SNR Margin: 15.8 dB 7.8 dB
Actual Delay: 0 ms 0 ms
Transmit Power: - 9.2 dBm 13.9 dBm
Receive Power: -18.6 dBm 6.4 dBm
Actual INP: 0.0 symbols 48.0 symbols
Total Attenuation: 9.2 dB 7.4 dB
Attainable Net Data Rate: 26.586 Mbps 89.304 Mbps
==================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 2.1 7.4 11.1 N/A 5.0 10.8 16.9
Signal Attenuation(dB): 2.1 6.9 10.2 N/A 5.5 10.7 16.9
SNR Margin(dB): 16.5 15.9 15.7 N/A 7.8 7.7 7.7
Transmit Power(dBm):-22.9 -35.5 - 9.6 N/A 11.3 7.4 7.2
==================================================
VDSL Counters

Downstream Upstream
Since Link time = 15 min 37 sec
FEC: 268 7733
CRC: 0 197
ES: 0 153
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 1 min 8 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 4 8
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 = 22 hours 16 min 8 sec
FEC: 268 7733
CRC: 0 197
ES: 0 153
SES: 0 0
UAS: 30 30
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Total time = 22 hours 16 min 8 sec
FEC: 268 7733
CRC: 0 197
ES: 0 153
SES: 0 0
UAS: 30 30
LOS: 0 0
LOF: 0 0
LOM: 0 0

A friend on another exchange also using a ZyXel VMG8924-B10A on 240 meter cable, BT 80/20 and gets good throughput and a neat graph from the TBB tests.
https://www.thinkbroadband.com/_assets/speedtest/but...
Compared to mine
I'm on same router, 170 meters, Plusnet 80/20.
https://www.thinkbroadband.com/_assets/speedtest/but...

Looking at the DSL stats from both routers I noticed a great difference in the signal margins and attenuations, band status etc and his attainable rate is also higher.

Would grateful for any comments

His.
=============================================
VDSL Training Status: Showtime
Mode: VDSL2 Annex B
VDSL Profile: Profile 17a
G.Vector: Disable
Traffic Type: PTM Mode
Link Uptime: 0 day: 20 hours: 11 minutes
============================================
VDSL Port Details Upstream Downstream
Line Rate: 19.999 Mbps 79.998 Mbps
Actual Net Data Rate: 20.000 Mbps 79.999 Mbps
Trellis Coding: ON ON
SNR Margin: 13.9 dB 5.1 dB
Actual Delay: 0 ms 0 ms
Transmit Power: 6.4 dBm 12.7 dBm
Receive Power: -12.1 dBm -2.5 dBm
Actual INP: 48.0 symbols 55.0 symbols
Total Attenuation: 0.0 dB 15.0 dB
Attainable Net Data Rate: 32.134 Mbps 91.820 Mbps
======================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 4.1 17.7 27.3 N/A N/A 9.9 23.2 37.0
Signal Attenuation(dB): 4.1 16.9 26.7 N/A N/A 11.6 22.9 37.0
SNR Margin(dB): 13.1 13.4 14.1 N/A N/A 5.2 5.0 5.0
TX Power(dBm): -8.8 -25.9 6.3 N/A N/A 8.8 7.8 7.3
======================================================
Mine
============================================
VDSL Training Status: Showtime
Mode: VDSL2 Annex B
VDSL Profile: Profile 17a
Traffic Type: PTM Mode
Link Uptime: 2 days: 20 hours: 1 minute
===========================================
===========================================
VDSL Port Details Upstream Downstream
Line Rate: 20.063 Mbps 79.998 Mbps
Actual Net Data Rate: 19.999 Mbps 79.999 Mbps
Trellis Coding: ON ON
SNR Margin: 15.5 dB 7.6 dB
Actual Delay: 0 ms 0 ms
Transmit Power: - 9.2 dBm 13.9 dBm
Receive Power: -18.5 dBm 6.5 dBm
Actual INP: 0.0 symbols 48.0 symbols
Total Attenuation: 9.1 dB 7.3 dB
Attainable Net Data Rate: 26.737 Mbps 89.234 Mbps
===================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 1.9 7.3 10.9 N/A 4.9 10.6 16.9
Signal Attenuation(dB): 1.9 6.6 10.1 N/A 5.4 10.5 16.9
SNR Margin(dB): 15.5 15.5 15.5 N/A 7.7 7.7 7.6
Transmit Power(dBm):-23.2 -35.5 - 9.5 N/A 11.3 7.7 7.1
===================================================

Can you post the results of the --stats command?
It's the Telnet Data - Connection Stats page on dslstats.

It shows a bunch of extra parameters that show things that affect throughput like INPRein and minEFTR.

I posted this yesterday but it does not appear to me here today. ??

Thanks

Stats recorded 18 Oct 2020 13:43:21

DSLAM type / SW version: BDCM:0xa49a (164.154) / v0xa49a
Modem/router firmware: AnnexA version - A2pv6F039q.d26a
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 4 days 22 hours 50 min 17 sec
Resyncs: 0 (since 18 Oct 2020 13:43:21)

Downstream Upstream
Line attenuation (dB): 8.8 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 79999 19999
SNR margin (dB): 7.7 15.5
Power (dBm): 13.9 -9.2
Interleave depth: 16 1
INP: 48.00 0
G.INP: Enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)

RSCorr/RS (%): 0.0001 0.2798
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 6.61

That's not what i was hoping to see.

I need the output of 'xdslcmd info --stats'
which is the exact same text shown in dslstats under "Telnet Data - Connection stats".

You just posted the exact same truncated stats as the day before.

First, thanks.
Second, I do net see my post from yesterday in the ticket but I do see today's.
third.Using the conf guide on the dslstats site in the example t shows xdsicti in the command page so I used that.
I have now set xdslcmd in the prefix box and get an error "no data returned".

What have I missed please ?.

Some modems use 'xdslcmd' and some use 'xdslctl' instead.

If dslstats is working, just paste me whatever is in the "Telnet Data - Connection stats" tab.

That's got all the info i need.