Community Forum

Upstream/Downstream numbers off, lag in online gaming...

Xfinity Forum Archive
About the archive project

Xfinity Forum Archive...

This is an archived section of the community.

Content in this area has been identified as outdated or irrelevant.

This change was done in an effort to make the forum easier to use and to keep only the most helpful and recent content active.

Post your questions in the Xfinity Community

Contributor

Upstream/Downstream numbers off, lag in online gaming...

Hello!

 

I have not had any connection issues, meaning that I am always connected and never have any kind of issues with web browising, streaming video, using wi-fi devices, etc. About a month or so ago I got an email from Comcast saying a wiring issue was detected and to contact them to have someone come out. Since I was having no issues I waited, but I was getting calls as well about it, and finally scheduled an appointment for this coming Thursday. Leakage issue they maybe said?

 

So anyways I started to notice some lagging in my Xbox online gaming, both on wi-fi and ethernet. And not in all games. Ran speed tests and as we all know they can be all over the place but they were generally close to what my speed should be, close to or over 200 mbps.I have powercycled, connected direct to modem, made sure my router firmware is up to date, etc. Here are my numbers, hoping to get some input from the group so I have some more knowledge for my upcoming tech visit. 

 

Modem Netgear CM 600

Router Netgear Nighthawk R7000 (AC1900)

 

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 615000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv6 only
 
<tabindex=-1>Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 17 615000000 Hz -1.4 dBmV 39.3 dB 0 0
2 Locked QAM256 1 513000000 Hz 0.6 dBmV 40.0 dB 1 0
3 Locked QAM256 2 519000000 Hz 0.2 dBmV 39.9 dB 0 0
4 Locked QAM256 3 525000000 Hz 0.2 dBmV 39.8 dB 0 0
5 Locked QAM256 4 531000000 Hz -0.2 dBmV 39.8 dB 0 0
6 Locked QAM256 5 537000000 Hz -1.0 dBmV 39.6 dB 0 0
7 Locked QAM256 6 543000000 Hz -1.7 dBmV 39.4 dB 0 0
8 Locked QAM256 7 549000000 Hz -2.3 dBmV 39.2 dB 0 0
9 Locked QAM256 8 561000000 Hz -2.5 dBmV 39.0 dB 0 0
10 Locked QAM256 9 567000000 Hz -2.0 dBmV 39.3 dB 2 0
11 Locked QAM256 10 573000000 Hz -2.3 dBmV 39.2 dB 1 0
12 Locked QAM256 11 579000000 Hz -2.4 dBmV 39.1 dB 1 0
13 Locked QAM256 12 585000000 Hz -2.3 dBmV 39.1 dB 2 0
14 Locked QAM256 13 591000000 Hz -2.3 dBmV 39.1 dB 0 0
15 Locked QAM256 15 603000000 Hz -1.9 dBmV 39.2 dB 0 0
16 Locked QAM256 16 609000000 Hz -1.7 dBmV 39.2 dB 1 0
17 Locked QAM256 18 621000000 Hz -1.2 dBmV 39.9 dB 0 0
18 Locked QAM256 19 627000000 Hz -1.5 dBmV 39.5 dB 0 0
19 Locked QAM256 20 633000000 Hz -2.3 dBmV 39.0 dB 0 0
20 Locked QAM256 21 639000000 Hz -2.4 dBmV 39.0 dB 0 0
21 Locked QAM256 22 645000000 Hz -2.1 dBmV 39.4 dB 0 0
22 Locked QAM256 23 651000000 Hz -1.7 dBmV 39.4 dB 0 0
23 Locked QAM256 25 663000000 Hz -0.9 dBmV 39.5 dB 0 0
24 Locked QAM256 28 681000000 Hz -1.5 dBmV 39.1 dB 0 0
 
<tabindex=-1>Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 93 5120 Ksym/sec 36500000 Hz 51.8 dBmV
2 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
3 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz

0.0 dBmV

 

Time Priority Description
2018-03-25, 19:32:26 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:32:22 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:32:22 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:32:22 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:32:20 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:32:20 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:32:20 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:59 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:59 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:59 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:58 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:58 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:58 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:37 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:37 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:37 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:36 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:36 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:36 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:15 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:15 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:15 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:13 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:13 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:31:13 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:53 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:53 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:53 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:51 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:51 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:30 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:30 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:30 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:29 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:29 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:29 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:08 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:08 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
2018-03-25, 19:30:08 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=2c:30:33:86:e5:e0;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.0;
Official Employee

Re: Upstream/Downstream numbers off, lag in online gaming...

What your numbers don’t tell, is that when you’re flagged for leakage, a filter (called a high pass) goes on your line( it’s on yours), to keep whatever is happening in your house from back feeding out into the plant. The filter limits upstream channels, hopefully you didn’t ignore it too long.

FYI your dvr is further out of spec than your modem is

I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Contributor

Re: Upstream/Downstream numbers off, lag in online gaming...

Not sure I understand Andrew....

 

Will the tech investigate this leakage issue? And what exactly is leakage?

 

DVR out of spec?

 

Thanks!

Official Employee

Re: Upstream/Downstream numbers off, lag in online gaming...


@Sinnin wrote:

Not sure I understand Andrew....

 

Will the tech investigate this leakage issue? And what exactly is leakage?

 

DVR out of spec?

 

Thanks!


Yes, that's the whole point of the tech coming out is to fix the leakage or ingress. It can be something as simple as loose cable, bad connectors, bad splitter, or bad cable. Your dvr has a range just like your modem does for operating properly. As you posted above, your modem's upstream is barely in that range, your dvr is way past that range. It may be all related to the leakage issue.


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Contributor

Re: Upstream/Downstream numbers off, lag in online gaming...

Thanks Andrew I appreciate the info. Hopefiully after Thursday things will be back to normal.

 

Thanks again

Expert

Re: Upstream/Downstream numbers off, lag in online gaming...

The upstrean power is too high. That is likely to be why the modem is not bonding any upstream channels. There is probably some kind of an upstream channel / return path impairment problem someehere.


I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!