Observer

Ping issue since April 22 2016

I have had Time Warner Cable here in South East Alabama the Dothan area for about 7 years and for the longest the internet ping issue has never existed until mid April my speed results before the high ping issue started

 

http://www.speedtest.net/my-result/5243252451

after

 

http://imgur.com/a/No0Zf

 

I am from the Alabama South East Region!!!!

 

After around May til this day my ping issue has been pretty bad. On servers like Atlanta i used to get 16 ping but now i get 80 ping. every server i connect to is 40-60 ms higher than what it was before. I used to get lag spikes but thankfully i don't no more. I have no idea whats going on and i contacted customer support and they have no clue either and this seems to be an issue only in my area because i know a guy from northern Alabama he has charter and he seems to not have this issue and i hope someday it will change back to the way it has been before because I pay for my internet for a good decent price and here people have Fiber optic with faster speeds and lower ping with cheaper prices and i can't switch since i don't live on a main highway. I want to stay with Time Warner but you guys have to step it up and fix this ping issue because with the amount of money you guys make i would assume it should be going for fixing the lines to all these servers I want the people of Time Warner to be aware of this issue as i am not the only one having this issue in my area in fact everyone here with Time Warner has this issue because i know them i am friends with almost everyone down here and they all keep asking me is your internet sluggish too and i would agree. Also i dont understand how my ping is lower only in Chicago servers since i live across the United states from there pls someone also ask me why this happens.

PLS RESPOND if you know how to fix this issue or if you guys are currently aware of this issue and or working on this issue.

19 REPLIES 19
Expert

Re: Ping issue since April 22 2016

Copy and paste the modems signal level and error log pages, don't reset it first, need to see actual history.

 

Observer

Re: Ping issue since April 22 2016

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 18705.00 MHz-5.25 dBmV36.61 dB256QAM41105008102460
Downstream 21663.00 MHz-4.42 dBmV36.84 dB256QAM29485223562300
Downstream 32669.00 MHz-5.04 dBmV36.17 dB256QAM31754840432670
Downstream 43675.00 MHz-4.75 dBmV36.17 dB256QAM31634577532640
Downstream 54681.00 MHz-5.08 dBmV36.39 dB256QAM30147932872960
Downstream 65687.00 MHz-5.61 dBmV36.61 dB256QAM29349436812690
Downstream 76693.00 MHz-5.06 dBmV37.09 dB256QAM27754667102930
Downstream 87699.00 MHz-5.39 dBmV36.61 dB256QAM30556455162440

 

 

 

I got a ARRIS TG862

Below is the logs

 DOCSIS(CM) Events

 

Date TimeEvent IDEvent LevelDescription
8/24/2016 1:49680106006DHCP Renew - lease parameters time server-66.75.142.117;tftp file-?BEWGlzkAHdZHX1JMN_BC@TDfwQtv5lLJUwxey2G9_qm2zi_tSt9vz modified;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
8/27/2016 13:49680103004DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
8/27/2016 13:49680106006DHCP Renew - lease parameters time server-76.85.237.54;tftp file-?BEWGlzkAHdZHX1JMN_BC@TDfwQndJW6_0J9AbyOFMJKoDabYG5fB2 modified;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
8/31/2016 1:50680103004DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
8/31/2016 1:50680106006DHCP Renew - lease parameters tftp file-?BEWGlzkAHdZHX1JMN_BC@TDfwQjut0Xe8sU+mOxiof_XDsBR1Pz99 modified;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/3/2016 13:50680103004DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/3/2016 13:50680106006DHCP Renew - lease parameters time server-76.85.237.14;tftp file-?BEWGlzkAHdZHX1JMN_BC@TDfwQjKtwDXvuODvVTIx7IIB+kLzJg79 modified;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/7/2016 1:50680103004DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/7/2016 1:50680106006DHCP Renew - lease parameters time server-76.85.237.54;tftp file-?BEWGlzkAHdZHX1JMN_BC@TDfwQv4nkNGBdSJKAT2Eg802gNfmh_9e modified;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/8/2016 14:17820002003No Ranging Response received - T3 time-out;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/10/2016 13:50680103004DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/10/2016 13:50680106006DHCP Renew - lease parameters time server-76.85.237.14;tftp file-?BEWGlzkAHdZHX1JMN_BC@TDfwQiFzrb4ZrS4lzZvXL+CK9UxeT9p3 modified;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/15/2016 9:20680101004DHCP RENEW sent - No response for IPv4;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/15/2016 9:20680103004DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/15/2016 9:20680106006DHCP Renew - lease parameters tftp file-?BEWGlzkAHdZHX1JMN_BC@TDfwQsmfu2O73AqFUjfIpG_Ib5ZLuPek modified;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/18/2016 5:35680103004DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/18/2016 5:35680106006DHCP Renew - lease parameters tftp file-?BEWGlzkAHdZHX1JMN_BC@TDfwQk6up+u6vr8GBBIkUYSryiAVtO9v modified;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
1/1/1970 0:00820002003No Ranging Response received - T3 time-out;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/18/2016 9:31900000004MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;
9/18/2016 9:31820002003No Ranging Response received - T3 time-out;CM-MAC=00:1d:d6:47:5f:52;CMTS-MAC=00:01:5c:46:98:53;CM-QOS=1.1;CM-VER=3.0;

 

 

 

 

