Skip to main content

    Support

    Offers

Vault-Tec's profile
Vault-Tec
Conversation Starter
1st Reply
1st Topic

Contributor

 • 

23 Messages

Monday, October 12th, 2020 9:00 PM

Closed

Worsening Internet Issues

Hi, the issues I'm having seem to be multiplying... it started with latency spikes which could be attributed to all sorts of stuff. It's moved on to momentary disconnects, prolonged latency issues, unstable power levels, massive amounts of "uncorrectables" and partial service notes in my event logs... on top of a Comcast phone tech canceling my last appointment that I set up because the issue was supposedly found and fixed! Just a heads up though, it wasn't and has worsened. I'm a bit irritated about that as I was told it was being canceled and had no other option. How's that for customer service, eh?

Question

 • 

Updated 

5 years ago

1.2K

9

0

0

This conversation is no longer open for comments or replies and is no longer visible to community members.

Vault-Tec

Contributor

 • 

23 Messages

5 years ago

Downstream
DCID Freq Power SNR Modulation Octets Correcteds Uncorrectables
Downstream 1 9 531.00 MHz -3.80 dBmV 38.98 dB 256QAM 19399194 42105 118642
Downstream 2 42 393.00 MHz -3.60 dBmV 38.61 dB 256QAM 18239931 27783 88934
Downstream 3 43 399.00 MHz -3.60 dBmV 38.61 dB 256QAM 21438816 29966 93444
Downstream 4 44 405.00 MHz -3.40 dBmV 38.61 dB 256QAM 18100512 31219 100108
Downstream 5 45 411.00 MHz -3.40 dBmV 38.61 dB 256QAM 19427519 31240 97710
Downstream 6 34 417.00 MHz -3.50 dBmV 37.64 dB 256QAM 19632463 32476 100430
Downstream 7 35 423.00 MHz -3.40 dBmV 37.64 dB 256QAM 15917991 34996 114428
Downstream 8 36 435.00 MHz -3.90 dBmV 37.64 dB 256QAM 15283692 33673 116640
Downstream 9 37 453.00 MHz -4.20 dBmV 37.64 dB 256QAM 13862024 35100 109865
Downstream 10 38 459.00 MHz -4.10 dBmV 37.36 dB 256QAM 14656407 33679 100205
Downstream 11 39 465.00 MHz -4.50 dBmV 38.98 dB 256QAM 16229059 35363 88010
Downstream 12 40 471.00 MHz -4.70 dBmV 37.36 dB 256QAM 16110714 35986 92687
Downstream 13 41 477.00 MHz -4.40 dBmV 38.61 dB 256QAM 17286983 33046 90522
Downstream 14 1 483.00 MHz -4.60 dBmV 37.64 dB 256QAM 14486696 34687 98779
Downstream 15 2 489.00 MHz -4.60 dBmV 37.64 dB 256QAM 12404242 36379 101414
Downstream 16 3 495.00 MHz -4.50 dBmV 38.61 dB 256QAM 17527548 36375 94835
Downstream 17 4 501.00 MHz -4.60 dBmV 38.61 dB 256QAM 19624313 36731 96057
Downstream 18 5 507.00 MHz -4.30 dBmV 37.36 dB 256QAM 18651251 37295 100078
Downstream 19 6 513.00 MHz -4.20 dBmV 38.61 dB 256QAM 21128913 39599 104456
Downstream 20 7 519.00 MHz -4.30 dBmV 38.61 dB 256QAM 21367157 38801 108462
Downstream 21 8 525.00 MHz -3.70 dBmV 37.64 dB 256QAM 21891178 41253 108389
Downstream 22 10 537.00 MHz -3.50 dBmV 37.64 dB 256QAM 16620487 44255 122237
Downstream 23 11 543.00 MHz -2.90 dBmV 38.61 dB 256QAM 16999563 44337 124223
Downstream 24 12 549.00 MHz -3.10 dBmV 38.61 dB 256QAM 14503400 45249 129286
Reset FEC Counters
Upstream
UCID Freq Power Channel Type Symbol Rate Modulation
Upstream 1 2 29.20 MHz 50.50 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Upstream 2 4 16.40 MHz 51.00 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Upstream 3 3 22.80 MHz 50.75 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Upstream 4 1 35.60 MHz 50.75 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Status
System Uptime: 0 d: 0 h: 40 m
Computers Detected: staticCPE(1), dynamicCPE(1)
CM Status: Telephony-DHCP
Time and Date: Mon 2020-10-12 23:05:49


