Participant

Really high ping (300+) during prime time (4pm-1am)

About a month ago I started getting really high ping during the times listed in the title.  Normal ping is around 20-40. I have the Ultimate 200 package. My next door neighbor has TWC as awell and doesn't have any problems.

 

Here's some modem info that is usually asked for:

 

MODEM MODEL: DG1670A

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 116573.00 MHz-2.30 dBmV38.98 dB256QAM229090735681730
Downstream 22489.00 MHz-1.60 dBmV40.37 dB256QAM196018225111370
Downstream 33495.00 MHz-1.60 dBmV40.37 dB256QAM196430728371420
Downstream 44501.00 MHz-2.10 dBmV38.98 dB256QAM195615481491340
Downstream 55507.00 MHz-2.50 dBmV40.95 dB256QAM197099854381450
Downstream 66513.00 MHz-2.60 dBmV40.37 dB256QAM195557835301050
Downstream 77519.00 MHz-2.30 dBmV38.98 dB256QAM19705035043980
Downstream 88525.00 MHz-2.40 dBmV40.37 dB256QAM189405234111220
Downstream 99531.00 MHz-2.40 dBmV40.37 dB256QAM195148457191350
Downstream 1010537.00 MHz-2.30 dBmV38.61 dB256QAM19536273725990
Downstream 1111543.00 MHz-2.50 dBmV38.98 dB256QAM19616149411970
Downstream 1212549.00 MHz-2.60 dBmV38.98 dB256QAM194670175561190
Downstream 1313555.00 MHz-2.80 dBmV38.98 dB256QAM196039157981330
Downstream 1414561.00 MHz-2.80 dBmV38.98 dB256QAM192365786971230
Downstream 1515567.00 MHz-2.50 dBmV40.37 dB256QAM197067468931160
Downstream 161483.00 MHz-1.40 dBmV40.37 dB256QAM198896592401170

 

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 1730.60 MHz42.75 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 2837.00 MHz44.00 dBmVDOCSIS2.0 (ATDMA)2560 kSym/s16QAM
Upstream 3519.40 MHz41.00 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM
Upstream 4624.20 MHz41.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM

 

Date TimeEvent IDEvent LevelDescription
7/28/2016 9:12680106006DHCP Renew - lease parameters tftp file-?BEWGlxyYaz3bS4IK_xn_@Cv8Z_wzBcPUulk7pbFXR9BtWPB+2+Pd+ modified;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
7/28/2016 13:36820002003No Ranging Response received - T3 time-out;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
7/31/2016 21:12680106006DHCP Renew - lease parameters time server-72.183.77.58;tftp file-?BEWGlxyYaz3bS4IK_xn_@Cv8Z_03_fXatYPZTLDVD3cKy5l66hNX_ modified;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
7/31/2016 23:27820002003No Ranging Response received - T3 time-out;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/5/2016 20:49680106006DHCP Renew - lease parameters time server-72.183.82.28;tftp file-?BEWGlxyYaz3bS4IK_xn_@Cv8Z_6NoClytyLGQDrcikWVh48iNGfb_ modified;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/6/2016 22:35820002003No Ranging Response received - T3 time-out;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/9/2016 8:49680106006DHCP Renew - lease parameters time server-72.183.77.18;tftp file-?BEWGlxyYaz3bS4IK_xn_@Cv8Z_5cx7VvRsXGB_zNKiyxMbPviT993 modified;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/9/2016 9:03820002003No Ranging Response received - T3 time-out;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/9/2016 11:12840007005RCS Partial Service;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/9/2016 11:2224171643086Unit has been restored to factory defaults from a software issued command;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/11/2016 8:16820002003No Ranging Response received - T3 time-out;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/12/2016 22:20680106006DHCP Renew - lease parameters time server-72.183.82.28;tftp file-?BEWGlxyYaz3bS4IK_xn_@Cv8Z_2lHkxL9eE47LxaycQqPJCHFtdHf modified;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/15/2016 11:34820002003No Ranging Response received - T3 time-out;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/16/2016 10:20680106006DHCP Renew - lease parameters time server-72.183.77.58;tftp file-?BEWGlxyYaz3bS4IK_xn_@Cv8Z__NJr1vuMT5xbeabSo_5BiJ1MTk8 modified;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/16/2016 20:54820002003No Ranging Response received - T3 time-out;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/19/2016 22:20680106006DHCP Renew - lease parameters time server-72.183.77.18;tftp file-?BEWGlxyYaz3bS4IK_xn_@Cv8Z_0v8rzQoLUVmrR3GPQgyEW4G6f9_ modified;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/20/2016 13:3024171643086Unit has been restored to factory defaults from a software issued command;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/20/2016 23:15820002003No Ranging Response received - T3 time-out;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/23/2016 10:20680106006DHCP Renew - lease parameters tftp file-?BEWGlxyYaz3bS4IK_xn_@Cv8Z_xCiPo3Kdck8wliaBCepnLoBXfxX modified;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;
8/23/2016 12:51820002003No Ranging Response received - T3 time-out;CM-MAC=98:6b:3d:db:4b:82;CMTS-MAC=00:17:10:88:3d:4a;CM-QOS=1.1;CM-VER=3.0;

 

