[Sephiroth]

Thanks for that.

Cable Modem Upstream

Upstream Lock : Locked
Upstream Channel ID : 4
Upstream Frequency : 37500000 Hz
Upstream Modulation : QPSK
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 42.0 dBmV
Upstream Mini-Slot Size : 2

At first sight, your problem appears to be the fact that you are on QPSK upstream modulation. On a less noisy upstream circuit, your modulation would be 16QAM which packs 4 bits per symbol presented to the error correction cisuit at either end. QPSK is the more noise tolerant 2 bits per symbol - for that channel.

This potentially has two effects:

1/
Your line is so noisy that packets don't reach their destination. However, your event log doesn't contain evidence of corrupted data, which would appear as serious numbers of T3 timeouts. This suggests that your circuit is coping with noise on QPSK modulation.

2/
Because your upstream only packs 2 bits per symbol, everyone on your channel has this modulation. The capacity of the channel is only half of what it would be at 16QAM so it congests sooner because people don't stop doing stuff if it appears to work. That sort of congestion on your upstream isn't in the VM network - it's between you and your entry point to the VM network.

Obviously I can't rule out something in the network, but seeing QPSK in your upstream makes nme raise the proverbial eyebrow.

IMO you should post all of this (MTR, stats, event log) and your story on the VM Forum and wait for a tech to check your circuit. They'll fo that anyway - they'll have the history and it won't matter if you haven't seen a naff MTR recently.

Hope that helps.