Basic Internet Connectivity And Modem Help

[waingro7]

Same troubles different night AGAIN... There's been on & off outages on their end lately (at least in Seattle area) and NOW the upload speed has died. The speedtest won't even run it. I've taken my router out of the mix and power cycled the modem for a direct connection and same result.

I ran pings on the DNS servers (they recently switched to 75.75.75.75 & 75.75.76.76) and I'm getting 30% packet loss on one and 60% packet loss on the other. I tried the old ones (68.87.85.102 & 68.87.69.150) and they're spotty as well with 40% & 16% packet loss.

Web browsing is noticeably choppy, it hangs, loads fast, then hangs, loads etc. Running ESPN (POWERED BY XFINITY!) & Netflix yields the same up and down quality issues in the picture.

I JUST HAD a tech out here to check the connection inside and outside... ALL GOOD.

But of course NONE OF THIS is Comcast's issue... it's my equipment or something else!

This is what they call an UPGRADE?! This is progress?!

[waingro7]

Just tried calling in and WHAT A SURPRISE... can't get through due to higher than normal call volume! Waiting... waiting...

[MillerTIme86]

Be prepared for a long wait with a 70% chance of disconnection while they put you back on hold. Good luck.

[waingro7]

Never got throught last night... lost patience. Yet HERE WE GO AGAIN TONIGHT... started at 8:30 getting hangs on web browsing... pages taking a long time to load. Speed test acting erratic. Ran the pings to the DNS servers again... same spotty packet loss. What the heck is going on?! I'm getting seriously fed up with this, it's becoming a nightly thing now.

[waingro7]

Got through to Comcast... same old stuff. They tell me they can't tell whether it's a signal delivery problem or something else like hardware (i.e. a bad modem). The guy said he was seeing the packet loss on his end but otherwise they've got no ideas or answers other than check cables, splitter etc.

Well I did that, bypassed the spitter, no change. Changed the cable to the wall, no change. That leaves just the modem. Tech was out here, tested signals & connections and were all good. So I left it last night after hitting the reset all defaults in the configuration tab on the modem access (through browser).

Now of course today everything is working fine! Speed test is running smooth... speeds are good. Interestingly the packet loss has cleared up on 75.75.75.75 but still showing around 50-60% on 75.75.76.76.

Last night web browsing was almost impossible... XBox Live connected but voice & connection to game were choppy and repeatedly dropped.

I'll have to check it today... and check it all again Sunday night. Modem seems to be in a recurring pattern when it fails. Trying to get a replacement to see if that clears up the issue.

[waingro7]

From LAST NIGHT 2/2/12...

Traceroute has started…

traceroute to 75.75.76.76 (75.75.76.76), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  1.082 ms  0.376 ms  0.356 ms

 2  73.98.44.1 (73.98.44.1)  9.326 ms  9.372 ms  9.807 ms

 3  te-4-1-ur06.burien.wa.seattle.comcast.net (68.87.205.185)  10.137 ms  9.320 ms  10.070 ms

 4  ae-9-0-ar03.seattle.wa.seattle.comcast.net (69.139.164.41)  10.494 ms *  25.550 ms

 5  pos-1-11-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.93.101)  12.847 ms

    pos-1-4-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.90.209)  12.143 ms

    pos-1-13-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.95.21)  15.418 ms

 6  te-7-1-ar01.saltlakecity.ut.utah.comcast.net (68.86.90.186)  37.038 ms  37.549 ms *

 7  te-8-1-ur05.saltlakecity.ut.utah.comcast.net (68.86.199.130)  38.684 ms  38.020 ms  37.923 ms

 8  cdns02.comcast.net (75.75.76.76)  37.824 ms  37.477 ms  37.860 ms

Ping has started…

PING 75.75.76.76 (75.75.76.76): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

Request timeout for icmp_seq 6

64 bytes from 75.75.76.76: icmp_seq=7 ttl=56 time=37.927 ms

64 bytes from 75.75.76.76: icmp_seq=8 ttl=56 time=37.588 ms

64 bytes from 75.75.76.76: icmp_seq=9 ttl=56 time=37.611 ms

