ContributionsMost RecentMost LikesSolutionsRe: Upstream channels in freefall Hi sorry for the late reply, a few days before the visit, the problem resolved itself and so I cancelled the visit. No issues since then so I assume it was a more acute fault. Re: Upstream channels in freefall Yeah I did that on day one and nothing was reported as wrong. I have an engineer coming on Monday so perhaps that will help, though I don't believe the fault to be due to equipment within my house. Re: Upstream channels in freefall As of 22:43 this evening the upstream channels have gone haywire again, modulation is negotiating at 16QAM and massive packet loss is occurring. The service issues consistently begin around 22:30 every evening and seem to last varying amounts of time. 3.0 Upstream channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 0 49600000 46 5120 QAM 16 7 1 43100000 45.8 5120 QAM 16 8 2 36600000 45.3 5120 QAM 16 9 3 30100000 45 5120 QAM 16 10 4 23600000 44.5 5120 QAM 16 11 Re: Upstream channels in freefall Network Log Time Priority Description 17-08-2024 09:21:31 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 09:21:30 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 09:21:30 critical 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 09:08:43 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 09:08:20 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 09:08:19 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 09:08:19 critical 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 09:01:31 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 09:01:08 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 09:01:08 critical 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 09:01:08 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:54:18 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:53:56 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:53:55 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:53:55 critical 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:45:48 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:45:30 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:45:28 critical 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:45:28 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:39:02 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:38:39 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:38:38 critical 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:38:38 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:28:37 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:28:13 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:28:12 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:28:12 critical 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:21:24 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:21:01 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:21:00 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:21:00 critical 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 17-08-2024 08:14:11 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; Re: Upstream channels in freefall 3.0 Upstream channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 0 49600000 45.8 5120 QAM 32 7 1 43100000 45.5 5120 QAM 32 8 2 36600000 45 5120 QAM 32 9 3 30100000 45 5120 QAM 32 10 4 23600000 44.3 5120 QAM 32 11 3.0 Upstream channels Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 0 ATDMA 0 0 0 0 1 ATDMA 0 0 0 0 2 ATDMA 0 0 32 0 3 ATDMA 0 0 504 0 4 ATDMA 0 0 2036 0 3.1 Upstream channels Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation 12 10.4 41.5 2K QAM 256 3.1 Upstream channels Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts 12 OFDMA 208 74000000 0 0 Re: Upstream channels in freefall I did a pinhole reset only last night at about 11PM. All those T3 timeouts in the upstream channels are since then. Re: Upstream channels in freefall 3.0 Downstream channels Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1 331000000 5.9 42 QAM 256 25 2 179000000 5.9 42 QAM 256 6 3 187000000 5.9 42 QAM 256 7 4 195000000 6.2 41 QAM 256 8 5 203000000 6.2 41 QAM 256 9 6 211000000 6.4 41 QAM 256 10 7 219000000 6.4 42 QAM 256 11 8 227000000 6.3 42 QAM 256 12 9 235000000 6.2 42 QAM 256 13 10 243000000 6.1 42 QAM 256 14 11 251000000 5.9 42 QAM 256 15 12 259000000 6 42 QAM 256 16 13 267000000 6.1 42 QAM 256 17 14 275000000 6.1 42 QAM 256 18 15 283000000 6.1 42 QAM 256 19 16 291000000 6.2 42 QAM 256 20 17 299000000 6.1 42 QAM 256 21 18 307000000 6.1 42 QAM 256 22 19 315000000 6 42 QAM 256 23 20 323000000 5.9 42 QAM 256 24 21 339000000 5.9 42 QAM 256 26 22 347000000 5.9 42 QAM 256 27 23 355000000 5.9 42 QAM 256 28 24 363000000 5.8 42 QAM 256 29 25 371000000 5.8 42 QAM 256 30 26 379000000 5.8 42 QAM 256 31 27 387000000 5.6 42 QAM 256 32 28 395000000 5.8 42 QAM 256 33 29 403000000 5.7 42 QAM 256 34 30 411000000 5.8 42 QAM 256 35 31 419000000 5.8 42 QAM 256 36 3.0 Downstream channels Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1 Locked 42 0 0 2 Locked 42 2 0 3 Locked 42 0 0 4 Locked 41 0 0 5 Locked 41 1 0 6 Locked 41 0 0 7 Locked 42 4 0 8 Locked 42 0 0 9 Locked 42 1 0 10 Locked 42 0 0 11 Locked 42 2 0 12 Locked 42 0 0 13 Locked 42 1 0 14 Locked 42 1 0 15 Locked 42 1 0 16 Locked 42 0 0 17 Locked 42 0 0 18 Locked 42 0 0 19 Locked 42 1 0 20 Locked 42 3 0 21 Locked 42 0 0 22 Locked 42 0 0 23 Locked 42 1 0 24 Locked 42 3 0 25 Locked 42 0 0 26 Locked 42 0 0 27 Locked 42 0 0 28 Locked 42 0 0 29 Locked 42 1 0 30 Locked 42 1 0 31 Locked 42 1 0 3.1 Downstream channels Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz) 37 94 4K 1840 QAM 4096 1108 3.1 Downstream channels Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile) 37 Locked 43 4.4 90033759 0 Upstream channels in freefall As of 10pm last night (and for a brief stint between 10pm and 1am the previous night) my upstream channels 2, 3 and 4 have crippled my connection with large amounts of T3 timeouts and lower than expected modulation (16-32 QAM vs expected 64). My downstream is fine achieving gig1 speeds as expected but my upload speed is down to half a megabit vs expected ~100mbps. Below is my BQM chart for today. Composing, forwarding, replying etc. not working for months on desktop As the title says, I'm unable to use my email properly on desktop, though emails can still be viewed and received. This has been the case for months so I've mainly been using other devices, hoping the issue would be resolved on its own. As this hasn't happened and its becoming a nuisance I'm hoping someone here can help.