Virgin Media
My Virgin Media
Mobile Your Account
- Virgin Media Community
- :
- Broadband
- :
- Gaming Support
- :
- constant CSGO Rubber banding, ping spikes
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Email this message to a friend
- Flag for a moderator
constant CSGO Rubber banding, ping spikes
on 16-01-2021 17:11
So, I have been using virgin for 8 years plus we've had are ups and downs but not as bad as it's been as of late. it was always perfect for gaming, I had good ping no lag unless it was server side but now since the start of 2020 I have been lagging/rubber banding at a constant basis everyday.
(fyi the first two lines are me explaining the problem the rest is me complaining)
Are early problem was constant disconnecting for 5 minuntes, the house would lose it's internet. we had many call out during 2020 and it was frustrating, we could see we had a problem and the person on the other end of the phone would agree and say something about the downstream is not right, we'd get a tech out to the house and he'd plug a cable into the modem and he'd see no issues, then tell me nothing is wrong and then leave, then in that same day I was gaming and it happened again so I called up and again talked to someone and again the tech came out, same story he saw nothing.
I mention this becuase It's embarsising and a waste of time having them come out and then leave without doing anything, we had 3 call outs in a month and at the end a out side node was fixed.
At a point after a bit of frustrating call out we had them put us on a 7 day watchlist and after the 9th day we got a call out saying that the neighbourhood node across the street was being looked at, and we ever constantly saying to the techs that it's possibly coming from outside but they wouldn't listen. that node seemed to have fixed the constant disconnecting.
Okay some specs.
I am running on ethernet, it shouldn't be a computer issue, 256down/25up is the speed.
we now have 3 working from home and one of those workers is a heavy Netflix watcher, but I don't think these factors should be the cause of this issue.
I saw in a similar post that the tech asks for BQM I have done nearly 24 hours and I have a feeling this is going to say all is perfect and no issues here.
onto my gaming notes.
I rubber band constantly, my ping is 40-60 to German/Netherland, anything other than that i get more. I play csgo on faceit, esportal, MM all have the same lag.
I notice the lag when I commit to a full spray and i can feel and hear my gun shooting slower it's super annoying,
I have collected 3 examples and 1 control of my gameplay issues. the 3 lag clips were capture on my twitch stream. as you can hear and see the bullets are not exiting the gun as fast as they should, I have found single fire weapons are still usable, but I still have some lag.
The first clip I had 49 ping, I assume it is the same for the rest.
to be fair I also have a second pc that I will put it to the test as well.
I encountered the same issues
Last two clips I could feel the lag, but it might not translate well in the video.
I guess that’s all for now, please any suggestions or any clarifications would be a help.
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Email this message to a friend
- Flag for a moderator
Re: constant CSGO Rubber banding, ping spikes
on 16-01-2021 17:17
Nobody will sat that BQM is perfect, it's a nightmare. Initial thoughts are that is a noise or power fault. Connect to the hub by clicking on this link http://192.168.0.1/ That should pull up the log in page for the hub. But don't log in, just click on the link "Check router status" That'll bring up a window with five tabs. Open the Downstream tab. Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here. Post that, do the same for the Upstream and Network log. You'll get an error message when you post the Network log, just click on "post" a second time. Don't use screenshots, too often they are not legible.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Email this message to a friend
- Flag for a moderator
Re: constant CSGO Rubber banding, ping spikes
on 16-01-2021 17:19
@AndrewTYZ wrote:So, I have been using virgin for 8 years plus we've had are ups and downs but not as bad as it's been as of late. it was always perfect for gaming, I had good ping no lag unless it was server side but now since the start of 2020 I have been lagging/rubber banding at a constant basis everyday.
(fyi the first two lines are me explaining the problem the rest is me complaining)
Are early problem was constant disconnecting for 5 minuntes, the house would lose it's internet. we had many call out during 2020 and it was frustrating, we could see we had a problem and the person on the other end of the phone would agree and say something about the downstream is not right, we'd get a tech out to the house and he'd plug a cable into the modem and he'd see no issues, then tell me nothing is wrong and then leave, then in that same day I was gaming and it happened again so I called up and again talked to someone and again the tech came out, same story he saw nothing.
I mention this becuase It's embarsising and a waste of time having them come out and then leave without doing anything, we had 3 call outs in a month and at the end a out side node was fixed.
At a point after a bit of frustrating call out we had them put us on a 7 day watchlist and after the 9th day we got a call out saying that the neighbourhood node across the street was being looked at, and we ever constantly saying to the techs that it's possibly coming from outside but they wouldn't listen. that node seemed to have fixed the constant disconnecting.
Okay some specs.
I am running on ethernet, it shouldn't be a computer issue, 256down/25up is the speed.
we now have 3 working from home and one of those workers is a heavy Netflix watcher, but I don't think these factors should be the cause of this issue.
I saw in a similar post that the tech asks for BQM I have done nearly 24 hours and I have a feeling this is going to say all is perfect and no issues here.
onto my gaming notes.
I rubber band constantly, my ping is 40-60 to German/Netherland, anything other than that i get more. I play csgo on faceit, esportal, MM all have the same lag.
I notice the lag when I commit to a full spray and i can feel and hear my gun shooting slower it's super annoying,
I have collected 3 examples and 1 control of my gameplay issues. the 3 lag clips were capture on my twitch stream. as you can hear and see the bullets are not exiting the gun as fast as they should, I have found single fire weapons are still usable, but I still have some lag.
The first clip I had 49 ping, I assume it is the same for the rest.
to be fair I also have a second pc that I will put it to the test as well.
I encountered the same issues
Last two clips I could feel the lag, but it might not translate well in the video.
I guess that’s all for now, please any suggestions or any clarifications would be a help.
Your BQM is terrible:
I would say your area is oversubscribed/utilized, however it normally settles in the early hours.
You should access your HUB on http://192.168.0.1 navigate to 'Advanced Settings/Tools/Network Status' and post the 'Upstream', 'Downstream', and 'Network Log' tab data.
We can check if the HUB stats are in spec, or not.
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Email this message to a friend
- Flag for a moderator
Re: constant CSGO Rubber banding, ping spikes
on 16-01-2021 17:51
That BQM isn't showing over-utilisation, that's a continuous performance fault. It is possible that with that out of the way the BQM then might reveal a utilisation problem, but we'll only know that when the main fault has been identified and resolved, and in the meantime there's not sufficient evidence to decide.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Email this message to a friend
- Flag for a moderator
Re: constant CSGO Rubber banding, ping spikes
on 16-01-2021 18:42
Power fault was orginally suggested but it seemed that was fixed from memory. The power fault was the initial internet going down for 5 mins at a time and actually Last night it did go down for 5 seconds.
when clicking the link i only have an option for password and log in
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Email this message to a friend
- Flag for a moderator
Re: constant CSGO Rubber banding, ping spikes
on 16-01-2021 18:49
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 174000000 | -1 | 37 | 256qam | 1 |
2 | 182000000 | -1 | 37 | 256qam | 2 |
3 | 190000000 | -1 | 36 | 256qam | 3 |
4 | 206000000 | 0 | 37 | 256qam | 5 |
5 | 222000000 | 0 | 37 | 256qam | 7 |
6 | 230000000 | 0 | 37 | 256qam | 8 |
7 | 238000000 | 0 | 37 | 256qam | 9 |
8 | 251000000 | 0 | 37 | 256qam | 10 |
9 | 259000000 | 0 | 37 | 256qam | 11 |
10 | 474000000 | 5 | 38 | 256qam | 12 |
11 | 490000000 | 6 | 38 | 256qam | 14 |
12 | 498000000 | 6 | 38 | 256qam | 15 |
13 | 514000000 | 6 | 38 | 256qam | 17 |
14 | 522000000 | 7 | 38 | 256qam | 18 |
15 | 538000000 | 7 | 38 | 256qam | 20 |
16 | 554000000 | 7 | 38 | 256qam | 22 |
17 | 714000000 | 9 | 37 | 256qam | 23 |
18 | 722000000 | 9 | 37 | 256qam | 24 |
19 | 738000000 | 9 | 37 | 256qam | 26 |
20 | 746000000 | 8 | 36 | 256qam | 27 |
21 | 754000000 | 8 | 36 | 256qam | 28 |
22 | 762000000 | 8 | 36 | 256qam | 29 |
23 | 770000000 | 8 | 36 | 256qam | 30 |
24 | 786000000 | 8 | 36 | 256qam | 32 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 37.356 | 36278704793 | 4957 |
2 | Locked | 37.356 | 36275794920 | 4406 |
3 | Locked | 36.610 | 36275785648 | 4160 |
4 | Locked | 37.636 | 17877223892 | 914 |
5 | Locked | 37.636 | 17877225041 | 965 |
6 | Locked | 37.636 | 17877224413 | 1030 |
7 | Locked | 37.356 | 17877220118 | 1634 |
8 | Locked | 37.636 | 17877213091 | 1118 |
9 | Locked | 37.636 | 17877217494 | 662 |
10 | Locked | 38.605 | 17877224142 | 143 |
11 | Locked | 38.605 | 378362176 | 7 |
12 | Locked | 38.983 | 378361617 | 23 |
13 | Locked | 38.605 | 378362842 | 9 |
14 | Locked | 38.605 | 378361641 | 6 |
15 | Locked | 38.605 | 17877224778 | 82 |
16 | Locked | 38.605 | 14060853088 | 89 |
17 | Locked | 37.356 | 14060851845 | 379 |
18 | Locked | 37.356 | 14060853463 | 729 |
19 | Locked | 37.636 | 14060847840 | 1258 |
20 | Locked | 36.610 | 14060852364 | 1634 |
21 | Locked | 36.610 | 26037633735 | 6164 |
22 | Locked | 36.387 | 32142693652 | 11655 |
23 | Locked | 36.610 | 32142696145 | 15090 |
24 | Locked | 36.610 | 32553792739 | 14917 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 32800000 | 39 | 5.120 | 64qam | 2 |
2 | 60200000 | 41 | 5.120 | 64qam | 6 |
3 | 53600000 | 40 | 5.120 | 64qam | 5 |
4 | 46000000 | 40 | 5.120 | 64qam | 4 |
5 | 39400000 | 40 | 5.120 | 64qam | 3 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | 2.0 | 0 | 0 | 42 | 0 |
2 | 2.0 | 0 | 0 | 40 | 0 |
3 | 2.0 | 0 | 0 | 36 | 0 |
4 | 2.0 | 0 | 0 | 42 | 0 |
5 | 2.0 | 0 | 0 | 31 | 0 |
Time Priority Description
16-01-2021 17:24:21 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10-01-2021 01:08:29 | warning | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10-01-2021 00:31:31 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04-01-2021 18:12:02 | warning | [**:**:**:**:**:**][DFS] Radar signal detected, DFS sequence applied, channel changed from 100 to 36 |
04-01-2021 11:06:24 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01-01-1970 00:01:18 | notice | Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04-01-2021 09:48:20 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01-01-1970 00:01:18 | notice | Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04-01-2021 05:49:08 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26-12-2020 21:29:18 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26-12-2020 21:29:14 | notice | Illegal - Dropped FORWARD packet: src=192.168.0.75 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01-01-1970 00:01:17 | notice | Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26-12-2020 19:38:54 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14-12-2020 12:57:53 | warning | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14-12-2020 12:57:47 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14-12-2020 12:38:30 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13-11-2020 09:51:02 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01-01-1970 00:02:42 | notice | Illegal - Dropped FORWARD packet: src=192.168.0.10 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01-01-1970 00:01:17 | notice | Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13-11-2020 01:11:59 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03-11-2020 22:32:12 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Email this message to a friend
- Flag for a moderator
Re: constant CSGO Rubber banding, ping spikes
on 16-01-2021 18:50
I replied to another person with this so you can see that too at the bottom. Thanks
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Email this message to a friend
- Flag for a moderator
Re: constant CSGO Rubber banding, ping spikes
on 16-01-2021 19:55
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Email this message to a friend
- Flag for a moderator
Re: constant CSGO Rubber banding, ping spikes
on 16-01-2021 19:58
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 174000000 -1 37 256qam 1
2 182000000 -1 36 256qam 2
3 190000000 -1 36 256qam 3
4 206000000 0 37 256qam 5
5 222000000 0 37 256qam 7
6 230000000 0 37 256qam 8
7 238000000 0 37 256qam 9
8 251000000 0 37 256qam 10
9 259000000 0 37 256qam 11
10 474000000 5 38 256qam 12
11 490000000 6 38 256qam 14
12 498000000 6 38 256qam 15
13 514000000 6 38 256qam 17
14 522000000 6 38 256qam 18
15 538000000 7 38 256qam 20
16 554000000 7 38 256qam 22
17 714000000 9 37 256qam 23
18 722000000 9 37 256qam 24
19 738000000 9 37 256qam 26
20 746000000 8 36 256qam 27
21 754000000 8 36 256qam 28
22 762000000 8 36 256qam 29
23 770000000 8 36 256qam 30
24 786000000 8 36 256qam 32
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.356 36420414529 4978
2 Locked 36.610 36417504669 4412
3 Locked 36.610 36417495140 4178
4 Locked 37.636 18018933492 929
5 Locked 37.356 18018934618 976
6 Locked 37.636 18018934037 1035
7 Locked 37.636 18018929754 1649
8 Locked 37.636 18018922742 1137
9 Locked 37.356 18018927125 663
10 Locked 38.605 18018935462 148
11 Locked 38.605 520073440 7
12 Locked 38.983 520072883 23
13 Locked 38.983 520074124 10
14 Locked 38.605 520072864 7
15 Locked 38.983 18018936075 82
16 Locked 38.605 14202564356 89
17 Locked 37.356 14202563104 382
18 Locked 37.356 14202564678 735
19 Locked 37.356 14202559170 1270
20 Locked 36.610 14202562034 1642
21 Locked 36.387 26179343124 6185
22 Locked 36.610 32284403042 11690
23 Locked 36.610 32284405263 15134
24 Locked 36.610 32695501933 14959
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 32800000 39 5.120 64qam 2
2 60200000 41 5.120 64qam 6
3 53600000 40 5.120 64qam 5
4 46000000 40 5.120 64qam 4
5 39400000 40 5.120 64qam 3
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 2.0 0 0 42 0
2 2.0 0 0 40 0
3 2.0 0 0 36 0
4 2.0 0 0 42 0
5 2.0 0 0 31 0
Network Log
Time Priority Description
16-01-2021 17:24:21 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2021 01:08:29 warning Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2021 00:31:31 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04-01-2021 18:12:02 warning [**:**:**:**:**:**][DFS] Radar signal detected, DFS sequence applied, channel changed from 100 to 36
04-01-2021 11:06:24 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:18 notice Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04-01-2021 09:48:20 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:18 notice Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04-01-2021 05:49:08 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26-12-2020 21:29:18 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26-12-2020 21:29:14 notice Illegal - Dropped FORWARD packet: src=192.168.0.75 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:17 notice Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26-12-2020 19:38:54 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14-12-2020 12:57:53 warning Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14-12-2020 12:57:47 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14-12-2020 12:38:30 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13-11-2020 09:51:02 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:02:42 notice Illegal - Dropped FORWARD packet: src=192.168.0.10 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:17 notice Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13-11-2020 01:11:59 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03-11-2020 22:32:12 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Email this message to a friend
- Flag for a moderator
Re: constant CSGO Rubber banding, ping spikes
on 16-01-2021 19:59
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 174000000 -1 37 256qam 1
2 182000000 -1 36 256qam 2
3 190000000 -1 36 256qam 3
4 206000000 0 37 256qam 5
5 222000000 0 37 256qam 7
6 230000000 0 37 256qam 8
7 238000000 0 37 256qam 9
8 251000000 0 37 256qam 10
9 259000000 0 37 256qam 11
10 474000000 5 38 256qam 12
11 490000000 6 38 256qam 14
12 498000000 6 38 256qam 15
13 514000000 6 38 256qam 17
14 522000000 6 38 256qam 18
15 538000000 7 38 256qam 20
16 554000000 7 38 256qam 22
17 714000000 9 37 256qam 23
18 722000000 9 37 256qam 24
19 738000000 9 37 256qam 26
20 746000000 8 36 256qam 27
21 754000000 8 36 256qam 28
22 762000000 8 36 256qam 29
23 770000000 8 36 256qam 30
24 786000000 8 36 256qam 32
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.356 36420414529 4978
2 Locked 36.610 36417504669 4412
3 Locked 36.610 36417495140 4178
4 Locked 37.636 18018933492 929
5 Locked 37.356 18018934618 976
6 Locked 37.636 18018934037 1035
7 Locked 37.636 18018929754 1649
8 Locked 37.636 18018922742 1137
9 Locked 37.356 18018927125 663
10 Locked 38.605 18018935462 148
11 Locked 38.605 520073440 7
12 Locked 38.983 520072883 23
13 Locked 38.983 520074124 10
14 Locked 38.605 520072864 7
15 Locked 38.983 18018936075 82
16 Locked 38.605 14202564356 89
17 Locked 37.356 14202563104 382
18 Locked 37.356 14202564678 735
19 Locked 37.356 14202559170 1270
20 Locked 36.610 14202562034 1642
21 Locked 36.387 26179343124 6185
22 Locked 36.610 32284403042 11690
23 Locked 36.610 32284405263 15134
24 Locked 36.610 32695501933 14959
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 32800000 39 5.120 64qam 2
2 60200000 41 5.120 64qam 6
3 53600000 40 5.120 64qam 5
4 46000000 40 5.120 64qam 4
5 39400000 40 5.120 64qam 3
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 2.0 0 0 42 0
2 2.0 0 0 40 0
3 2.0 0 0 36 0
4 2.0 0 0 42 0
5 2.0 0 0 31 0
Network Log
Time Priority Description
16-01-2021 17:24:21 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2021 01:08:29 warning Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2021 00:31:31 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04-01-2021 18:12:02 warning [**:**:**:**:**:**][DFS] Radar signal detected, DFS sequence applied, channel changed from 100 to 36
04-01-2021 11:06:24 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:18 notice Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04-01-2021 09:48:20 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:18 notice Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04-01-2021 05:49:08 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26-12-2020 21:29:18 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26-12-2020 21:29:14 notice Illegal - Dropped FORWARD packet: src=192.168.0.75 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:17 notice Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26-12-2020 19:38:54 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14-12-2020 12:57:53 warning Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14-12-2020 12:57:47 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14-12-2020 12:38:30 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13-11-2020 09:51:02 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:02:42 notice Illegal - Dropped FORWARD packet: src=192.168.0.10 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:17 notice Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13-11-2020 01:11:59 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03-11-2020 22:32:12 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;