64 bytes from 75.75.76.76: icmp_seq=10 ttl=56 time=39.481 ms

64 bytes from 75.75.76.76: icmp_seq=11 ttl=56 time=37.383 ms

64 bytes from 75.75.76.76: icmp_seq=12 ttl=56 time=52.021 ms

64 bytes from 75.75.76.76: icmp_seq=13 ttl=56 time=37.435 ms

64 bytes from 75.75.76.76: icmp_seq=14 ttl=56 time=53.753 ms

64 bytes from 75.75.76.76: icmp_seq=15 ttl=56 time=44.229 ms

64 bytes from 75.75.76.76: icmp_seq=16 ttl=56 time=55.974 ms

64 bytes from 75.75.76.76: icmp_seq=17 ttl=56 time=37.117 ms

64 bytes from 75.75.76.76: icmp_seq=18 ttl=56 time=37.516 ms

64 bytes from 75.75.76.76: icmp_seq=19 ttl=56 time=37.143 ms

64 bytes from 75.75.76.76: icmp_seq=20 ttl=56 time=36.967 ms

Request timeout for icmp_seq 21

Request timeout for icmp_seq 22

Request timeout for icmp_seq 23

Request timeout for icmp_seq 24

Request timeout for icmp_seq 25

Request timeout for icmp_seq 26

Request timeout for icmp_seq 27

Request timeout for icmp_seq 28

--- 75.75.76.76 ping statistics ---

30 packets transmitted, 14 packets received, 53.3% packet loss

round-trip min/avg/max/stddev = 36.967/41.582/55.974/6.724 ms

Traceroute has started…

traceroute to 75.75.75.75 (75.75.75.75), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  0.996 ms  0.394 ms  0.386 ms

 2  73.98.44.1 (73.98.44.1)  9.645 ms  9.189 ms  10.350 ms

 3  te-4-1-ur05.burien.wa.seattle.comcast.net (68.87.205.177)  9.958 ms  9.671 ms  9.945 ms

 4  ae-9-0-ar03.burien.wa.seattle.comcast.net (69.139.164.37)  99.200 ms  9.804 ms  10.159 ms

 5  ae-2-0-ar03.seattle.wa.seattle.comcast.net (68.86.177.146)  22.410 ms  11.408 ms  10.294 ms

 6  pos-1-11-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.93.101)  16.023 ms

    pos-1-10-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.93.97)  11.761 ms

    pos-1-14-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.90.85)  14.881 ms

 7  * so-6-0-0-0-ar03.troutdale.or.bverton.comcast.net (68.86.95.98)  28.708 ms  14.803 ms

 8  te-7-4-ur01.beaverton.or.bverton.comcast.net (68.87.216.41)  16.467 ms  17.008 ms  15.912 ms

 9  cdns01.comcast.net (75.75.75.75)  30.487 ms  17.125 ms  15.726 ms

Ping has started…

PING 75.75.75.75 (75.75.75.75): 56 data bytes

64 bytes from 75.75.75.75: icmp_seq=0 ttl=56 time=15.936 ms

64 bytes from 75.75.75.75: icmp_seq=1 ttl=56 time=15.626 ms

64 bytes from 75.75.75.75: icmp_seq=2 ttl=56 time=15.520 ms

64 bytes from 75.75.75.75: icmp_seq=3 ttl=56 time=15.660 ms

64 bytes from 75.75.75.75: icmp_seq=4 ttl=56 time=15.601 ms

64 bytes from 75.75.75.75: icmp_seq=5 ttl=56 time=15.536 ms

Request timeout for icmp_seq 6

64 bytes from 75.75.75.75: icmp_seq=7 ttl=56 time=15.421 ms

Request timeout for icmp_seq 8

64 bytes from 75.75.75.75: icmp_seq=9 ttl=56 time=50.575 ms

64 bytes from 75.75.75.75: icmp_seq=10 ttl=56 time=15.329 ms

64 bytes from 75.75.75.75: icmp_seq=11 ttl=56 time=15.180 ms

64 bytes from 75.75.75.75: icmp_seq=12 ttl=56 time=15.084 ms

64 bytes from 75.75.75.75: icmp_seq=13 ttl=56 time=15.174 ms

