Community Forum

Random horrible lag spikes (gaming/voice chat)

New Poster

Random horrible lag spikes (gaming/voice chat)

Hello everyone, I seem to be having some connection issues currently on an off for the past 3 or 4 days. It's mostly while gamining, and using voice chat programs. First while gaming I play a game called world of warcraft. my MS seems to spike radomly, my normal ping is usually 50 ms i have seen it go as high as 30000 home which i believe is my actual ping and world which is blizzard servers. It has been happening since thursday of this week. The second issue is in a chat progam called discord, while in discord friends have told me that I sound Robotic and choppy; this seems to happen around the same time that my MS seems to spike in game.   I called comcast and spoke to a rep who told me that he saw nothing wrong with my service or modem. I just wanted to post my modem  stats to see if that is what is causing the issues.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 675000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK  
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed  

 

 
Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
28 Locked QAM256 675000000 Hz 2.5 dBmV 42.0 dB 60 10
1 Locked QAM256 513000000 Hz -2.6 dBmV 40.1 dB 138 119
2 Locked QAM256 519000000 Hz -2.3 dBmV 39.8 dB 149 120
3 Locked QAM256 525000000 Hz -2.3 dBmV 40.0 dB 100 98
4 Locked QAM256 531000000 Hz -2.7 dBmV 39.5 dB 84 81
5 Locked QAM256 537000000 Hz -2.4 dBmV 39.6 dB 87 60
6 Locked QAM256 543000000 Hz -2.7 dBmV 40.0 dB 94 58
7 Locked QAM256 555000000 Hz -2.5 dBmV 40.1 dB 70 76
8 Locked QAM256 561000000 Hz -1.8 dBmV 40.0 dB 75 51
9 Locked QAM256 567000000 Hz -1.5 dBmV 39.4 dB 96 55
10 Locked QAM256 573000000 Hz -1.6 dBmV 40.2 dB 69 48
11 Locked QAM256 579000000 Hz -2.7 dBmV 40.0 dB 59 58
12 Locked QAM256 585000000 Hz -2.7 dBmV 39.6 dB 77 51
13 Locked QAM256 591000000 Hz -1.8 dBmV 40.7 dB 59 53
14 Locked QAM256 597000000 Hz -0.9 dBmV 41.0 dB 58 50
15 Locked QAM256 603000000 Hz -0.9 dBmV 40.9 dB 55 40
16 Locked QAM256 609000000 Hz -0.4 dBmV 40.3 dB 66 28
17 Locked QAM256 615000000 Hz 0.1 dBmV 40.2 dB 76 10
18 Locked QAM256 621000000 Hz 0.4 dBmV 41.1 dB 53 31
19 Locked QAM256 627000000 Hz 0.5 dBmV 41.2 dB 78 21
20 Locked QAM256 633000000 Hz 0.9 dBmV 41.5 dB 63 39
21 Locked QAM256 639000000 Hz 1.2 dBmV 40.1 dB 57 24
22 Locked QAM256 645000000 Hz 1.4 dBmV 40.4 dB 63 8
23 Locked QAM256 651000000 Hz 1.6 dBmV 41.4 dB 53 15
24 Locked QAM256 657000000 Hz 2.1 dBmV 38.2 dB 68 10
26 Locked QAM256 663000000 Hz 2.2 dBmV 40.8 dB 53 12
27 Locked QAM256 669000000 Hz 2.2 dBmV 41.3 dB 61 13
29 Locked QAM256 681000000 Hz 2.3 dBmV 41.9 dB 91 32
25 Locked Other 762000000 Hz 1.8 dBmV 40.0 dB 927 0

 

 
Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 36 Locked SC-QAM 16600000 Hz 6400000 Hz 47.5 dBmV
2 33 Locked SC-QAM 35800000 Hz 6400000 Hz 46.3 dBmV
3 34 Locked SC-QAM 29400000 Hz 6400000 Hz 47.5 dBmV
4 35 Locked SC-QAM 23000000 Hz 6400000 Hz 49.0 dBmV

 

 

also here is the info from my event log

 

3-10-2018, 14:21:39 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:42 Notice(6) "Honoring MDD; IP provisioning mode = IPv6"
1-1-1970, 0:0:37 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:38 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 16:10:40 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:38 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 14:25:51 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 14:24:37 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 14:24:37 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 14:24:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 14:24:21 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 14:24:21 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 14:23:55 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 14:23:55 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 14:23:42 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 14:23:42 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 14:21:26 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 14:10:11 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:38 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
3-9-2018, 11:33:53 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:36 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
3-8-2018, 22:53:11 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-8-2018, 22:52:19 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-8-2018, 22:52:11 Critical(3) "REG RSP not received;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-8-2018, 22:52:11 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-8-2018, 22:52:8 Critical(3) "REG RSP not received;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-8-2018, 22:52:8 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-8-2018, 22:52:5 Critical(3) "REG RSP not received;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:1:11 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:58 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
3-8-2018, 21:6:30 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:1:2 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:41 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
3-8-2018, 21:4:30 Critical(3) "Resetting the cable modem due to docsDevResetNow"
3-8-2018, 21:2:3 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
3-8-2018, 20:31:59 Critical(3) "REG RSP not received;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:42 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:38 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
3-8-2018, 20:29:0 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:37 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
3-8-2018, 19:14:24 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:70:ec:91;CMTS-MAC=00:01:5c:6c:58:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-197
 
any help would be greatly aprechated as i would like to get back to gaming.
 
Thank you
New Poster

Re: Random horrible lag spikes (gaming/voice chat)

Are you located on the east coast or where that nor eastern just hit? The same thing is happening to me after this storm hit. I'm dealing with packet loss, along with my ping jumping around. If you were hit by any high winds or heavy rains around the time the issue started to happen, I'd have comcast send a tech out to inspect your wires outside because I'm in the same exact boat as you. They also said they see nothing wrong, but I know there is something off recently.

New Poster

Re: Random horrible lag spikes (gaming/voice chat)

on the east cost in Florida no real crazy weather, are your problems with world of warcraft as well or just your general internet usage?

New Poster

Re: Random horrible lag spikes (gaming/voice chat)

Not world of warcraft, but my friends say I go robotic in teamspeak and discord, and I get spikes of not being able to move in league of legends. Do you ever lose internet, or is it just ping spikes and such?

New Poster

Re: Random horrible lag spikes (gaming/voice chat)

its just crazy lag spikes no loss of service, going from like home 50ms-50 world ms to 3000-6000 on both or sometimes 375 home and 65ms world so i dont know if its on blizzards end, but it seems to happen around the time of all these T3 errors im getting from my modem, sometimes they seem like 3 or 4 times an hour and i had a good patch where i thought the lag was gone yesterday from 6pm till abaout 12 this afternoon, and i did not see a T3 error unless i restarted my modem during that time. I have Xfinity gigabit service and see no issues with speed.

New Poster

Re: Random horrible lag spikes (gaming/voice chat)

Well I can tell you that your upstream power levels are a bit high. When mine get that high, I lose my internet. I've been dealing with what you are dealing with now for probably 2 years. They always say it's working, but that's not always the case. Could be your modem, your cabling or splitters inside or out, or a problem on their end. It wouldn't hurt to schedule a tech visit for outside your home, as long as they don't come inside there is no service charge for their visit. That way it can either be fixed, or you know it's an inside issue most likely. If you can, you also want to eliminate any extra splitters or cables that aren't being used inside. What also helps is hooking up your modem with the least amount of connections/splitters between itself and where the outside cable comes in.