I have plotted the data you sent (attached for reference), but it appears that some of it is missing from the Bitloading & SNR sections.
Hence the 'odd' appearance of those graphs.
I don't know if Eric's program only reports particular 'useable' tones' data for those elements or perhaps you didn't manage to copy all of it.
Alternatively it could be some sort of issue that your modem isn't actually reporting on all the tones data.
Strictly speaking, there should be data for all 4096 tones (0 to 4095), even if it is zero values.
Could you double-check that you had actually copied all the data present & resend it if you discover that you had missed some of it?
I have inserted zeros for the missing data & re-plotted it (also attached), but we don't yet know for sure that the missing values were actually all zeros.
Your QLN & Hlog data is all there though & from that we can see that although a little 'spiky', QLN is generally low (which is good), but Hlog (attenuation) is quite severe. However, there is no significant evidence of harmful bridged taps etc.
The data suggests you are possibly around 1600m from the cabinet.
Do you know the actual distance?
There's every chance that your HG612's firmware will be remotely updated soon.
That may bring some improvement, as it does seem to improve performance & stability on longer lines.
You have 143 errored seconds over the 1 day 8 hours connection time, which isn't too bad for a less than perfect fastpath connection & all your other error counts (FEC, HEC, CRC etc.) are remarkably low or zero values.
Although all the band plan tones are there as Discovery Phase:-
Discovery Phase (Initial) Band Plan
US: (0,95) (880,1195) (1984,2771)
DS: (32,859) (1216,1959) (2792,4083)
your connection is only able to use a few of them at Medley Phase:-
Medley Phase (Final) Band Plan
US: (0,95)
DS: (32,859) (1216,1959)
That's not unusual for a long connection length, but the original, non-updated firmware reports all the tones for useable bands, whereas the updated firmware only reports the tones that were useable when the connection had trained up from cold or from a resync.
Overall & depending on the actual length of your connection, everything apart from the really low SNRM values looks relatively good.
SNRM must have been higher when the connection resynced as DS Attainable rate is now only around 7Mbps, whereas an actual DS sync speed of 9 Mbpd was achieved.
This does suggest that SNRM has either gradually or suddenly lowered to the current 3dB.
Target SNRM for VDSL2 connections is 6dB, so connections usually sync at around that value.
Rebooting the modem during daylight hours (around noon) may show around 6dB SNRM.
It might be a good idea to try that & immediately grab all the relevant stats.
If your connection is significantly less than 1600m in length, it would appear that you have a serious problem somewhere.
I'm not sure for how long a period DSLStats can store ongoing data.
If you felt so inclined, you could try my HG612 Modem Stats program that can store many, many months worth of ongoing & snapshot data, sampled every minute for longer term monitoring of changing performance/conditions, but it does need to run 24/7 during the monitoring period to be worthwhile & meaningful data.