If you need anything else let me know.

17 REPLIES 17
Expert

Re: Really high ping (300+) during prime time (4pm-1am)

You shouldn't be doing this:

8/20/2016 13:3024171643086Unit has been restored to factory defaults from a software issued command

 

Is anything trying to run IPv6?

 Is this speed measured using a wired connection?

 What sort of router?

Are any devices running cloud, sync or onedrive?

 

Levels look good, but are you getting multiple T3-T4 errors a day?

Some of the logs are having issues and write over repetative errrors.

 

Participant

Re: Really high ping (300+) during prime time (4pm-1am)

The factory default is from when I messed with some settings to try and fix the problem myself. I ended up just putting everything back to how it was, and then disabling the IPv6 after. It's a wired connection. The problem was around for weeks before I even tried anything in the settings. The router is a 2 in 1 modem/router from TWC, the model is in the first post above all the logs. No cloud/sync/onedrive. I'm not really sure what the errors are but I don't get any popup errors or anything. Just the ping problem for most of the day.

Helper

Re: Really high ping (300+) during prime time (4pm-1am)

Is this a signal page when things were acting up, during prime time? If not repost signal levels when everything is all messed up, those numbers look good but can be decieving if not real time when the problem is happening.

 

A borderline signal might show as ok ,,, until the neighbors are all on, watch for the upstream channels to rise at night during prime time,, if t hat is the case you have a cut or noise on your line.

Participant

Re: Really high ping (300+) during prime time (4pm-1am)

I'm pretty sure it is yea. I'll take another one today when it starts acting up just to be sure.

Participant

Re: Really high ping (300+) during prime time (4pm-1am)

Here you go, this is during the ping problem.

 

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 116573.00 MHz-3.00 dBmV38.98 dB256QAM241815424845464148
Downstream 22489.00 MHz-2.00 dBmV39.85 dB256QAM20671692906709126909
Downstream 33495.00 MHz-2.00 dBmV40.95 dB256QAM20687629771405430474
Downstream 45507.00 MHz-2.80 dBmV40.37 dB256QAM2061330077210
Downstream 56513.00 MHz-2.90 dBmV40.37 dB256QAM2075755949020
Downstream 67519.00 MHz-2.70 dBmV38.98 dB256QAM2061041580910
Downstream 78525.00 MHz-2.70 dBmV40.37 dB256QAM2078560137820
Downstream 89531.00 MHz-2.80 dBmV40.37 dB256QAM2001202219320
Downstream 910537.00 MHz-2.70 dBmV38.98 dB256QAM2054568854210
Downstream 1011543.00 MHz-3.10 dBmV38.98 dB256QAM2056924977170
Downstream 1112549.00 MHz-3.40 dBmV38.61 dB256QAM2064590213330
Downstream 1213555.00 MHz-3.50 dBmV38.98 dB256QAM2048105950610
Downstream 1314561.00 MHz-3.40 dBmV38.98 dB256QAM2062593614720
Downstream 1415567.00 MHz-3.10 dBmV38.98 dB256QAM2027316235610
Downstream 151483.00 MHz-1.80 dBmV40.37 dB256QAM20787996136110
Downstream 1617579.00 MHz-2.90 dBmV38.98 dB256QAM2100123029110
Reset FEC Counters

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 1730.60 MHz42.75 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 2837.00 MHz44.00 dBmVDOCSIS2.0 (ATDMA)2560 kSym/s16QAM
Upstream 3519.40 MHz41.00 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM
Upstream 4624.20 MHz41.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Expert

Re: Really high ping (300+) during prime time (4pm-1am)

You have serious broadcast tv ingress on 489 mHz from local broadcast tv ch 17..

 What's your zip code? I can look it up

 

 

 something is corroded or loose or there's a surge protector outlet strip or ups inlinewith the coax.

all connections should be a tad more than finger tight.

 

Participant

Re: Really high ping (300+) during prime time (4pm-1am)

78154
Expert

Re: Really high ping (300+) during prime time (4pm-1am)

You have relatively strong tv stations on ch 16&18 which may be causing the ingress issues.

 18 is the 495 mHz channel and it's affected as well.

TWC needs to fix whatevers chewed up, corroded or loose.

 http://www.tvfool.com/?option=com_wrapper&Itemid=29&q=id%3de2cb9c2d445081

Participant

Re: Really high ping (300+) during prime time (4pm-1am)

So I should call them and tell them what? That I have a chewed up, corroded, or loose line and I need them to come fix it?