64 bytes from 75.75.75.75: icmp_seq=14 ttl=56 time=15.064 ms

64 bytes from 75.75.75.75: icmp_seq=15 ttl=56 time=15.307 ms

64 bytes from 75.75.75.75: icmp_seq=16 ttl=56 time=15.010 ms

64 bytes from 75.75.75.75: icmp_seq=17 ttl=56 time=15.122 ms

Request timeout for icmp_seq 18

64 bytes from 75.75.75.75: icmp_seq=19 ttl=56 time=30.544 ms

64 bytes from 75.75.75.75: icmp_seq=20 ttl=56 time=16.669 ms

Request timeout for icmp_seq 21

Request timeout for icmp_seq 22

Request timeout for icmp_seq 23

64 bytes from 75.75.75.75: icmp_seq=24 ttl=56 time=29.052 ms

64 bytes from 75.75.75.75: icmp_seq=25 ttl=56 time=20.552 ms

Request timeout for icmp_seq 26

64 bytes from 75.75.75.75: icmp_seq=27 ttl=56 time=16.344 ms

64 bytes from 75.75.75.75: icmp_seq=28 ttl=56 time=20.639 ms

64 bytes from 75.75.75.75: icmp_seq=29 ttl=56 time=16.238 ms

--- 75.75.75.75 ping statistics ---

30 packets transmitted, 23 packets received, 23.3% packet loss

round-trip min/avg/max/stddev = 15.010/18.747/50.575/7.950 ms

[waingro7]

Signals from last night...

[waingro7]

From TODAY 2/4/12...

Traceroute has started…

traceroute to 75.75.76.76 (75.75.76.76), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  0.907 ms  0.520 ms  0.349 ms

 2  73.98.44.1 (73.98.44.1)  10.659 ms  9.551 ms  10.011 ms

 3  te-4-1-ur06.burien.wa.seattle.comcast.net (68.87.205.185)  10.226 ms  11.488 ms  9.397 ms

 4  ae-9-0-ar03.seattle.wa.seattle.comcast.net (69.139.164.41)  10.360 ms  44.475 ms  21.784 ms

 5  pos-1-10-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.93.97)  23.508 ms

    pos-1-11-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.93.101)  11.663 ms

    pos-1-10-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.93.97)  12.341 ms

 6  te-7-1-ar01.saltlakecity.ut.utah.comcast.net (68.86.90.186)  38.216 ms  37.693 ms  37.980 ms

 7  te-8-1-ur05.saltlakecity.ut.utah.comcast.net (68.86.199.130)  38.614 ms  41.976 ms  42.317 ms

 8  cdns02.comcast.net (75.75.76.76)  38.603 ms  37.653 ms  38.242 ms

Ping has started…

PING 75.75.76.76 (75.75.76.76): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

64 bytes from 75.75.76.76: icmp_seq=5 ttl=56 time=37.296 ms

64 bytes from 75.75.76.76: icmp_seq=6 ttl=56 time=37.009 ms

64 bytes from 75.75.76.76: icmp_seq=7 ttl=56 time=39.490 ms

64 bytes from 75.75.76.76: icmp_seq=8 ttl=56 time=36.968 ms

64 bytes from 75.75.76.76: icmp_seq=9 ttl=56 time=37.170 ms

64 bytes from 75.75.76.76: icmp_seq=10 ttl=56 time=38.636 ms

64 bytes from 75.75.76.76: icmp_seq=11 ttl=56 time=38.472 ms

64 bytes from 75.75.76.76: icmp_seq=12 ttl=56 time=38.448 ms

64 bytes from 75.75.76.76: icmp_seq=13 ttl=56 time=38.775 ms

64 bytes from 75.75.76.76: icmp_seq=14 ttl=56 time=38.360 ms

64 bytes from 75.75.76.76: icmp_seq=15 ttl=56 time=38.231 ms

64 bytes from 75.75.76.76: icmp_seq=16 ttl=56 time=43.355 ms

64 bytes from 75.75.76.76: icmp_seq=17 ttl=56 time=59.192 ms

Request timeout for icmp_seq 18

Request timeout for icmp_seq 19

Request timeout for icmp_seq 20