Expert

Re: Ping issue since April 22 2016

need the upstream levels as well

 

Observer

Re: Ping issue since April 22 2016

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 1437.00 MHz49.25 dBmVDOCSIS2.0 (ATDMA)2560 kSym/s16QAM
Upstream 2119.40 MHz48.25 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM
Upstream 3224.20 MHz48.75 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s16QAM
Upstream 4330.60 MHz49.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s16QAM
Expert

Re: Ping issue since April 22 2016

The T 3's on the 18th are about it for errors for the past month.

post a tracert to google.com

 

 

Observer

Re: Ping issue since April 22 2016

I  know exactly what this guy is referring to. I live in Enterprise which is not far from Dothan and we are getting the same thing as well as other TWC users here since that time that he posted. I have incoming proof as well.

Observer

Re: Ping issue since April 22 2016

The speeds are there but the ping is BAAAD.

TWC business class ping.

On a business class connection... That ping...

 

Residential ping.

Residential ping...

 

Tracing route to google.com [216.58.192.142]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms INTERNAL HOST [INTERNAL IP]
2 1 ms <1 ms <1 ms rrcs-74-87-146-33.west.biz.rr.com [74.87.146.33]
3 <1 ms <1 ms <1 ms 65.28.220.226
4 1 ms 1 ms 1 ms 65.28.220.25
5 21 ms 20 ms 20 ms xe-0-0-0.dthnal1401h.midwest.rr.com [65.29.27.142]
6 42 ms 38 ms 38 ms be29.clevohek01r.midwest.rr.com [65.29.27.132]
7 47 ms 46 ms 46 ms 0.ae3.pr1.lax00.tbone.rr.com [107.14.17.254]
8 46 ms 46 ms 46 ms 0.ae3.pr0.dca20.tbone.rr.com [107.14.19.160]
9 47 ms 47 ms 47 ms 216.50.76.41
10 55 ms 58 ms 49 ms 207.88.14.190.ptr.us.xo.net [207.88.14.190]
11 47 ms 48 ms 47 ms 207.88.14.165.ptr.us.xo.net [207.88.14.165]
12 65 ms 65 ms 63 ms 216.50.79.62
13 85 ms 82 ms 88 ms 216.239.62.143
14 47 ms 47 ms 47 ms 72.14.236.98
15 48 ms 48 ms 48 ms 72.14.232.73
16 47 ms 49 ms 48 ms 209.85.243.162
17 47 ms 47 ms 47 ms 108.170.244.1
18 48 ms 48 ms 48 ms 216.239.42.149
19 48 ms 47 ms 47 ms ord36s01-in-f142.1e100.net [216.58.192.142]

Trace complete.

 

What's the deal?

 

It's not us by the way. NOTHING is wrong with the modems. In fact the business connection is fiber right to work here.

Proven Sharer

Re: Ping issue since April 22 2016

Ping times to servers near Chicago are lower because that's where TWC connects with their contracted internet service provider. As you already knew, TWC has made some routing changes between their regional network centers which will change ping times for traffic flowing within the TWC network.

This forum is peer-to-peer support, staffed mostly by experienced customer volunteers, also some TWC volunteers and employees who identify themselves as such. We help YOU troubleshoot problems at your end, while TWC runs the network business and cable plant.
Proven Sharer

Re: Ping issue since April 22 2016

I guess I don't understand your complaint - ping times to Montgomery AL shown in the Speedtest runs are lower for residential users than for business class. Line 10 is where you exit TWC's network and jump onto the internet. Please run a tracert to the same destination GOOGLE.COM on both lines and post the results.