Date Time Event ID Event Level Description
10/12/2020 20:48 84020200 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 20:52 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 20:54 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 20:55 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:06 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:07 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:08 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:08 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:08 84020200 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:08 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:09 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:11 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:11 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:11 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:34 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:34 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:56 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 21:56 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 22:19 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 22:19 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
PacketCable(MTA) Events

Date Time Event ID Description
12/31/2019 12:24 25 MTA PROV: Failed
1/6/2020 1:51 25 MTA PROV: Failed
1/8/2020 9:57 25 MTA PROV: Failed
1/8/2020 12:15 25 MTA PROV: Failed
1/8/2020 13:52 25 MTA PROV: Failed
1/27/2020 11:37 25 MTA PROV: Failed
2/12/2020 18:11 25 MTA PROV: Failed
2/12/2020 18:29 25 MTA PROV: Failed
2/24/2020 10:14 25 MTA PROV: Failed
3/3/2020 18:53 25 MTA PROV: Failed
3/4/2020 5:38 25 MTA PROV: Failed
3/7/2020 9:53 25 MTA PROV: Failed
3/10/2020 11:30 25 MTA PROV: Failed
3/27/2020 9:03 25 MTA PROV: Failed
4/16/2020 9:53 25 MTA PROV: Failed
6/11/2020 16:35 25 MTA PROV: Failed
6/11/2020 16:41 25 MTA PROV: Failed
6/14/2020 17:13 25 MTA PROV: Failed
8/2/2020 11:28 25 MTA PROV: Failed
8/6/2020 1:42 25 MTA PROV: Failed
8/12/2020 19:17 25 MTA PROV: Failed
9/16/2020 23:59 25 MTA PROV: Failed
9/18/2020 10:18 25 MTA PROV: Failed
9/19/2020 13:04 25 MTA PROV: Failed
9/20/2020 18:58 25 MTA PROV: Failed
9/21/2020 16:02 25 MTA PROV: Failed
9/25/2020 15:49 25 MTA PROV: Failed
9/27/2020 16:32 25 MTA PROV: Failed
10/8/2020 0:01 25 MTA PROV: Failed
10/8/2020 2:08 25 MTA PROV: Failed
10/8/2020 10:03 25 MTA PROV: Failed
10/12/2020 22:26 25 MTA PROV: Failed

0

0

EG

Expert

 • 

111.4K Messages

5 years ago

The upstream power is too high and it may be intermittently fluctuating even higher to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.

0

0

Vault-Tec

Contributor

 • 

23 Messages

5 years ago

I already booked a tech to come out and visit! A woman with a super heavy accent canceled my appointment and told me it was fixed!

My latency is up 35-40ms from the average now.

Downstream
DCID Freq Power SNR Modulation Octets Correcteds Uncorrectables
Downstream 1 9 531.00 MHz -9.10 dBmV 36.39 dB 256QAM 323156680 528374 1642344
Downstream 2 10 537.00 MHz -9.10 dBmV 36.39 dB 256QAM 329573194 542614 1743708
Downstream 3 11 543.00 MHz -8.80 dBmV 36.39 dB 256QAM 348625657 552357 1772789
Downstream 4 12 549.00 MHz -9.30 dBmV 36.61 dB 256QAM 358008695 567194 1846859
Downstream 5 13 555.00 MHz -9.60 dBmV 35.78 dB 256QAM 354405826 586358 1947865
Downstream 6 14 561.00 MHz -9.90 dBmV 35.78 dB 256QAM 422305842 594153 1994841
Downstream 7 15 567.00 MHz -11.10 dBmV 35.08 dB 256QAM 422505138 604531 2038753
Downstream 8 16 573.00 MHz -12.00 dBmV 34.93 dB 256QAM 425023887 616269 2092083
Downstream 9 17 579.00 MHz -12.80 dBmV 34.48 dB 256QAM 316255079 629628 2165944
Downstream 10 18 585.00 MHz -14.10 dBmV 33.83 dB 256QAM 394895202 594619 2057579
Downstream 11 19 591.00 MHz -14.20 dBmV 33.96 dB 256QAM 394949755 599035 2153685
Downstream 12 20 597.00 MHz -14.80 dBmV 33.38 dB 256QAM 485258742 621048 2197670
Downstream 13 21 603.00 MHz -15.50 dBmV 32.68 dB 256QAM 415161232 650768 2293442
Downstream 14 22 609.00 MHz -15.30 dBmV 32.68 dB 256QAM 495662728 613165 2170316
Downstream 15 23 615.00 MHz -15.20 dBmV 32.58 dB 256QAM 498692486 658620 2328075
Downstream 16 24 621.00 MHz -15.70 dBmV 32.24 dB 256QAM 496490666 820340 2416581
Downstream 17 25 627.00 MHz -15.70 dBmV 31.69 dB 256QAM 375679110 1043985 2632212
Downstream 18 26 633.00 MHz -16.50 dBmV 31.14 dB 256QAM 460139446 644100 2100855
Downstream 19 27 639.00 MHz -17.40 dBmV 30.37 dB 256QAM 458829626 819141 1725281
Downstream 20 28 645.00 MHz -17.80 dBmV 30.00 dB 256QAM 461539946 840533 1811704
Downstream 21 29 651.00 MHz -19.00 dBmV 29.27 dB 256QAM 386546750 1204823 1425169
Downstream 22 30 657.00 MHz -20.10 dBmV 28.61 dB 256QAM 481326309 2862866 1907496
Downstream 23 31 663.00 MHz -20.80 dBmV 27.81 dB 256QAM 483990090 4367522 2523966
Downstream 24 32 669.00 MHz -22.20 dBmV 26.75 dB 256QAM 457329369 12949350 5340212
Reset FEC Counters
Upstream
UCID Freq Power Channel Type Symbol Rate Modulation
Upstream 1 2 29.20 MHz 51.00 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Upstream 2 4 16.40 MHz 51.25 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Upstream 3 3 22.80 MHz 51.00 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Upstream 4 1 35.60 MHz 51.50 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Status
System Uptime: 0 d: 6 h: 22 m
Computers Detected: staticCPE(1), dynamicCPE(1)
CM Status: Telephony-DHCP
Time and Date: Tue 2020-10-13 15:06:55