Request timeout for icmp_seq 21

Request timeout for icmp_seq 22

Request timeout for icmp_seq 23

Request timeout for icmp_seq 24

Request timeout for icmp_seq 25

Request timeout for icmp_seq 26

Request timeout for icmp_seq 27

Request timeout for icmp_seq 28

--- 75.75.76.76 ping statistics ---

30 packets transmitted, 13 packets received, 56.7% packet loss

round-trip min/avg/max/stddev = 36.968/40.108/59.192/5.732 ms

Traceroute has started…

traceroute to 75.75.75.75 (75.75.75.75), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  1.005 ms  0.585 ms  0.579 ms

 2  73.98.44.1 (73.98.44.1)  10.260 ms  10.962 ms  9.645 ms

 3  te-4-1-ur05.burien.wa.seattle.comcast.net (68.87.205.177)  10.499 ms  9.688 ms  9.991 ms

 4  ae-9-0-ar03.burien.wa.seattle.comcast.net (69.139.164.37)  9.712 ms  9.603 ms  9.979 ms

 5  ae-3-0-ar03.seattle.wa.seattle.comcast.net (68.86.177.150)  12.972 ms  10.375 ms

    ae-2-0-ar03.seattle.wa.seattle.comcast.net (68.86.177.146)  10.006 ms

 6  pos-1-10-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.93.97)  15.224 ms

    pos-1-14-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.90.85)  11.162 ms

    pos-1-10-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.93.97)  14.582 ms

 7  so-6-0-0-0-ar03.troutdale.or.bverton.comcast.net (68.86.95.98)  19.635 ms  16.214 ms  15.799 ms

 8  te-7-4-ur01.beaverton.or.bverton.comcast.net (68.87.216.41)  17.687 ms  16.668 ms  15.822 ms

 9  cdns01.comcast.net (75.75.75.75)  15.516 ms  15.700 ms  15.974 ms

Ping has started…

PING 75.75.75.75 (75.75.75.75): 56 data bytes

64 bytes from 75.75.75.75: icmp_seq=0 ttl=56 time=14.495 ms

64 bytes from 75.75.75.75: icmp_seq=1 ttl=56 time=13.714 ms

64 bytes from 75.75.75.75: icmp_seq=2 ttl=56 time=15.570 ms

64 bytes from 75.75.75.75: icmp_seq=3 ttl=56 time=15.079 ms

64 bytes from 75.75.75.75: icmp_seq=4 ttl=56 time=14.618 ms

64 bytes from 75.75.75.75: icmp_seq=5 ttl=56 time=14.454 ms

64 bytes from 75.75.75.75: icmp_seq=6 ttl=56 time=15.070 ms

64 bytes from 75.75.75.75: icmp_seq=7 ttl=56 time=14.174 ms

64 bytes from 75.75.75.75: icmp_seq=8 ttl=56 time=28.254 ms

64 bytes from 75.75.75.75: icmp_seq=9 ttl=56 time=14.853 ms

64 bytes from 75.75.75.75: icmp_seq=10 ttl=56 time=14.763 ms

64 bytes from 75.75.75.75: icmp_seq=11 ttl=56 time=15.305 ms

64 bytes from 75.75.75.75: icmp_seq=12 ttl=56 time=13.905 ms

64 bytes from 75.75.75.75: icmp_seq=13 ttl=56 time=14.469 ms

64 bytes from 75.75.75.75: icmp_seq=14 ttl=56 time=13.775 ms

64 bytes from 75.75.75.75: icmp_seq=15 ttl=56 time=13.634 ms

64 bytes from 75.75.75.75: icmp_seq=16 ttl=56 time=14.123 ms

64 bytes from 75.75.75.75: icmp_seq=17 ttl=56 time=13.510 ms

64 bytes from 75.75.75.75: icmp_seq=18 ttl=56 time=13.347 ms

64 bytes from 75.75.75.75: icmp_seq=19 ttl=56 time=14.043 ms

64 bytes from 75.75.75.75: icmp_seq=20 ttl=56 time=14.022 ms

64 bytes from 75.75.75.75: icmp_seq=21 ttl=56 time=13.305 ms

