Cox → Re: Packetloss on Cox's network - 68.1.4.139

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?

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.

Sounds like QOS on the router is kicking in.

I am having similar problems when I route through either 68.1.4.139 or 68.1.4.133. I was supposed to have a tech come out Wednesday, but I received a call saying that the problem was fixed on Cox's end. I was still having terrible problems, on an unloaded line, last night after the fix.

I will upload pingplotter outputs when I get home tonight.

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.

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.

For reference, I found one of the server IPs from another thread. Ping Plotter (with router).

I'd like to get without the router, but SWMBO is using the tubes as well.

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

The replacement router appears to have helped with some of the intermittent loss that was being observed previously. Latency is still a little high but still much better without the router. Which tier of service do you subscribe to and do you have any other Internet applications running?

When the problem started, I upgraded to Premier in the vain hopes that it was a neighborhood bandwidth issue. I haven't stepped back down.

During these tests, the only programs I had running were Firefox (generic speed tests show 15-30Mbps download, Ventrilo, and LoL.

The vent was probably an interesting issue. my ping to tungsten.typefrag.com (located in Atlanta) was ~175 ms, to go maybe 100 miles north. My ping to the LoL servers (according to in game) was ~200-250, and they're west coast.

And again, it's time-related. I played one or two games when I got home with no problems. But once the sun goes down, my connection goes all Mr. Hyde on me.

It may be necessary for a technician to come out and so some further troubleshooting at this point.