Date Time Event ID Event Level Description
10/13/2020 14:48 84020200 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:48 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:48 84020200 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:48 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:48 84020200 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:48 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:48 84020200 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:48 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:48 84020200 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:48 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:48 84020200 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:48 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:49 84020200 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:49 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:50 84020200 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:50 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:51 84020200 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:51 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 14:53 84020200 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/13/2020 15:08 84000700 5 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
PacketCable(MTA) Events

Date Time Event ID Description
1/8/2020 12:15 25 MTA PROV: Failed
1/8/2020 13:52 25 MTA PROV: Failed
1/27/2020 11:37 25 MTA PROV: Failed
2/12/2020 18:11 25 MTA PROV: Failed
2/12/2020 18:29 25 MTA PROV: Failed
2/24/2020 10:14 25 MTA PROV: Failed
3/3/2020 18:53 25 MTA PROV: Failed
3/4/2020 5:38 25 MTA PROV: Failed
3/7/2020 9:53 25 MTA PROV: Failed
3/10/2020 11:30 25 MTA PROV: Failed
3/27/2020 9:03 25 MTA PROV: Failed
4/16/2020 9:53 25 MTA PROV: Failed
6/11/2020 16:35 25 MTA PROV: Failed
6/11/2020 16:41 25 MTA PROV: Failed
6/14/2020 17:13 25 MTA PROV: Failed
8/2/2020 11:28 25 MTA PROV: Failed
8/6/2020 1:42 25 MTA PROV: Failed
8/12/2020 19:17 25 MTA PROV: Failed
9/16/2020 23:59 25 MTA PROV: Failed
9/18/2020 10:18 25 MTA PROV: Failed
9/19/2020 13:04 25 MTA PROV: Failed
9/20/2020 18:58 25 MTA PROV: Failed
9/21/2020 16:02 25 MTA PROV: Failed
9/25/2020 15:49 25 MTA PROV: Failed
9/27/2020 16:32 25 MTA PROV: Failed
10/8/2020 0:01 25 MTA PROV: Failed
10/8/2020 2:08 25 MTA PROV: Failed
10/8/2020 10:03 25 MTA PROV: Failed
10/12/2020 22:26 25 MTA PROV: Failed
10/13/2020 1:35 25 MTA PROV: Failed
10/13/2020 8:18 25 MTA PROV: Failed
10/13/2020 8:49 25 MTA PROV: Failed

0

0

Vault-Tec

Contributor

 • 

23 Messages

5 years ago

What's even better is that my internet is off and on right now at this moment. It keeps disconnecting or is giving me garbage signal and power levels I can't use.

So, I check the outage map and it says everything is fine! THERE'S LITERALLY AN OUTAGE NOTIFICATION WITH THE ( ! ) IN MY AREA. Comcast tools are a joke... please fix your stuff or I'll be forced to go to Centurylink!

