Newcomer

Re: latency and thoughput issues

Sorry but i would have to disagree with lose connection or corroded connection

1. all new wiring and connectors

2. new line from house to tap orange rg6

3. all connection are torqued

4. Modem rebooted because they replaced 3 sections underground cable down the block on my side of the road.

5. Primary channel   correctables  are  from when they splice in new lines yesterday.

6. Guess its my problem Trace Route are way out there in ms..

and T4s and T3s  / MDD /TOD / Timing Synchronization failure.

7. Guess its my problem TV pixelate, your right because for a year now these are issues I have to deal with day after day .

8. Thoughput issues / ultization Issues

So thank you for the suggestion of corroded or loose connection and need to be more then tad more then finger tight.

I am in N.C. local network is 24.25.5.60

Newcomer

Re: latency and thoughput issues

So Please enlighten me of these because there are no loose connection.

 

Performing traceroute to (24.25.5.60) from (71.77.140.xxx), 30 hops max, 1000 byte packets

01   71.77.128.1        10 ms  60 ms  10 ms
02   24.88.225.126      220 ms  40 ms  30 ms
03   24.25.39.14        10 ms  20 ms  30 ms
04   24.93.64.190       20 ms  30 ms  20 ms
05   24.93.64.119       20 ms  20 ms  24.93.64.90        10 ms
06   24.25.5.60         10 ms  24.93.64.119       20 ms  24.25.5.60         20 ms
Traceroute complete.

Performing traceroute to (24.25.5.60) from (71.77.140.xxx), 30 hops max, 1000 byte packets

01   71.77.128.1        40 ms  10 ms  <1 ms
02   24.88.225.126      50 ms  20 ms  30 ms
03   24.25.39.14        20 ms  20 ms  20 ms
04   24.93.64.190       20 ms  20 ms  20 ms
05   24.93.64.119       20 ms  10 ms  24.93.64.103       20 ms
06   24.25.5.60         150 ms  10 ms  10 ms
Traceroute complete.

Performing traceroute to (24.25.5.60) from (71.77.140.xxx), 30 hops max, 1000 byte packets

01   71.77.128.1        20 ms  10 ms  10 ms
02   24.88.225.126      240 ms  40 ms  20 ms
03   24.25.39.14        30 ms  10 ms  20 ms
04   24.93.64.190       20 ms  20 ms  20 ms
05   24.93.64.117       20 ms  20 ms  24.93.64.90        10 ms
06   24.25.5.60         30 ms  10 ms  24.93.64.117       20 ms
Traceroute complete.

Expert

Re: latency and thoughput issues

What's your zip code

???

This is ingress, is probably affecting everyone on the node.

If they are replacing lengths of underground cable, they darn well know somethings wrong.

Call them back out if it persists. This may be other customer drops as well.

 

Newcomer

Re: latency and thoughput issues

Zip 28358

   After a year to the date under cable gets replaced .

Even with new cables installed and connected

Trace route still same

Take a look :

Performing traceroute to (24.25.5.60) from (71.77.140.134), 30 hops max, 1000 byte packets

01   71.77.128.1        20 ms  10 ms  10 ms
02   24.88.225.126      210 ms  30 ms  40 ms

03   24.25.39.14        10 ms  20 ms  20 ms
04   24.93.64.190       20 ms  20 ms  20 ms
05   24.93.64.103       20 ms  20 ms  24.93.64.117       10 ms

06   24.25.5.60         10 ms  10 ms  20 ms
Traceroute complete.

Performing traceroute to (24.25.5.60) from (71.77.140.134), 30 hops max, 1000 byte packets

01   71.77.128.1        10 ms  10 ms  10 ms
02   24.88.225.126      30 ms  40 ms  20 ms

03   24.25.39.14        10 ms  20 ms  20 ms
04   24.93.64.190       20 ms  20 ms  30 ms
05   24.93.64.103       20 ms  24.93.64.90        20 ms  20 ms
06   24.25.5.60         110 ms  10 ms  24.93.64.117       20 ms
Traceroute complete.

Performing traceroute to (24.25.5.60) from (71.77.140.134), 30 hops max, 1000 byte packets

01   71.77.128.1        10 ms  10 ms  10 ms
02   24.88.225.126      160 ms  30 ms  40 ms

03   24.25.39.14        10 ms  30 ms  10 ms
04   24.93.64.190       30 ms  20 ms  20 ms
05   24.93.64.117       10 ms  20 ms  20 ms
06   24.25.5.60         20 ms  10 ms  20 ms


Performing traceroute to (24.25.5.60) from (71.77.140.134), 30 hops max, 1000 byte packets

01   71.77.128.1        10 ms  10 ms  10 ms
02   24.88.225.126      30 ms  20 ms  40 ms
03   24.25.39.14        20 ms  10 ms  10 ms
04   24.93.64.190       20 ms  20 ms  20 ms
05   24.93.64.117       20 ms  30 ms  24.93.64.103       20 ms
06   24.25.5.60         390 ms  20 ms  24.93.64.117       20 ms

Traceroute complete.

Performing traceroute to (24.25.5.60) from (71.77.140.134), 30 hops max, 1000 byte packets

