ContributionsMost RecentMost LikesSolutionsRe: Video calls dropping, upstream showing 16QAM Thanks @Tom_W1 - we saw some improvement earlier this week, but as the temperatures have dropped again there is increased packet loss and continuing 32/16QAM reported upstream. Re: Video calls dropping, upstream showing 16QAM As I said above, I would rather someone from the Forum Team reaches out so we can resolve this. Re: Video calls dropping, upstream showing 16QAM Significant deterioriation in the last 24 hours. Again status says "nothing wrong"... Re: Video calls dropping, upstream showing 16QAM Can I get some assistance here please? I tried calling but because "everything is working" they were not even interested in booking an engineer (despite certain things explicitly not working)... Re: Video calls dropping, upstream showing 16QAM ...yes, I know... Re: Video calls dropping, upstream showing 16QAM Had a new omni, cable drop and modem last year when this happened... Re: Video calls dropping, upstream showing 16QAM BQM here. Again, surprisingly unremarkable but for some red dots along the top indicating marginal packet loss. BQM Re: Video calls dropping, upstream showing 16QAM Also nothing on check services online or on 0800 number (unsurprisingly... they are never accurate.) Video calls dropping, upstream showing 16QAM Sigh. My Virgin broadband is misbehaving again. This time, it's in the subtle and annoying type of problem. Most things are alright, but I see packet loss, my partner who works from home sees video calls drop entirely, and general slowness. BQM doesn't show much, but the main thing I see is upstream QAM negotiated down. Power levels look OK (DS a little high, but it's cold), and DS errors look broadly OK. Last time this happened, it was a cabinet problem, found after several premises engineers came (and didn't come), insisted on replacing the modem (not the fault) and various other horrendous first line experiences. Can we cut through this Gordian knot and just get someone from Networks to come and look at the cabinet please? Data below. Matt Downstream bonded channels Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1 138750000 5.4 38 256 qam 1 2 146750000 5.5 38 256 qam 2 3 154750000 5.4 38 256 qam 3 4 162750000 5.3 38 256 qam 4 5 170750000 5.1 38 256 qam 5 6 178750000 5 38 256 qam 6 7 186750000 4.9 38 256 qam 7 8 194750000 4.9 38 256 qam 8 9 266750000 3.2 38 256 qam 17 10 274750000 3.2 38 256 qam 18 11 282750000 3.5 38 256 qam 19 12 290750000 4 38 256 qam 20 13 298750000 4.6 38 256 qam 21 14 306750000 4.8 38 256 qam 22 15 314750000 5.4 38 256 qam 23 16 322750000 5.6 38 256 qam 24 17 330750000 6 38 256 qam 25 18 338750000 6.4 38 256 qam 26 19 346750000 6.1 38 256 qam 27 20 354750000 6.5 38 256 qam 28 21 362750000 6.8 38 256 qam 29 22 370750000 7 40 256 qam 30 23 378750000 6.6 38 256 qam 31 24 386750000 5.9 38 256 qam 32 Downstream bonded channels Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1 Locked 38.6 89 0 2 Locked 38.6 71 0 3 Locked 38.9 55 0 4 Locked 38.6 55 0 5 Locked 38.6 52 0 6 Locked 38.6 57 0 7 Locked 38.6 47 0 8 Locked 38.6 49 0 9 Locked 38.6 371 0 10 Locked 38.6 414 0 11 Locked 38.6 870 0 12 Locked 38.6 491 0 13 Locked 38.6 416 0 14 Locked 38.9 269 0 15 Locked 38.6 305 0 16 Locked 38.9 254 0 17 Locked 38.9 183 0 18 Locked 38.9 141 0 19 Locked 38.9 186 0 20 Locked 38.9 134 0 21 Locked 38.9 113 0 22 Locked 40.3 76 12 23 Locked 38.9 118 0 24 Locked 38.9 114 0 Upstream bonded channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 1 23599976 44.3 5120 32 qam 5 2 36600000 43.8 5120 64 qam 3 3 30100000 44 5120 64 qam 4 4 43100058 44 5120 16 qam 2 5 49600000 44.2 5120 16 qam 1 Upstream bonded channels Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 1 ATDMA 0 0 15 0 2 ATDMA 0 0 9 0 3 ATDMA 0 0 8 0 4 ATDMA 0 0 5 0 5 ATDMA 0 0 14 0 Network log is completely unremarkable. Re: Major packet loss since last night - dead cab amp? It looks like the Sunday impact may have been remediatory work; a short 10-15 minute spike and then has been fine since. So no further action needed...