on 24-06-2024 20:03
Hi all,
Sure there's a fair few threads on this topic but don't really have much time to look into it much myself at the moment and hoping this is best way for me to get someone to take a look at my connection from the VM side of things.
Been noticing a stutter/packet loss whilst gaming mostly but actually I notice it also when typing in google/youtube etc.
Anyhow, first time I've looked at the router page for some time and it says "Partial Service (US Only)". This is also paired with alot of T3 timeouts in the network log and wondered if it's linked. Feel like I've had some T3 timeouts for a number of years but this appears to be very frequent. Appreciate any advance. Posted below is my router stats. Thanks!
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 315000000 | 8 | 40 | 256 qam | 23 |
2 | 139000000 | 8 | 40 | 256 qam | 1 |
3 | 147000000 | 7.9 | 40 | 256 qam | 2 |
4 | 155000000 | 8 | 40 | 256 qam | 3 |
5 | 163000000 | 7.8 | 40 | 256 qam | 4 |
6 | 171000000 | 8.1 | 40 | 256 qam | 5 |
7 | 179000000 | 8 | 40 | 256 qam | 6 |
8 | 187000000 | 7.9 | 40 | 256 qam | 7 |
9 | 195000000 | 7.8 | 40 | 256 qam | 8 |
10 | 203000000 | 7.8 | 40 | 256 qam | 9 |
11 | 211000000 | 7.8 | 40 | 256 qam | 10 |
12 | 219000000 | 7.8 | 40 | 256 qam | 11 |
13 | 227000000 | 7.9 | 40 | 256 qam | 12 |
14 | 235000000 | 7.9 | 40 | 256 qam | 13 |
15 | 243000000 | 7.8 | 40 | 256 qam | 14 |
16 | 251000000 | 8 | 40 | 256 qam | 15 |
17 | 259000000 | 8.1 | 40 | 256 qam | 16 |
18 | 267000000 | 8.4 | 40 | 256 qam | 17 |
19 | 275000000 | 8.4 | 40 | 256 qam | 18 |
20 | 283000000 | 8.3 | 40 | 256 qam | 19 |
21 | 291000000 | 8 | 40 | 256 qam | 20 |
22 | 299000000 | 8 | 40 | 256 qam | 21 |
23 | 307000000 | 8.1 | 40 | 256 qam | 22 |
24 | 323000000 | 8 | 40 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 5 | 0 |
2 | Locked | 40.3 | 6 | 0 |
3 | Locked | 40.3 | 4 | 0 |
4 | Locked | 40.9 | 6 | 0 |
5 | Locked | 40.3 | 11 | 0 |
6 | Locked | 40.3 | 6 | 0 |
7 | Locked | 40.3 | 5 | 0 |
8 | Locked | 40.9 | 4 | 0 |
9 | Locked | 40.3 | 18 | 0 |
10 | Locked | 40.3 | 5 | 0 |
11 | Locked | 40.3 | 7 | 0 |
12 | Locked | 40.9 | 5 | 0 |
13 | Locked | 40.3 | 6 | 0 |
14 | Locked | 40.9 | 6 | 0 |
15 | Locked | 40.9 | 0 | 0 |
16 | Locked | 40.3 | 0 | 0 |
17 | Locked | 40.9 | 5 | 0 |
18 | Locked | 40.9 | 5 | 0 |
19 | Locked | 40.3 | 5 | 0 |
20 | Locked | 40.9 | 5 | 0 |
21 | Locked | 40.3 | 0 | 0 |
22 | Locked | 40.9 | 5 | 0 |
23 | Locked | 40.9 | 6 | 0 |
24 | Locked | 40.9 | 0 | 0 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 49599986 | 45.5 | 5120 | 64 qam | 1 |
2 | 23600004 | 47 | 5120 | 64 qam | 5 |
3 | 36600012 | 45.5 | 5120 | 64 qam | 3 |
4 | 43100026 | 45.5 | 5120 | 64 qam | 2 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 24-06-2024 20:04
Time Priority Description
24/06/2024 19:59:57 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:59:57 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:57:57 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:57:57 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:55:57 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:55:57 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:53:57 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:53:57 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:51:58 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:51:57 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:49:58 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:49:58 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:47:58 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:47:58 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:45:58 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:45:58 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:44:18 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:44:18 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:42:9 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:39:55 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 24-06-2024 21:20
There are Zero obvious issues with the Upstream Hub data.
All Channels of the Hub 3 are on 64 QAM and there are ZERO T1 to T4 timeouts.
Looks like an overloaded game server is the real problem.
"typing in google/youtube" - this is character echo occurring on your computer.
on 24-06-2024 21:36
Hi Client62, thank you very much for taking a look at my post.
I'll try a few other games and see if I experience the same issue. It's just the others in my lobby said they weren't experiencing any lag/stutter.
Thanks again for the quick response.
on 25-06-2024 07:11
Test the VM service to a Router mode Hub(3/4/5/5x) + your device with the link below.
https://www.samknows.com/realspeed/
Once the test begins click on: Run full test to see all the stats.
The speed at the Hub should reflect your subscription.
The speed any WiFi device draws data at is limited by its data needs and technical abilities.