US Cable Support > Cox HSI > [LA] Baton Rouge Packet Loss

[LA] Baton Rouge Packet Loss

You mentioned support had no issues pinging the modem and all PCs experience issues, have you tested without the router to eliminate that variable?

Yes, all of the symptoms persist when bypassing all routers and getting as close to possible to the coax entrypoint into my home (bypassing all splitters or lengths of unnecessary cable).

Another pingplotter from today:

»i.imgur.com/jEzhi.png

show the results with out the router on pinng plotter as the last screen shot is with the router and then ping to www.cox.net so as to stay with in the cox network

reply to anterograde
What part of town are you in? I'm in shenandoah and have the same if not worse. I'm dropping 8-20% depending on where I test.

Just north of you, old hammond and millerville, approx. It has been like this for some time now, like 6 weeks. Today is PARTICULARLY awful, 100% in bursts for like 5-10-15, sometimes 20 seconds.

reply to m8trix
Here is some data straight to the modem, and straight to cox.net.

»i.imgur.com/GnqN7.png

Same issues.

I think that it is hilarious that when I call cox on the telephone, they tell me there doesn't seem to be any issues with my phone or internet, and then they can't hear me on the phone for 10-15 seconds and almost hang up, because my phone doesn't work consistently, probably due to the same problem.

I've had some pretty wicked packet loss since August 27, the day before the storm. They performed some tests on my modem and detected 30% packet loss, so they're sending a tech out in a few hours.

Here's pingplotter results with my laptop connected directly to the modem, personal firewall turned off etc.

»i.imgur.com/dOocx.png

Oh yeah, I'm in 70808

Is it just me or does it seem like 68.99.123.4 has more packet loss than any other hop?

And they will never send out a tech same day for me. Last time I was in the bathroom and they left within like 20 seconds of the first knock, time after that, the technician was scheduled for TV maintenance and said he had to reschedule for an internet/phone visit.

I only have a home phone so I can never troubleshoot over the phone, since resetting the modem obviously ends our call.

Lucky for you, your problems only started as recently as the 27th, mine have been like this for over 6 weeks with no help from Cox to fix the issue, only threats of charging for tech visits and delay after delay after delay.

Latest pingplotter:

»i.imgur.com/Eqj1f.png

Absolutely loving this.

That's a definite pattern my friend. My assumption as to the cause of the packet loss was they were redirecting traffic to other data centers in anticipation of the storm. What was weird is that I had no issues Friday, August 31 so I thought everything was back to normal.

I called yesterday and the tech on the phone confirmed the traffic re-route to be true. I was really surprised when he offered me a 3-5 time slot for today. Unfortunately, I am confident that the tech won't be able to do anything to fix my problem immediately. He will simply be reporting the issue to his supervisor for escalation.

like I said, I don't think that my problem has anything to do with traffic re-routing as it began before Isaac was even a named storm, but it seems like a valid theory for your issue.

lets all hope we can start getting what we pay for soon.

My favorite line out of this whole debate with cox was when a representative told me that I didn't have a tier of internet designed for online gaming, and I told them the game I was trying to play was a game I played in the 90s on dial-up.

Some more love from Cox in this thread would be greatly appreciated, maybe with some commentary about the 68.99.123.4 node?

reply to komseh
Looking at you guy's pingplotter results, it seems the issue is local to yall as first hop(either Modem, or Router) is showing 100% packet loss as if its not responding to ping, which is odd. It also continues threw out the rest of the hops. So most the time the first hop packet loss starts occurring on, means the source of the problem is happening there. Its something imo you need to have cox out to troubleshoot locally.

It would be nice if they would become aware of a problem that I've been complaining about for WELL over a month without having a gathering of people with notarized evidence.

That being said, thanks for the insight into the pingplotter results, I wasn't really sure what to make of the 100% loss on the first hop, maybe that is a real indication of a serious local problem.

I wish I could just skip this whole process of a tech coming out by getting ahold of someone on the telephone that can actually DO something.

The 100% packet loss on the first hop simply means that device doesn't respond to ICMP echo requests. This is a common occurrence in traceroute results and does not necessarily indicate a problem with the device in question.

The tech just finished up here. We swapped modems and the issue still persisted. The tech checked all of my connectors and everything is fine. My signal levels are great.

Another tech was communicating with him during his troubleshooting process and another customer is having the exact same type of issue and he only lives a few miles away. The tech seems confident that this is a problem at the office and he is reporting both issues to the maintenance supervisor.

I'm going out of town for work and will be able to check this problem again on saturday. I will reply back here once I have new information.

Also, to explain how they test packet loss to your modem - They ping the private IP address of your modem from the office, which is a 10.x.x.x number. The test sends 50 ICMP echo requests in a few seconds. In my case the tech did 3 tests from his truck. The first result showed 2% loss, second results showed 88%, third results showed 58%.

Kind of what I figured, and I have run plenty of traceroute's with many modems, with, and without a router. Never seen modem itself not respond to ICMP requests. I understand a router has an option to not respond to ICMP requests, and some routers with dos attack protection are known to drop ICMP requests when so many are requested in a very short time.

Anyways I figured both you guy's problem are locally, meaning either it was a home side issue. Or a problem between your home, and the local CMTS. Because that's what your pingplotter results point to, with packet loss occurring right after leaving your home network.

Just got a call back from the tech - He spoke with the maintenance supervisor and apparently the issue is due to noise in the 37Mhz range on my node.

I wonder what the time frame for their adjustments will be, and I wonder if whatever they do will fix both of our problems.

reply to komseh

reply to anterograde
Well they said it definitely won't be priority due to them still having to correct outages from the hurricane.

That really seems like a cop-out answer from them, in my opinion.

I'm going to tell them it isn't a priority to pay my bill due to still having to correct outages from their service.