64 bytes from 75.75.75.75: icmp_seq=22 ttl=56 time=13.206 ms

64 bytes from 75.75.75.75: icmp_seq=23 ttl=56 time=18.141 ms

64 bytes from 75.75.75.75: icmp_seq=24 ttl=56 time=15.623 ms

64 bytes from 75.75.75.75: icmp_seq=25 ttl=56 time=14.815 ms

64 bytes from 75.75.75.75: icmp_seq=26 ttl=56 time=17.438 ms

64 bytes from 75.75.75.75: icmp_seq=27 ttl=56 time=15.241 ms

64 bytes from 75.75.75.75: icmp_seq=28 ttl=56 time=14.988 ms

64 bytes from 75.75.75.75: icmp_seq=29 ttl=56 time=24.531 ms

--- 75.75.75.75 ping statistics ---

30 packets transmitted, 30 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 13.206/15.415/28.254/3.161 ms

[waingro7]

Signals from today...

[waingro7]

Modem log from last night scrolling down showing some stuff from Sun 1/29. It's all clear today after a reset in the Configuration tab. Might only be temporary though... I did the same last Friday night and here we are again a week later. 

[waingro7]

I'll have to run Shaperprobe again when it's acting up...

DiffProbe release. January 2012.
Shaper Detection Module.

Connected to server 203.5.76.139.

Estimating capacity:
Upstream: 5117 Kbps.
Downstream: 35320 Kbps.

The measurement will last for about 2.5 minutes. Please wait.

Checking for traffic shapers:

Upstream: No shaper detected.
Median received rate: 5114 Kbps.

[acwong]

Hello - Saw your post and I am running into the same issue here in Martinez, CA.  Called Comcast and they said that there were no issues.  The "support person" did say that my modem was out of sync, but offered no solutions.  Were you able to resolve your issue?  If yes, what did they do?

[waingro7]

So everything was working PERFECTLY Sat afternoon... speed test running with no hangs, speeds good... ESPN with full 3 bars and great picture on XBox Live. Unfortunately I couldn't hang around to see how it did Sat night...

BUT here we are again Sunday night 9pm... Same old problems. Speeds have dropped, browsing is choppy, speedtest runs then hangs and won't start upload test, packet loss is back etc. So what gives here... this stuff is happening at such a consistent recurring time it doesn't make any sense.

Here's the latest. Like I've seen on other folks... Shaperprobe aborts due to high packet loss...

Last login: Sun Feb  5 20:52:32 on console

DiffProbe release. January 2012.

Shaper Detection Module.

Connected to server 38.106.70.175.

Estimating capacity:

Upstream: 944 Kbps.

Downstream: 1 Kbps.

The measurement will last for about 2.5 minutes. Please wait.

Checking for traffic shapers:

Upstream: Measurement aborted due to high packet loss rate.

Traceroute has started…

traceroute to 75.75.75.75 (75.75.75.75), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  0.914 ms  0.588 ms  0.466 ms

 2  73.98.44.1 (73.98.44.1)  8.613 ms  8.886 ms  7.768 ms

 3  te-4-1-ur05.burien.wa.seattle.comcast.net (68.87.205.177)  10.160 ms  9.731 ms  8.766 ms

 4  ae-9-0-ar03.burien.wa.seattle.comcast.net (69.139.164.37)  9.947 ms  27.136 ms  7.472 ms

 5  ae-2-0-ar03.seattle.wa.seattle.comcast.net (68.86.177.146)  8.511 ms

    ae-3-0-ar03.seattle.wa.seattle.comcast.net (68.86.177.150)  12.521 ms

    ae-2-0-ar03.seattle.wa.seattle.comcast.net (68.86.177.146)  8.725 ms

 6  pos-1-12-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.93.93)  12.903 ms *

    pos-1-14-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.90.85)  26.614 ms

 7  * * so-6-0-0-0-ar03.troutdale.or.bverton.comcast.net (68.86.95.98)  14.026 ms

 8  te-7-4-ur01.beaverton.or.bverton.comcast.net (68.87.216.41)  13.541 ms  67.089 ms  14.106 ms

 9  * cdns01.comcast.net (75.75.75.75)  14.285 ms *

