For reference, the graph below displays my latency to the CMTS (hop 2 in the traceroute). This amount of latency and jitter is unacceptable, spurious packet loss is visible also. The Admin, Info data is looking good, I just wanted to verify that the correct lease time (1 week) is in use, which is the case. Event Type Code: 16 Chan ID: 33 DSID: N/A MAC Addr: N/A OFDM/OFDMA Profile ID: 3. SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing CM-MAC=6c:ff:ce:fb:87:a7 CMTS-MAC=00:17:10:9f:d0:88 CM-QOS=1.1 CM-VER=3.1 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing CM-MAC=6c:ff:ce:fb:87:a7 CMTS-MAC=00:00:00:00:00:00 CM-QOS=1.1 CM-VER=3.1 DS Chan ID: 32 Previous Profile: New Profile: 1 2 3. REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value CM-MAC=6c:ff:ce:fb:87:a7 CMTS-MAC=00:17:10:9f:d0:88 CM-QOS=1.1 CM-VER=3.1 ĭS profile assignment change. REGISTRATION COMPLETE - Waiting for Operational status Started Unicast Maintenance Ranging - No Response received - T3 time-out CM-MAC=6c:ff:ce:fb:87:a7 CMTS-MAC=00:17:10:9f:d0:88 CM-QOS=1.1 CM-VER=3.1

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out CM-MAC=6c:ff:ce:fb:87:a7 CMTS-MAC=00:17:10:9f:d0:88 CM-QOS=1.1 CM-VER=3.1 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW CM-MAC=6c:ff:ce:fb:87:a7 CMTS-MAC=00:17:10:9f:d0:88 CM-QOS=1.1 CM-VER=3.1

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1

Ping test by ookla