Random ping spikes

Thanks EG! Could you please share a few links to known good splitters and coax cable for high speed connection?

The downstream power is on the low / weak side and it may be intermittently fluctuating even lower to out of spec levels. And some of the SNR's are too low. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, and latency problems.

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.

Here are some quality brand splitters that Comcast actually uses in different market areas;

Antronix CMC2002H 2-Way Splitter: http://www.amazon.com/Antronix-CMC2002H-2-Way-Splitter/dp/B001E4OH1E

Regal 2 WAY 1 GHZ Splitter: http://www.amazon.com/DIG702867-Regal-WAY-GHZ-SPLITTER/dp/B0018BQMUM/ref=sr_1_2?s=electronics&ie=UTF...

Extreme Broadband BDS102H 2-Way Digital Coax Splitter: http://www.amazon.com/EXTREME-DIGITAL-PERFORMANCE-CABLE-SPLITTER/dp/B007YV0UQW

Holland 2-way horizontal splitter 5-1000 MHz with ground.http://www.3starinc.com/holland_2-way_horizontal_splitter_5-1000_mhz-w-ground.html

Sv-2g 2-way Splitter 5-1000mhz: http://www.amazon.com/Sv-2g-2-way-Splitter-5-1000mhz-Sv2g/dp/B003TH36CK

Look on Amazon for high quality RG6 coax cable and compression fittings.

Unfortunately, it didn't solve the problem. Just ran into another slowdown 😞 How can I escalate it to Comcast to maybe send a technician?

ping google.com

PING google.com (172.217.164.110): 56 data bytes

64 bytes from 172.217.164.110: icmp_seq=0 ttl=54 time=477.703 ms

64 bytes from 172.217.164.110: icmp_seq=1 ttl=54 time=410.560 ms

64 bytes from 172.217.164.110: icmp_seq=2 ttl=54 time=390.360 ms

64 bytes from 172.217.164.110: icmp_seq=3 ttl=54 time=491.980 ms

64 bytes from 172.217.164.110: icmp_seq=4 ttl=54 time=695.457 ms

64 bytes from 172.217.164.110: icmp_seq=5 ttl=54 time=367.230 ms

64 bytes from 172.217.164.110: icmp_seq=6 ttl=54 time=648.874 ms

Request timeout for icmp_seq 7

64 bytes from 172.217.164.110: icmp_seq=8 ttl=54 time=901.170 ms

64 bytes from 172.217.164.110: icmp_seq=9 ttl=54 time=855.526 ms

Request timeout for icmp_seq 10

64 bytes from 172.217.164.110: icmp_seq=10 ttl=54 time=1599.596 ms

64 bytes from 172.217.164.110: icmp_seq=11 ttl=54 time=1509.966 ms

64 bytes from 172.217.164.110: icmp_seq=12 ttl=54 time=1523.819 ms

64 bytes from 172.217.164.110: icmp_seq=13 ttl=54 time=1133.900 ms

64 bytes from 172.217.164.110: icmp_seq=14 ttl=54 time=1617.865 ms

64 bytes from 172.217.164.110: icmp_seq=15 ttl=54 time=1278.725 ms

64 bytes from 172.217.164.110: icmp_seq=16 ttl=54 time=1375.204 ms

64 bytes from 172.217.164.110: icmp_seq=17 ttl=54 time=1090.479 ms

64 bytes from 172.217.164.110: icmp_seq=18 ttl=54 time=1863.399 ms

64 bytes from 172.217.164.110: icmp_seq=19 ttl=54 time=1703.222 ms

64 bytes from 172.217.164.110: icmp_seq=20 ttl=54 time=1961.580 ms

64 bytes from 172.217.164.110: icmp_seq=21 ttl=54 time=1818.299 ms

Request timeout for icmp_seq 23

64 bytes from 172.217.164.110: icmp_seq=22 ttl=54 time=2181.274 ms

64 bytes from 172.217.164.110: icmp_seq=23 ttl=54 time=2013.676 ms

64 bytes from 172.217.164.110: icmp_seq=24 ttl=54 time=2111.472 ms

64 bytes from 172.217.164.110: icmp_seq=25 ttl=54 time=1904.868 ms

64 bytes from 172.217.164.110: icmp_seq=26 ttl=54 time=2059.071 ms

64 bytes from 172.217.164.110: icmp_seq=27 ttl=54 time=1842.700 ms

64 bytes from 172.217.164.110: icmp_seq=28 ttl=54 time=1909.451 ms

