Time Warner Cable - Legacy → [TWC] Cary,NC - Packet Loss to ae-2-0.pr0.dca10.tbone.rr.com

This morning a 2 to 3% Packet loss to ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]

--- 66.109.6.169 ping statistics ---
100 packets transmitted, 98 packets received, 2.0% packet loss
round-trip min/avg/max/stddev = 28.980/35.086/62.088/4.615 ms

--- 66.109.6.169 ping statistics ---
100 packets transmitted, 97 packets received, 3.0% packet loss
round-trip min/avg/max/stddev = 29.297/35.419/108.986/8.301 ms

Some of TWC routers are over utilized as seen below:
traceroute to ndt-03.ncren.net (128.109.178.83), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 1.310 ms 0.964 ms 1.019 ms
2 cpe-174-097-224-001.nc.res.rr.com (174.97.224.1) 372.456 ms 409.600 ms 327.657 ms
3 gig2-0-9.rlghncj-rtr4.nc.rr.com (66.26.33.141) 9.825 ms 16.753 ms 13.306 ms
4 ae19.rlghncpop-rtr1.southeast.rr.com (24.93.64.0) 12.146 ms 11.790 ms 10.522 ms
5 ae14.chrlncpop-rtr1.southeast.rr.com (24.93.64.25) 60.614 ms 18.766 ms 19.432 ms
6 ten1-3.chrlncsa-p-rtr01.southeast.rr.com (24.93.73.57) 21.903 ms 18.315 ms 19.410 ms
7 por100.twcc.rlghnc-a-c2701.nc.rr.com (24.27.255.253) 20.792 ms 19.207 ms 39.628 ms
8 rrcs-24-172-64-46.midsouth.biz.rr.com (24.172.64.46) 20.327 ms * *
9 * * *
10 * * *
11 * * *
12 * * ndt-03.ncren.net (128.109.178.83) 32.653 ms

Website Load Times Max on 3/22 up to 10 secs:
----Date---- / Min(Sec) / Max(Sec) / Avg(Sec)
2013-03-27 / 0.36 / 1.54 / 0.83
2013-03-26 / 0.35 / 2.74 / 0.95
2013-03-25 / 0.40 / 4.92 / 1.00
2013-03-24 / 0.41 / 3.94 / 0.99
2013-03-23 / 0.40 / 5.96 / 0.99
2013-03-22 / 0.41 / 10.27 / 1.03
2013-03-21 / 0.42 / 2.67 / 1.00
2013-03-20 / 0.44 / 4.25 / 1.00

Latency Max on 3/24 up to 1.1 seconds:
--Date-- /Min(ms) / Max(ms) / Avg(ms)
3/27/13 / 24.69 / 47.92 / 31
3/26/13 / 20.91 / 589.8 / 30.83
3/25/13 / 20.77 / 71.43 / 30.52
3/24/13 / 20.79 / 1181.44 / 30.92
3/23/13 / 20.88 / 403.69 / 30.61
3/22/13 / 20.78 / 550.32 / 30.51
3/21/13 / 20.78 / 89.75 / 30.77
3/20/13 / 20.76 / 72.22 / 30.41

There seems to be a TWC issue going on in this region as measured above and per others also posting on this site.

I already posted to the TWC Direct.

How long will this take for them to correct ?

Pinging routers directly is no way to troubleshoot a problem with an endpoint.

Traffic direct to the router is the least important traffic to a router. Because the router is busy processing real traffic. The only traffic meant to go direct to a router is for the people that admin the router. Packets going THROUGH the router do NOT get processed the same way as packets destined TO the router.

Also, your traceroute does not even have dca10.tbone.rr.com in the path, so I'm not sure what you're even trying to look at here.

The high ping on your second hop is related to a well-known issue with one particular CMTS vendor's hardware deployed by TWC. Let's just say that the vendor is question is further behind other vendors with regards to some aspects of their equipment.

Hop 2 is consistently bad. Why is TWC not replacing it?

traceroute to 173.194.37.32 (173.194.37.32), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 3.694 ms 0.608 ms 0.642 ms
2 cpe-174-097-224-001.nc.res.rr.com (174.97.224.1) 3114.620 ms 819.126 ms 1841.552 ms
3 66.26.44.25 (66.26.44.25) 11.692 ms 11.440 ms 10.485 ms
4 ae19.rlghncpop-rtr1.southeast.rr.com (24.93.64.0) 21.474 ms 12.705 ms 9.505 ms
5 107.14.19.44 (107.14.19.44) 31.367 ms 32.971 ms 35.131 ms
6 107.14.19.133 (107.14.19.133) 28.170 ms * 30.013 ms
7 66.109.9.66 (66.109.9.66) 81.105 ms 83.976 ms 92.029 ms
8 209.85.252.46 (209.85.252.46) 36.686 ms 31.742 ms 46.241 ms
9 72.14.236.98 (72.14.236.98) 30.962 ms 31.368 ms 61.635 ms
10 66.249.95.231 (66.249.95.231) 38.964 ms 39.088 ms 35.696 ms
11 72.14.239.66 (72.14.239.66) 26.854 ms 28.800 ms 32.830 ms
12 66.249.94.23 (66.249.94.23) 28.142 ms 28.261 ms 28.550 ms
13 64.233.175.92 (64.233.175.92) 30.765 ms 30.838 ms 28.628 ms
14 atl14s07-in-f0.1e100.net (173.194.37.32) 28.805 ms 31.150 ms 32.168 ms

Because it's not an issue. You are honestly going to have to learn how to read a traceroute to understand what you are seeing.

Those are packets destined for that particular router, they end there. They go NO FURTHER. The router/CMTS is slow to respond to those packets, and those packets ONLY.

It is not doing that to the traffic going THROUGH the router, like I tried to explain already.

If it were affecting traffic THROUGH the router, you would see the SAME latency added to each hop until the very end. Latency at the end hop is cumulative. If it takes you 3000ms to get to the second hop it would take you 3032ms to get to the last hop in your traceroute.

There is NOTHING wrong with the 2nd hop in your traceroute if the FINAL hop looks fine. And 32ms from a cable modem to what appears to be a host in Atlanta on another provider's network is not bad latency.

When a packet "expires", its TTL goes to zero" at a router, it is discarded. Always, without exception. The router may elect to generate a new packet and return it to the sender, at the whim of whoever configured the router.

The router is fine. It is doing what TWC programmed it to do.