Frequent lagspikes/packet loss with comcast? troubleshoot help please.

Yensu

Honorable
Dec 22, 2012
36
0
10,530
We set up service with Comcast in November with no noticeable interruptions for the first month or so. But we started experience frequent lag spikes and packet loss.

I've been using VE Network Catcher Lite to track these spikes and packet loss.

At the end of the record we have an average of 5% packet loss and ~10 800+ ping spikes over a 15 minute test.
That means we're getting a lag spike every ~1.5 minutes.

Right before a huge lag spike, 95% of the time, there is a huge packet loss.

This is unacceptable for my streaming/gaming needs.

I have not yet contacted them. I want to try everything in my power to trouble shoot this before I call.

So far I have tried:
unplug 30s, replug
full reset
lan cable swap

What would you recommend I try?
 

memadmax

Distinguished
Mar 25, 2011
2,492
0
19,960
If you can get into the cable modems configuration page, look and see if it's the one having the problem. It should show something like connection speed(make sure it matches what you are paying for), connection db(lower is better I believe) dropped packets that it has seen, etc etc...

If you see errors in the modem then start tracing your cable wire up as far as you can, if in doubt replace. If that doesn't help then call up comcast.
 

Yensu

Honorable
Dec 22, 2012
36
0
10,530


Connection Speed: 1Gbps (faster than paying for, but also not receiving that rate)
I don't know where to look for connection db


-------------------------------------
Logs on the gateway after resetting it:
Sun Jan 26 03:20:36 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:35:40:cd:ff:5a;CMTS-MAC=00:01:5c:22:46:0d;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 26 02:08:40 2014 Notice (6) TLV-11 - unrecognized OID;CM-MAC=cc:35:40:cd:ff:5a;CMTS-MAC=00:01:5c:22:46:0d;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 26 02:05:00 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:35:40:cd:ff:5a;CMTS-MAC=00:01:5c:22:46:0d;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 26 01:54:50 2014 Notice (6) TLV-11 - unrecognized OID;CM-MAC=cc:35:40:cd:ff:5a;CMTS-MAC=00:01:5c:22:46:0d;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 26 01:50:16 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:35:40:cd:ff:5a;CMTS-MAC=00:01:5c:22:46:0d;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 26 01:41:57 2014 Notice (6) TLV-11 - unrecognized OID;CM-MAC=cc:35:40:cd:ff:5a;CMTS-MAC=00:01:5c:22:46:0d;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 26 01:40:40 2014 Notice (6) SW download Successful - Via Config file
Sun Jan 26 01:39:10 2014 Notice (6) SW Download INIT - Via Config file d11_v_tc8305c_speedtier_c02.cm
Sun Jan 26 01:39:02 2014 Notice (6) TLV-11 - unrecognized OID;CM-MAC=cc:35:40:cd:ff:5a;CMTS-MAC=00:01:5c:22:46:0d;CM-QOS=1.1;CM-VER=3.0;
-----------------------------
 

Yensu

Honorable
Dec 22, 2012
36
0
10,530


I think it's on their end, I've done so much troubleshooting and swapping things out. I just pray they do something about it when we call.
 

Rickbm

Prominent
May 15, 2017
2
0
510


 

Rickbm

Prominent
May 15, 2017
2
0
510
I have had both Comcast (Xfinity) and AT&T. Packet loss has been a real problem with Xfinity (for whatever the reason), and they offer a lot of suggestions (excuses) as why their customers have these issues; http://networkmanagement.xfinity.com/index.php?option=com_content&view=article&id=57 Given that Comcast or Xfinity is getting all the complaints (for years), most of their suggestions are bogus. They have a problem unique to cable or their system.

I have seen a lot of fixes from Techies, but the simple fact remains that Xfinity's system design is flawed. This problem has been going on for years, so I assume that it would cost them more to fix the problem than they are willing to spend. Please note that none of their technicians are trained in packet loss. This should tell you something. Their equipment does not test for packet loss. Need I say more?

THE FACT REMAINS THAT I HAVE NEVER HAD A PROBLEM WITH PACKET LOSS WITH AT&T DSL OR U-VERSE. They have other problems.

A while back AT&T pushed me into giving up my regular DSL for the U-Verse, the new DSL. That's when I started having disconnection problems (out of sync). I learned that you cannot be more than 3,500 feet from their box on the street. They use cable or fiber at this box and then the old copper wire phone line to your house. You also cannot walk out the door and estimate the distance to the box. My box was a block away, say, 500 feet, but by the wire connection distance, my modem was about 11,000 feet away. I have had this issue in 2 out of my last three homes. I asked for my old DSL back again, and got it and that fixed the problem. (One of the reasons they pushed U-Verse was it was less costly for them per their techs.)

I have since looked for anything on the net to see whether DSL or the newer U-Verse version of DSL could carry farther, but haven't found anything. However, looking at the AT&T website, they only offer the old DSL in "rural" situations, so that seems to answer that question. The old DSL will carry further without problems. You will not find the speed, however.

I would try U-Verse, provided you can get within 3-3,500 feet from the box. The Techs have equipment that will tell you the distance. If it is too far, cancel install and try something else. This creates another problem. Any time you move or want to build a new house, until the tech comes out on an install, with AT&T you got no clue what you got until they set of the modem and check the distance. I don't think you get charged if you cancel at that point, but I am pretty sure you don't. Verify with the tech.

I also have had OOMA all this time, and packet loss used to disconnect your phone call. I asked OOMA recently if they fixed the packet loss with Xfinity, and they said yes. I should have asked how, but maybe you can ask. OOMA is the best VOIP out there and I only pay less than $6 per month.

I have no clue how much data is used when gaming online, I would try a local wireless ISP. Many are smaller companies and will bend over backwards to help solve problems. AT&T and Xfinity don't like you when you are having problems such as these.