US Cable Support > Cox HSI > Packetloss on Cox's network - 68.1.4.139

Packetloss on Cox's network - 68.1.4.139

Hello Shadowdane,

I'm having a similar problem in Arizona with a similar server, also my fifth hop to pretty much anywhere, with the IP 68.1.1.19. Same PingPlotter results. Have you tried pinging that IP directly in the Windows cmd ? When I do this with my questionable hop, the pings look normal. However, when I try to run a trace route to anywhere with Windows or PingPlotter, I get a lot of time-outs at this address.

For me, it seems that even if my Internet speeds are perfectly fine and stable, this hop will still show 40-50 % packet loss consistently on PingPlotter. It's to the point where I was wondering if it was an issue with PingPlotter and not the server itself, but I find it fascinating that you are posting about essentially the same observation.

reply to Shadowdane
Being that there is no loss before or after that hop it's very likely that router deprioritizes ICMP packets. Basically, it only responds to a set number in a given time frame. Once that number is reached it discards the rest. Hope this helps.

reply to Shadowdane
Iceman0803's right, 68.1.4.139 can't be dropping packets if you're able to get to 70.167.150.18 and beyond without loss.

reply to Shadowdane
ok I've figured out a bit more specifically when I'm getting packetloss... it seems when ever I'm downloading or uploading over maybe ~4-6Mbps sustained throughput. I start getting packetloss, once the bandwidth usage goes back to 0 the packetloss stops.

Like tonight for example I fired up Netflix on my Xbox 360 and started streaming a HD show which is about 4-5Mbps stream. I jumped on my computer and did a pinged youtube.com for example.

This data makes a little more sense now. The trace route you posted this time indicates loss between the PC you tested from and our CMTS. Can you try without the router and see if it's possible to duplicate these results?

reply to Shadowdane
What firmware are you running on the SB6141? I had similar problems until the firmware was automatically upgraded by Cox to SB_KOMODO-1.0.6.8-SCM01-NOSH.

reply to Shadowdane

reply to CoxTech1

The loss in your case appears to be mostly random. Can you try without the router and post the results?

This second trace route without the router looks much better. 68.1.4.133 is showing ICMP deprioritization but no issues unlike the previous results you posted.

So how do I fix the deprioritization? Is that the cause of my latency/stutter?

I'm currently in game, sitting at over 200 ping. Hell, I'm an hour south of Atlanta and my ventrilo (tungsten.typefrag: in ATL) is pinging at 150+ ms.

ICMP deprioritization is nothing to worry about. It isn't going to negatively affect your connection. As mentioned earlier, all that's happening is the router only replies to a certain number of pings within a given time frame. After that it just ignores the ICMP packets (ping) and that's why you see packet loss at 68.1.4.133 in Ping Plotter. This router isn't ignoring regular packets so that's why you don't see packet loss after that hop [68.1.4.133].

Hope that makes sense. Now as far as latency/stutter that is definitely a problem.. but it's not caused by 68.1.4.133 doing ICMP deprioritization.

reply to Manse
As KennyD mentioned ICMP deprioritization is a non-issue and won't cause any problems with your connection. Comparing your pingplotter results with and without the router leads me to believe the router may be a contributing factor with regards to the issues you're experiencing.

I'll snag a new router tomorrow, but I still had the same issue in game.

Perhaps it's on LoL's end, but noone I play with has the same problem

updates with new router tomorrow.

Your other ping plotters also looked better without the router so I would try this test again without it to compare the results.