Ping has started…

PING 75.75.75.75 (75.75.75.75): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

64 bytes from 75.75.75.75: icmp_seq=2 ttl=56 time=14.483 ms

64 bytes from 75.75.75.75: icmp_seq=3 ttl=56 time=14.188 ms

64 bytes from 75.75.75.75: icmp_seq=4 ttl=56 time=30.122 ms

Request timeout for icmp_seq 5

Request timeout for icmp_seq 6

Request timeout for icmp_seq 7

64 bytes from 75.75.75.75: icmp_seq=8 ttl=56 time=14.921 ms

64 bytes from 75.75.75.75: icmp_seq=9 ttl=56 time=14.210 ms

64 bytes from 75.75.75.75: icmp_seq=10 ttl=56 time=14.184 ms

64 bytes from 75.75.75.75: icmp_seq=11 ttl=56 time=14.144 ms

64 bytes from 75.75.75.75: icmp_seq=12 ttl=56 time=28.666 ms

Request timeout for icmp_seq 13

Request timeout for icmp_seq 14

64 bytes from 75.75.75.75: icmp_seq=15 ttl=56 time=27.804 ms

Request timeout for icmp_seq 16

64 bytes from 75.75.75.75: icmp_seq=17 ttl=56 time=13.368 ms

Request timeout for icmp_seq 18

64 bytes from 75.75.75.75: icmp_seq=19 ttl=56 time=13.120 ms

64 bytes from 75.75.75.75: icmp_seq=20 ttl=56 time=13.070 ms

Request timeout for icmp_seq 21

Request timeout for icmp_seq 22

Request timeout for icmp_seq 23

Request timeout for icmp_seq 24

Request timeout for icmp_seq 25

64 bytes from 75.75.75.75: icmp_seq=26 ttl=56 time=14.533 ms

64 bytes from 75.75.75.75: icmp_seq=27 ttl=56 time=14.608 ms

64 bytes from 75.75.75.75: icmp_seq=28 ttl=56 time=14.344 ms

64 bytes from 75.75.75.75: icmp_seq=29 ttl=56 time=28.588 ms

--- 75.75.75.75 ping statistics ---

30 packets transmitted, 16 packets received, 46.7% packet loss

round-trip min/avg/max/stddev = 13.070/17.772/30.122/6.397 ms

Traceroute has started…

traceroute to 75.75.76.76 (75.75.76.76), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  0.955 ms  0.553 ms  0.385 ms

 2  73.98.44.1 (73.98.44.1)  9.162 ms * *

 3  * te-4-1-ur06.burien.wa.seattle.comcast.net (68.87.205.185)  26.374 ms  9.699 ms

 4  ae-9-0-ar03.seattle.wa.seattle.comcast.net (69.139.164.41)  8.259 ms  8.377 ms  9.327 ms

 5  * pos-1-13-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.95.21)  27.227 ms

    pos-1-11-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.93.101)  11.013 ms

 6  * * te-7-1-ar01.saltlakecity.ut.utah.comcast.net (68.86.90.186)  36.661 ms

 7  te-8-1-ur05.saltlakecity.ut.utah.comcast.net (68.86.199.130)  38.588 ms * *

 8  cdns02.comcast.net (75.75.76.76)  54.416 ms  36.304 ms  35.127 ms

Ping has started…

PING 75.75.76.76 (75.75.76.76): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

64 bytes from 75.75.76.76: icmp_seq=6 ttl=56 time=36.023 ms

64 bytes from 75.75.76.76: icmp_seq=7 ttl=56 time=35.966 ms

64 bytes from 75.75.76.76: icmp_seq=8 ttl=56 time=35.802 ms

64 bytes from 75.75.76.76: icmp_seq=9 ttl=56 time=48.660 ms

Request timeout for icmp_seq 10

64 bytes from 75.75.76.76: icmp_seq=11 ttl=56 time=36.098 ms

64 bytes from 75.75.76.76: icmp_seq=12 ttl=56 time=55.372 ms

64 bytes from 75.75.76.76: icmp_seq=13 ttl=56 time=58.419 ms

64 bytes from 75.75.76.76: icmp_seq=14 ttl=56 time=36.131 ms

