I began noticing erratic internet service issues beginning somewhere around Oct 8, or so. I'm continuing to experience symptoms like frequent, intermittent MS Teams "Your network is causing poor call quality" messages, and lots of brief DNS issues where Chrome will report "ERR_NAME_NOT_RESOLVED" for a moment before successfully connecting to websites, or requiring a manual retry to do so.
Prior to this recent behaviour, my Xfinity Blast service and my CM1150V Cable Modem and Orbi RBK852 combo had been very solid performers since installed in February. Nothing physical has changed in my setup, at least inside the house.
I've been wondering if Comcast may have pushed Firmware Version V4.02.02 around that time a few weeks ago, which might be the culprit. Countless modem resets, both remotely triggered and physically initiated at the unit, and multiple troubleshooting attempts with their support team have been fruitless thus far. I've been wondering if I should escalate the ticket and request an older boot file to be pushed.
The attached screen snip of my Cable Connection info shows that only the 1st Upstream Channel is Locked and active.
My Event Log keeps showing many recurring instances of Critical (3) Priority:
- 16 consecutive T3 timeouts while trying to range on upstream channel x (where x=1-3)
- No Ranging Response received - T3 time-out
- Ranging Request Retries exhausted
...and a few Notice (6) entries:
- CM-STATUS message sent. Event Type Code: 7; Chan ID: 2 3 4;
- CM-STATUS message sent. Event Type Code: 8; Chan ID: 2;
I know of at least one other customer ( @cmarti02 ) with the same firmware, but not in my same local region, who is experiencing the exact same same behavior. Is there any way to determine when v4.02.02 was pushed, in order to discern if there's a correlation? Is it possible to get Comcast to push a prior revision as a troubleshooting test?