64 bytes from 172.217.164.110: icmp_seq=29 ttl=54 time=2233.418 ms

64 bytes from 172.217.164.110: icmp_seq=30 ttl=54 time=2417.243 ms

64 bytes from 172.217.164.110: icmp_seq=31 ttl=54 time=2016.866 ms

64 bytes from 172.217.164.110: icmp_seq=32 ttl=54 time=2796.990 ms

64 bytes from 172.217.164.110: icmp_seq=33 ttl=54 time=2867.477 ms

Request timeout for icmp_seq 36

64 bytes from 172.217.164.110: icmp_seq=34 ttl=54 time=3320.085 ms

64 bytes from 172.217.164.110: icmp_seq=35 ttl=54 time=3354.215 ms

64 bytes from 172.217.164.110: icmp_seq=36 ttl=54 time=3774.617 ms

64 bytes from 172.217.164.110: icmp_seq=37 ttl=54 time=3592.125 ms

Request timeout for icmp_seq 41

64 bytes from 172.217.164.110: icmp_seq=38 ttl=54 time=4484.495 ms

64 bytes from 172.217.164.110: icmp_seq=39 ttl=54 time=4454.970 ms

64 bytes from 172.217.164.110: icmp_seq=40 ttl=54 time=4939.266 ms

64 bytes from 172.217.164.110: icmp_seq=41 ttl=54 time=4679.145 ms

Request timeout for icmp_seq 46

64 bytes from 172.217.164.110: icmp_seq=42 ttl=54 time=5245.843 ms

64 bytes from 172.217.164.110: icmp_seq=43 ttl=54 time=4942.949 ms

64 bytes from 172.217.164.110: icmp_seq=44 ttl=54 time=5268.556 ms

64 bytes from 172.217.164.110: icmp_seq=45 ttl=54 time=5076.755 ms

64 bytes from 172.217.164.110: icmp_seq=46 ttl=54 time=5407.261 ms

64 bytes from 172.217.164.110: icmp_seq=47 ttl=54 time=5615.502 ms

64 bytes from 172.217.164.110: icmp_seq=48 ttl=54 time=5496.112 ms

64 bytes from 172.217.164.110: icmp_seq=49 ttl=54 time=4948.270 ms

64 bytes from 172.217.164.110: icmp_seq=50 ttl=54 time=5413.834 ms

64 bytes from 172.217.164.110: icmp_seq=51 ttl=54 time=4983.363 ms

64 bytes from 172.217.164.110: icmp_seq=52 ttl=54 time=5555.131 ms

64 bytes from 172.217.164.110: icmp_seq=53 ttl=54 time=4857.313 ms

64 bytes from 172.217.164.110: icmp_seq=54 ttl=54 time=4466.627 ms

Almost a 14dB improvement on some channels ! The modem has also locked on to some different / better / cleaner channel frequencies.

In order to exclude my in-house wiring from the equation, I connected the modem directly to the input cable. It seems the numbers improved. Will live like for a few days to see if it really cures the problem.

It sounds like it's a problem with your side of the demarc point / your premises wiring. If it is, you may be charged for the tech visit. You can book a tech visit at 1800comcast.

In an attempt to pinpoint the problem, I replaced all of my in-house equipment (wiring, cable modem, wifi router) with the 'latest and greatest' devices. Still seeing latency spikes 😞

PING google.com (172.217.6.46): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 172.217.6.46: icmp_seq=0 ttl=54 time=1359.301 ms
Request timeout for icmp_seq 2
64 bytes from 172.217.6.46: icmp_seq=1 ttl=54 time=2365.476 ms
64 bytes from 172.217.6.46: icmp_seq=2 ttl=54 time=2974.349 ms
Request timeout for icmp_seq 5
64 bytes from 172.217.6.46: icmp_seq=3 ttl=54 time=4000.302 ms
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
64 bytes from 172.217.6.46: icmp_seq=4 ttl=54 time=5194.913 ms
--- google.com ping statistics ---
11 packets transmitted, 5 packets received, 54.5% packet loss
round-trip min/avg/max/stddev = 1359.301/3178.868/5194.913/1323.136 ms

Scheduled a technician visit. The first available appointment was on 04/09. I guess I'll have to wait till then.

@BrantleyIV 

Please create your own new topic here on this board detailing your issue, thanks. 9 month old dead thread now being closed.

Any update after scheduling the tech visit? Dealing with the same issue now. Thanks!