25-07-2021 00:59 - edited 25-07-2021 01:06
I'm on the Vivid200 Broadband Package and have the Super Hub 2, which I have in modem only mode connecting directly to my PC via Ethernet. When I perform Speed Tests I typically notice I get 220Mbps Download and apparently 21Mbps Upload. Which I believe should be perfectly fine for me to be able to stream to Twitch at 6Mbps without any issues. Yet in recent time I've noticed whilst I'll be midstream I suddenly start dropping a ton of frames and then my OBS software will report it has lost network connection. When I check my Upload Speed at this point it's always at 0Mbps. I go check the system status page on the Virgin Website to see if there are any issues, I even run the test on my equipment, which usually just tells me to restart my Hub, which I do but the problem persists after restart. Usually I find that over a couple of hours the Speed does return to normal, but obviously during that time I'm completely unable to stream.
Here is the data from checking my router status:
Cable Modem StatusItem Status Comments
Acquired Downstream Channel (Hz) | 139000000 | Locked |
Ranged Upstream Channel (Hz) | 53700000 | Success |
Provisioning State | OK | Operational |
Downstream DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8
Frequency (Hz) | 139000000 | 147000000 | 155000000 | 163000000 | 171000000 | 179000000 | 187000000 | 195000000 |
Lock Status(QAM Lock/FEC Sync/MPEG Lock) | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked |
Channel ID | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
Modulation | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM |
Symbol Rate (Msym/sec) | 6.952000 | 6.952000 | 6.952000 | 6.952000 | 6.952000 | 6.952000 | 6.952000 | 6.952000 |
Interleave Depth | I=12 J=17 | I=12 J=17 | I=12 J=17 | I=12 J=17 | I=12 J=17 | I=12 J=17 | I=12 J=17 | I=12 J=17 |
Power Level (dBmV) | 6.32 | 6.32 | 6.37 | 6.44 | 6.25 | 6.11 | 6.06 | 6.04 |
RxMER (dB) | 37.94 | 37.94 | 37.94 | 37.94 | 38.26 | 38.26 | 38.26 | 38.26 |
Pre RS Errors | 1100 | 1004 | 349 | 345 | 313 | 299 | 300 | 276 |
Post RS Errors | 291 | 279 | 281 | 290 | 301 | 291 | 292 | 273 |
Upstream US-1 US-2 US-3 US-4
Channel Type | 2.0 | 2.0 | 2.0 | 2.0 |
Channel ID | 2 | 4 | 3 | 1 |
Frequency (Hz) | 53700000 | 39400000 | 46200000 | 60300000 |
Ranging Status | Success | Success | Success | Success |
Modulation | 64QAM | 64QAM | 64QAM | 64QAM |
Symbol Rate (Sym/sec) | 5120000 | 5120000 | 5120000 | 5120000 |
Mini-Slot Size | 2 | 2 | 2 | 2 |
Power Level (dBmV) | 48.54 | 46.79 | 47.29 | 49.54 |
T1 Timeouts | 0 | 0 | 0 | 0 |
T2 Timeouts | 0 | 0 | 0 | 0 |
T3 Timeouts | 0 | 0 | 0 | 0 |
T4 Timeouts | 0 | 0 | 0 | 0 |
Upstream Burst Req(1) Init Maint(3) Per Maint(4) Adv Short(9) Adv Long(10) Adv UGS(11)
Modulation Type | 16QAM | QPSK | 16QAM | 64QAM | 64QAM | 16QAM |
Differential Encoding | OFF | OFF | OFF | OFF | OFF | OFF |
Preamble Length | 56 | 640 | 384 | 104 | 104 | 104 |
Preamble Value Offset | 652 | 0 | 0 | 716 | 716 | 716 |
FEC Error Correction (T) | 0 | 5 | 5 | 10 | 16 | 5 |
FEC Codeword Information Bytes (K) | 16 | 34 | 34 | 81 | 223 | 86 |
Maximum Burst Size | 0 | 0 | 0 | 3 | 255 | 255 |
Guard Time Size | 8 | 48 | 48 | 8 | 8 | 8 |
Last Codeword Length | Fixed | Fixed | Fixed | Shortened | Shortened | Shortened |
Scrambler On/Off | ON | ON | ON | ON | ON | ON |
General Configuration
Network Access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | EuroDOCSIS 3.0 |
Config File |
Primary Downstream Service Flow
SFID | 46690 |
Max Traffic Rate | 230000061 bps |
Max Traffic Burst | 42600 bytes |
Min Traffic Rate | 0 bps |
Primary Upstream Service Flow
SFID | 46689 |
Max Traffic Rate | 22000061 bps |
Max Traffic Burst | 42600 bytes |
Min Traffic Rate | 0 bps |
Max Concatenated Burst | 42600 bytes |
Scheduling Type | Best Effort |
Right now the modem is working fine and I'm getting the correct speeds when I check. However I really don't want to see this problem keep repeating. Especially when it happened today at 3:30pm and it was nearly 7:30pm before my speed was back to normal.
on 04-08-2021 11:43
Thanks for the update cwatty, monitor this going forward and let us know if you need us again in the future.
Rob