The outage seems to have cleared, but I am still concerned about the power levels I'm receiving.
Downstream
DCID Freq Power SNR Modulation Octets Correcteds Uncorrectables
Downstream 1 9 531.00 MHz -8.50 dBmV 37.36 dB 256QAM 39258489 0 0
Downstream 2 10 537.00 MHz -8.40 dBmV 36.39 dB 256QAM 40757642 5 0
Downstream 3 11 543.00 MHz -8.10 dBmV 36.39 dB 256QAM 43354331 0 0
Downstream 4 12 549.00 MHz -8.50 dBmV 36.61 dB 256QAM 42562225 7 0
Downstream 5 13 555.00 MHz -8.70 dBmV 36.39 dB 256QAM 39075987 7 0
Downstream 6 14 561.00 MHz -9.00 dBmV 35.78 dB 256QAM 47903043 0 0
Downstream 7 15 567.00 MHz -10.00 dBmV 35.60 dB 256QAM 49973178 0 0
Downstream 8 16 573.00 MHz -10.80 dBmV 35.78 dB 256QAM 51057015 0 0
Downstream 9 17 579.00 MHz -11.50 dBmV 35.08 dB 256QAM 40592415 0 0
Downstream 10 18 585.00 MHz -12.70 dBmV 34.48 dB 256QAM 41627359 0 0
Downstream 11 19 591.00 MHz -12.90 dBmV 34.48 dB 256QAM 47777004 0 0
Downstream 12 20 597.00 MHz -13.60 dBmV 33.96 dB 256QAM 41397807 0 0
Downstream 13 21 603.00 MHz -14.40 dBmV 33.49 dB 256QAM 42945801 0 0
Downstream 14 22 609.00 MHz -14.30 dBmV 33.38 dB 256QAM 46573119 0 0
Downstream 15 23 615.00 MHz -14.30 dBmV 33.38 dB 256QAM 43737031 1 0
Downstream 16 24 621.00 MHz -14.60 dBmV 32.96 dB 256QAM 39924084 0 0
Downstream 17 25 627.00 MHz -14.60 dBmV 32.68 dB 256QAM 23698909 0 0
Downstream 18 26 633.00 MHz -15.30 dBmV 32.24 dB 256QAM 35540393 0 0
Downstream 19 27 639.00 MHz -16.10 dBmV 31.34 dB 256QAM 29696452 1 0
Downstream 20 28 645.00 MHz -16.40 dBmV 31.14 dB 256QAM 24771411 6 0
Downstream 21 29 651.00 MHz -17.60 dBmV 30.42 dB 256QAM 16549658 2 0
Downstream 22 30 657.00 MHz -18.50 dBmV 29.85 dB 256QAM 25550510 135 0
Downstream 23 31 663.00 MHz -19.00 dBmV 29.19 dB 256QAM 21406014 2083 0
Downstream 24 32 669.00 MHz -20.40 dBmV 28.09 dB 256QAM 18606602 74661 0

0

0

EG

Expert

 • 

111.4K Messages

5 years ago

The downstreams are way out of spec now ! You have some wide intermittent fluctuations going on there. They should not flux more than 3-4 dB. 

 

Good luck with the tech visit ! Please post back with how things turn out.

0

0

Vault-Tec

Contributor

 • 

23 Messages

5 years ago

I've swapped modems to an older model and am still having trouble. So, that mostly rules out the modem being the culprit. This modem is also still recording T3 Timeouts, partial service, and Sync Failures... along with really high amounts of uncorrectables.

0

0

EG

Expert

 • 

111.4K Messages

5 years ago

Have you re-booked a tech visit ? This can't be fixed remotely by phone.

0

0

Vault-Tec

Contributor

 • 

23 Messages

5 years ago

There was an outage taken in the area the following day of my last reply and it helped for a little bit, then did the same thing. The day after that they took another outage and that helped for a while until now.

Now, I have 108ms ping with 375Mbps dl 0.62Mbps ul and 80% Packet Loss...

I have a super low opinion of Comcast's reliability, customer support, and products right now... to say the least.

0

0

Vault-Tec

Contributor

 • 

23 Messages

5 years ago

Update: They've declared another outage! My internet is fine now, despite the outage in my area until 4pm. Funny, when it was affecting me last night... NO OUTAGE! It's like the "outage detector" is a farce and someone just designates it manually.

How is a company this technologically inept in the current tech climate? Sheer determination and willpower?

0

0

forum icon

New to the Community?

Start Here