Dodgy VDSL, give me some ideas...

Probably looking at @Hio77, but keen to hear others thoughts.

Chucked a new VDSL connection for a custom, on a POTS line, filter installed.

Stats (from Chorus side) look like this:

DIAGNOSIS PARAMETERSACTUAL BITRATE DOWNSTREAM 113.279 Mb/sUPSTREAM 29.999 Mb/s

ACTUAL PSD DOWNSTREAM -56.2 dBm/HzUPSTREAM -65.0 dBm/Hz

USER TRAFFIC DOWNSTREAM DetectedUPSTREAM Detected

ATTAINABLE BITRATE DOWNSTREAM 113.635 Mb/sUPSTREAM 36.513 Mb/s

ATTENUATION DOWNSTREAM 11.9 dBUPSTREAM 14.8 dB

NOISE MARGIN DOWNSTREAM 6.1 dBUPSTREAM 9.9 dB

OUTPUT POWER DOWNSTREAM 14.5 dBmUPSTREAM 1.9 dBm

RELATIVE CAPACITY OCCUPATION DOWNSTREAM 99.0 %UPSTREAM 85.0 %

LOOP ATTENUATION DOWNSTREAM 11.9 dBUPSTREAM 14.8 dB

LINE OPERATIONAL INFOESTIMATED ELT DISTANCE 343LAST STATUS CHANGED 1548120309962LINE STATUS upSERVICE STABILITY UNSTABLELINE CONFIGURATIONCPE TYPE UnknownDSL TYPE non.shdsl.opermode vdsl2.g9932.profile.17a, line.type.potsLINE ID USER LABEL UnknownSPECTRUM PROFILE NAME EUBAV-VDSL2-1SERVICE PROFILE NAME EUBAV-I-FSFSSERVICE TEMPLATE NAME VDSL2-I-V-ddDLM

So it's rocking it hard on a 17a profile at 110Mbps down, but is "unstable" in Chorus' words and also from our own monitoring via SNMP. I've requested we pull it back to a 9b profile, but wondering if there is a better option. Obviously could just simply be a bad line, so no amount of profile changing will help. But from experience, what do people reckon?

Edit: dam, tables didn't come out properly lol