64 bytes from 75.75.76.76: icmp_seq=15 ttl=56 time=35.843 ms

64 bytes from 75.75.76.76: icmp_seq=16 ttl=56 time=35.837 ms

64 bytes from 75.75.76.76: icmp_seq=17 ttl=56 time=34.952 ms

Request timeout for icmp_seq 18

Request timeout for icmp_seq 19

Request timeout for icmp_seq 20

Request timeout for icmp_seq 21

Request timeout for icmp_seq 22

Request timeout for icmp_seq 23

Request timeout for icmp_seq 24

Request timeout for icmp_seq 25

Request timeout for icmp_seq 26

Request timeout for icmp_seq 27

Request timeout for icmp_seq 28

--- 75.75.76.76 ping statistics ---

30 packets transmitted, 11 packets received, 63.3% packet loss

round-trip min/avg/max/stddev = 34.952/40.828/58.419/8.437 ms

[waingro7]

Modem signals... Nothing in the log since I reset defaults which wiped it clean. I might try this again and see if it resolves the issue.

Channel ID	67	65	66	68
Frequency	579000000 Hz	567000000 Hz	573000000 Hz	585000000 Hz
Signal to Noise Ratio	38 dB	37 dB	37 dB	38 dB
Downstream Modulation	QAM256	QAM256	QAM256	QAM256
Power Level The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading	5 dBmV	4 dBmV	4 dBmV	5 dBmV

Upstream Bonding Channel Value

Channel ID	1	3
Frequency	30600000 Hz	37000000 Hz
Ranging Service ID	11	11
Symbol Rate	5.120 Msym/sec	5.120 Msym/sec
Power Level	47 dBmV	48 dBmV
Upstream Modulation	[3] QPSK [3] 64QAM	[3] QPSK [3] 64QAM
Ranging Status	Success	Success

Signal Stats (Codewords) Bonding Channel Value

Channel ID	67	65	66	68
Total Unerrored Codewords	7076980404	2782013198	2782013604	2782013558
Total Correctable Codewords	396	409	357	316
Total Uncorrectable Codewords	1601	1450	1503	1332

[waingro7]

Tried the reset all defaults on the modem... half hour later and no improvement but I'm sure by tomorrow morning everything will be running smoothly again. Connection is COMPLETELY USELESS TONIGHT. Tried running the speedtest got a “DOWNLOAD TEST ERROR. Download test returned an error while trying to read the download file”... Never seen that before!

Shaperprobe FAILS again on the upstream due to high packet loss.

Last login: Sun Feb  5 22:31:38 on ttys000

DiffProbe release. January 2012.

Shaper Detection Module.

Connected to server 64.9.225.153.

Estimating capacity:

Upstream: 453 Kbps.

Downstream: 36364 Kbps.

The measurement will last for about 4.5 minutes. Please wait.

Checking for traffic shapers:

Upstream: Measurement aborted due to high packet loss rate.

Anybody from Comcast want to escalate this issue and actually get someone from Networking on the problem? Other folks are having the same problems.

[waingro7]

8pm - 9pm... just like clockwork connection starts to go bad.

Shaperprobe actually ran... upload on speed test didnt...

Last login: Mon Feb  6 12:32:33 on ttys000

DiffProbe release. January 2012.

Shaper Detection Module.

Connected to server 213.244.128.168.

Estimating capacity:

Upstream: 277 Kbps.

Downstream: 0 Kbps.

The measurement will last for about 2.5 minutes. Please wait.

Checking for traffic shapers:

Upstream: No shaper detected.

Median received rate: 616 Kbps.

Segmentation fault

logout

[Process completed]

[Andrewgd]

Any updates? I've been having problems connecting (but only to certain sites, others work fine, then they all work fine minutes later)... 

Not sure I want to deal with Comcast customer support...

[waingro7]

Well after a lot of outages and consistent drops of service in the evenings the problem was finally taken care of by reprovisioning my modem. Kind of weird that nobody I spoke to on the phone offered to do that since that's who you call when you have a new modem. No issues since, connection is back to normal. YAY.

[Andrewgd]

Awesome. Thanks for the reply! I'll try that next.