Help Understanding Modem Event Logs

[S0ulHer0]

Hello, recently I have noticed disruptions in internet that have affected both my extensive and general usage. At first I thought it was nothing but maybe lag on the servers of the games I played or anything else, but I've been seeing much longer load times for videos and even my email. I check out my modem and router and while I'm tech savvy, I'm not sure of what to make of my modem's event logs. Below are a few examples (I was gone on vacation for the long period of no logs)
Tue Aug 11 01:33:51 2015-Critical (3)-Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:70:45:9a;CMTS-MAC=00:0e:83:ca:88:23;CM-QOS=1.1;CM-VER=3.0;

Thu Jul 09 09:29:45 2015-Warning (5)-DBC-REQ denied - confirmation code 210: reject-dynamic-range-windowviolation;CM-MAC=6c:ca:08:70:45:9a;CMTS-MAC=00:0e:83:ca:88:23;CM-QOS=1.1;CM-VER=3.0;

Thu Jul 09 09:29:45 2015-Warning (5)-Dynamic Range Window violationTime Not Established
Notice (6) Honoring MDD; IP provisioning mode = IPv6

Thu Jul 09 09:27:45 2015-Critical (3)-Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:70:45:9a;CMTS-MAC=00:0e:83:ca:88:23;CM-QOS=1.1;CM-VER=3.0;

Thu Jul 09 09:26:47 2015-Critical (3)-SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=6c:ca:08:70:45:9a;CMTS-MAC=00:0e:83:ca:88:23;CM-QOS=1.1;CM-VER=3.0;

I'm not sure if this is something I should be concerned about. I have an Arris SURFboard 600 Series DOCSIS 3.0 that's about 2 months old so I don't think its the modems fault. I also checked for ping pockets and I have zero (not sure how reliable that is).

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

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 97 561000000 Hz 0.5 dBmV 39.3 dB 62 0
2 Locked QAM256 98 567000000 Hz 0.7 dBmV 39.3 dB 147 0
3 Locked QAM256 99 573000000 Hz 0.8 dBmV 39.4 dB 314 0
4 Locked QAM256 100 579000000 Hz 1.1 dBmV 39.3 dB 602 0
5 Locked QAM256 101 585000000 Hz 1.0 dBmV 39.2 dB 1967 0
6 Locked QAM256 102 591000000 Hz 1.1 dBmV 39.1 dB 3604 0
7 Locked QAM256 103 597000000 Hz 1.0 dBmV 39.0 dB 6061 0
8 Locked QAM256 104 603000000 Hz 1.3 dBmV 39.0 dB 8843 0
9 Locked QAM256 105 609000000 Hz 1.3 dBmV 39.0 dB 10010 0
10 Locked QAM256 106 615000000 Hz 1.4 dBmV 39.0 dB 13432 0
11 Locked QAM256 107 621000000 Hz 1.2 dBmV 39.0 dB 19152 0
12 Locked QAM256 108 627000000 Hz 1.2 dBmV 38.9 dB 26508 0
13 Locked QAM256 109 633000000 Hz 1.0 dBmV 38.9 dB 28874 0
14 Locked QAM256 110 639000000 Hz 1.1 dBmV 38.8 dB 38092 0
15 Locked QAM256 111 645000000 Hz 0.9 dBmV 38.8 dB 49372 0
16 Locked QAM256 112 651000000 Hz 1.0 dBmV 38.7 dB 60372 0

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 4 5120 Ksym/sec 16200000 Hz 51.5 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 35700000 Hz 54.0 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 29200000 Hz 54.0 dBmV
4 Locked ATDMA 3 5120 Ksym/sec 22700000 Hz 52.5 dBmV

And I guess I'll include my channel frequencies since It should help. I just really want to know if my connection errors are on my side, my hardware, or my connection. Any help or follow up questions will be greatly appreciated!

oh and yes Comcast is my provider

 

[bill001g]

This is hard to say normally you will have a log full of trash when you are having issues. Even if you are not around the modem powered on will talk to the cable company and if it has issues it will still create log entries. I am not sure you have a modem issue.

The upstream power numbers are near the upper end of the recommended values but I don't think you are above.

Still all you can really do to fix these is make sure your cable connection are clean and dry and you have as few splitters in the path as you can. Anything else only the cable company would have to check with their meters.

What you can do is open a cmd window in the background and run a continuous ping to common server like 8.8.8.8 or 4.2.2.2. When you think you are having issues you want to check this window for packet loss or even high latency spikes.

Still you should see problems on the speedtest sites if you are getting errors. In addition to the speed being slower than what you are suppose to get the graph of packet transfer rates will jump all over the place.

 

[S0ulHer0]

Thank you so much! I knew that it wasn't my routers fault and that I was receiving less frequency than I should be. To be honest, I feel like the problem resides with the wires and Comcast's signal than with my equipment. Thank you for reassuring my suspicions. Comcast needs to come over and poke around the cables or I'm gonna demand an upgrade or refund of some sort.