g.inp increased my ping

I noticed yesterday that dslstarts started showing G.INP was enabled on my line my latency seems to have increased a bit - is that normally ?

My Broadband Ping before g.inp

My Broadband Ping after g.inp

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 25636 Kbps, Downstream rate = 79468 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79727 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): 6.3 15.2
Attn(dB): 14.1 0.0
Pwr(dBm): 13.8 4.1
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 42
R: 10 16
S: 0.0975 0.3781
L: 20851 5374
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 63 0
TxQueue: 21 0
G.INP Framing: 18 0
G.INP lookback: 21 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 0
D: 3 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 2866284
OHFErr: 0 7
RS: 2522884752 4198858
RSCorr: 718 13
RSUnCorr: 0 0
Bearer 1
OHF: 3841680 0
OHFErr: 0 0
RS: 46099424 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 51347 0
rtx_c: 122 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 1 0
minEFTR: 79710 0
errFreeBits: 75035957 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 870992935 0
Data Cells: 194678952 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: 0 7
SES: 0 0
UAS: 26 26
AS: 61709

Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 79808.62 20063.54

Bearer 1
INP: 4.00 0.00
INPRein: 4.00 0.00
delay: 3 0
PER: 16.06 0.01
OR: 95.62 0.01
AgR: 95.62 0.01

Bitswap: 18500/18500 6/6

Total time = 17 hours 8 min 55 sec
FEC: 718 13
CRC: 0 7
ES: 0 7
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 8 min 55 sec
FEC: 33 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: 40 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 17 hours 8 min 55 sec
FEC: 718 13
CRC: 0 7
ES: 0 7
SES: 0 0
UAS: 26 26
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
Since Link time = 17 hours 8 min 27 sec
FEC: 718 13
CRC: 0 7
ES: 0 7
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#

If you have moved from Fastpath to Interleaved, that would increase your latency.

Strange stats re latency.

First, for Bearer 0 G.INP normally causes a residual interleaving depth of 8 on the downstream, with a (latency) "Delay" of 0. Bearer 1 normally has interleaving 1 (fast path) and 0 delay.

Yours has the expected depth on bearer 0 of 8, but an odd depth on Bearer 1 of 3. You've also got a very unusual delay on bearer 1 of 3ms.

I'm a bit disturbed by all the deep red lines on your BQMs, both of the 6 Feb one and the 13 Feb. Are most of these caused by something you are doing? If so, you may have upset the DLM.

Every disconnect/reconnection of your PPP session on Plusnet is likely to result in a latency change. You need to record your gateway every time you see your BQM average level change. I did for quite a while, just in a WordPad document. It was quite useful. Date & time, gateway, latency. Possibly one other field but I forget now.

Your stats are quite similar to mine, I see not increase in latency from G.inp As RobertoS has eluded to it will almost be down to plusnet routing

When i would gateway hop some of the routes from certain gateways would differ quite a lot iirc one as around 10ms higher,

Looking at you ping monitor it looks like some peak time congestion is present too, though it's not that easy toi tell as it looks like the connection is in constant use 24hrs if that yellow spiking is usage if it ain't there is a problem