on 06-04-2023 12:44
Hello,
Whenever I try to play games online, ping keeps spiking intermittently throughout the whole day averaging from 25-40 ms to 1000+ ms for a couple of seconds combined with some packet loss. It really affects my gaming experience heavily in ping-sensitive environments such as first-person shooters and fighting games; it's extremely frustrating.
Any assistance to fix this problem would be great. 👍
- TK_Switch
p.s. - I have a Gig1 broadband only package with a Hub 5 and wired.
on 06-04-2023 14:22
Find out how much Latency & Packet Loss you have on your connection to the public internet.
What every you see in a game that is above the baseline for your internet connection is due to the distance to the game servers plus their performance and load balancing.
https://www.samknows.com/realspeed/
Once the test begins click on: Run full test to see all the stats.
on 06-04-2023 16:31
I ran the tests and everything seems perfect.
The problem persists with the internet overall as it affects the whole household, not just gaming when the ping spikes occur.
08-04-2023 01:29 - edited 08-04-2023 01:34
I opened up the routers page and it seems the Ranged Upstream Channel (Hz) has failed. Is this okay?
Cable Modem StatusItem Status Comments
Acquired Downstream Channel(Hz) | 330000000 | Locked |
Ranged Upstream Channel(Hz) | 0 | Failed |
Provisioning State | Online | Operational |
The rest of the routers status:
Downstream bonded channels
1 | 330000000 | 6.4 | 39 | QAM 256 | 25 |
2 | 138000000 | 6.2 | 40 | QAM 256 | 1 |
3 | 146000000 | 6.1 | 40 | QAM 256 | 2 |
4 | 154000000 | 6 | 40 | QAM 256 | 3 |
5 | 162000000 | 6 | 40 | QAM 256 | 4 |
6 | 170000000 | 5.7 | 40 | QAM 256 | 5 |
7 | 178000000 | 5.7 | 40 | QAM 256 | 6 |
8 | 186000000 | 6.1 | 40 | QAM 256 | 7 |
9 | 194000000 | 6.3 | 40 | QAM 256 | 8 |
10 | 202000000 | 6.1 | 39 | QAM 256 | 9 |
11 | 210000000 | 6.5 | 39 | QAM 256 | 10 |
12 | 218000000 | 6.6 | 40 | QAM 256 | 11 |
13 | 226000000 | 6.3 | 40 | QAM 256 | 12 |
14 | 234000000 | 6.3 | 40 | QAM 256 | 13 |
15 | 242000000 | 6.4 | 40 | QAM 256 | 14 |
16 | 250000000 | 6.2 | 40 | QAM 256 | 15 |
17 | 258000000 | 6.1 | 39 | QAM 256 | 16 |
18 | 266000000 | 6 | 39 | QAM 256 | 17 |
19 | 274000000 | 6 | 39 | QAM 256 | 18 |
20 | 282000000 | 6 | 40 | QAM 256 | 19 |
21 | 290000000 | 5.7 | 40 | QAM 256 | 20 |
22 | 298000000 | 5.6 | 39 | QAM 256 | 21 |
23 | 306000000 | 6 | 39 | QAM 256 | 22 |
24 | 314000000 | 6.1 | 39 | QAM 256 | 23 |
25 | 322000000 | 6.2 | 39 | QAM 256 | 24 |
26 | 338000000 | 6.1 | 40 | QAM 256 | 26 |
27 | 346000000 | 5.6 | 40 | QAM 256 | 27 |
28 | 354000000 | 5.4 | 40 | QAM 256 | 28 |
29 | 362000000 | 4.6 | 40 | QAM 256 | 29 |
30 | 370000000 | 6.1 | 40 | QAM 256 | 30 |
31 | 378000000 | 6.1 | 40 | QAM 256 | 31 |
Downstream bonded channels
1 | Locked | 39 | 0 | 0 |
2 | Locked | 40 | 0 | 0 |
3 | Locked | 40 | 0 | 0 |
4 | Locked | 40 | 1 | 0 |
5 | Locked | 40 | 4 | 0 |
6 | Locked | 40 | 4 | 0 |
7 | Locked | 40 | 0 | 0 |
8 | Locked | 40 | 0 | 0 |
9 | Locked | 40 | 0 | 0 |
10 | Locked | 39 | 0 | 0 |
11 | Locked | 39 | 0 | 0 |
12 | Locked | 40 | 0 | 0 |
13 | Locked | 40 | 0 | 0 |
14 | Locked | 40 | 0 | 0 |
15 | Locked | 40 | 0 | 0 |
16 | Locked | 40 | 0 | 0 |
17 | Locked | 39 | 0 | 0 |
18 | Locked | 39 | 0 | 0 |
19 | Locked | 39 | 0 | 0 |
20 | Locked | 40 | 0 | 0 |
21 | Locked | 40 | 3 | 0 |
22 | Locked | 39 | 1 | 0 |
23 | Locked | 39 | 0 | 0 |
24 | Locked | 39 | 0 | 0 |
25 | Locked | 39 | 0 | 0 |
26 | Locked | 40 | 0 | 0 |
27 | Locked | 40 | 2 | 0 |
28 | Locked | 40 | 0 | 0 |
29 | Locked | 40 | 1 | 0 |
30 | Locked | 40 | 0 | 0 |
31 | Locked | 40 | 0 | 0 |
08-04-2023 01:34 - edited 08-04-2023 01:36
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
Not Available
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
Not Available
Network Log
07-04-2023 22:25:12 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-04-2023 22:25:12 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-04-2023 21:22:39 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-04-2023 21:22:39 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-04-2023 10:59:16 | notice | CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: 264940; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-04-2023 10:59:12 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-04-2023 10:59:12 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-04-2023 10:59:12 | warning | Unicast DSID PSN startup error |
07-04-2023 10:59:08 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
07-04-2023 10:59:08 | warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-04-2023 10:59:02 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-04-2023 10:58:08 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-04-2023 10:58:06 | notice | Honoring MDD; IP provisioning mode = IPv4 |
07-04-2023 10:58:01 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-04-2023 10:58:00 | critical | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-04-2023 10:57:51 | 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.1; |
06-04-2023 15:21:04 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-04-2023 21:34:49 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-04-2023 21:34:49 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-04-2023 20:20:48 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-04-2023 20:20:48 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-04-2023 19:13:49 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 08-04-2023 07:40
This indicates the Upstream channels are missing. Call 0800 561 0061 check for a local fault.
Ranged Upstream Channel(Hz) | 0 | Failed |
on 10-04-2023 16:11
Hi @TK_switch,
Thank you for your posts and welcome to our community forums. We're here to help.
I'm very sorry to hear of the issues you've experienced with your connection recently. Are these ongoing today? If they are, would you mind clarifying what troubleshooting and diagnostics you've performed thus far?
Thanks,
on 10-04-2023 17:37
Hello @Zack_R
The issues has been ongoing for couple of months now. I have tried all these methods but nothing has improved:
on 10-04-2023 17:56
Hello,
Have the Upstream Channels reconnected ?
There should be 4 or more DOCSIS 3.0 upstream channels.
on 10-04-2023 18:00
Hello
No. The upstream provisional channel still shows as "Failed" and the four upstream channels are not available.