01   71.77.128.1        10 ms  10 ms  20 ms
02   24.88.225.126      40 ms  80 ms  30 ms
03   24.25.39.14        20 ms  10 ms  10 ms
04   24.93.64.190       10 ms  30 ms  20 ms
05   24.93.64.90        20 ms  24.93.64.103       10 ms  20 ms
06   24.25.5.60         10 ms  10 ms  110 ms
Traceroute complete.

 

This effects everyone  not just my node goes all the way back to hub.

24.25.5.60 is the local network.

Days turn into weeks

Weeks turn into months

Months turn into year of dealing with these issues.

Besides they want to get paid.... every month.....

Its ok for casual e mail checker.

I pay to watch the little buffer wheel spin.

Nights and weekends.

Same old song and dance from spectrum 

 

Expert

Re: latency and thoughput issues

You need them back out,  it might be CH 36 trashing 597 mHz in zip code 28358...

WFPX-DT (Digital)

Channel: 36 (62.1)
Network: ION
Maximum ERP: 1000.000 kW
Coordinates: 34.884886 -79.074477

 

If you reset the modem, you might be able to get a different home (first) channel.

 

Newcomer

Re: latency and thoughput issues

Modem resets it self on regular basis , the other day  all the 6000000mHz channels  had large amount of uncorrectables and correctables , Threw that question out to the area supervisor,

Never received a response on that. So the issue is larger then just 597 mHz trashing in this area.

This mostly likely the whole area is effected due to outdated or lack of equipment within the local network.

Node capacity approached 90% due to TDMA transmit simply being unavailable 

So it bigger then just 597 trashing .

But they want to increase your bill for services they can not provide.

I know here it has nothing to do with inside wiring , its all within the network

 

This right here is just like : Systematically And Knowingly Failed To Deliver The Reliable And Fast Internet Access It Promised To Subscribers ,slower than promised; WiFi speeds were even slower, with some subscribers getting speeds that were more than 80 percent slower than what they had paid for. Spectrum-TWC continues to underserve their subscribers by failing to make the capital investments necessary to live up to their promised speeds. These investments would include substantially upgrading Spectrum-TWC’s network capability . Spectrum-TWC knew that bottlenecks in its network would result in many subscribers routinely experiencing the very hallmarks of a poor Internet connection—slowdowns, lag time, buffering and interruptions.

 

Newcomer

Re: latency and thoughput issues

I would like to say I am not a troll bad mouthing spectrum , I have a year worth of event logs

  because the matter at hand just kept get worse and worse.  Uploading issues, Downstream issues , Modem also going down. High uncorrectables and correctables. WiFi issues  you name it.  Signal issues/ out of spec . Upstream channel dropping 1 or 2 at a time.

TV pixelation, system outages I can go on and on.

I simply asking for some resolution in this matter and some one up the chain of command within Spectrum to look into this matter.

Because after a whole year of this and it not getting fixed.

Thank you Ms Raye  for your input.

 

 

Newcomer

Re: latency and thoughput issues

Question :

     Ms Raye  have you been able to check on my local network ?

Will this forum run on deaf ears or will be brought to the attention of Spectrum to come up with a solution and address issues ?

If runs on deaf ears here could provide me with the right person to contact because dealing locally  is not working.

As I stated is been over a year of issues after issue.

 

 

Expert

Re: latency and thoughput issues

It looks like issues at the cable head end or the node you're on, this looks unusually bad:

You can try a reverse tracert thru speedguide as well. But it's claiming 17ms when i checked it.. Thru the TWC/RR network this looks pretty ugly:

13    68 ms 68 ms 67 ms be1.fyvlnchj01r.southeast.rr.com [24.93.64.189]

14    130 ms 130 ms 415 ms cpe-024-025-039-013.ec.res.rr.com [24.25.39.13]

15     74 ms 73 ms 73 ms cpe-71-77-128-1.nc.res.rr.com [71.77.128.1]

Trace complete.

If your node has a lot of ingress and many customers are affected, it will overload the nodes server especially if those result in more uncorrectables than correctables

 

Newcomer

Re: latency and thoughput issues

Though I would add more meaningful data

 

2018-2-11, 20:17:21Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-11, 20:17:24Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-11, 20:18:15Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-11, 20:18:34Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:25:14Warning (5)B-INIT-RNG Failure - Retries exceeded;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:25:15Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:29:32Warning (5)B-INIT-RNG Failure - Retries exceeded;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:29:33Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:35:32Warning (5)B-INIT-RNG Failure - Retries exceeded;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:35:33Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:41:12Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2018-2-11, 20:41:33Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-11, 20:41:33Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-11, 20:41:37Critical (3)REG RSP not received;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-11, 20:41:49Error (4)T6 Timeout and retries exceeded;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-11, 20:41:51Notice (6)Received REG-RSP while in REG-HOLD1 state;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:41:57Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:47:43Warning (5)B-INIT-RNG Failure - Retries exceeded;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:47:44Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:52:48Warning (5)B-INIT-RNG Failure - Retries exceeded;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:52:49Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-2-11, 20:52:53Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2018-2-11, 20:53:06Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-11, 20:53:06Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;