dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
588
share rss forum feed

SpHeRe31459

join:2002-10-09
Sacramento, CA
kudos:1

1 edit

[Speed] Network problems for the past day or so

As of last night (was gone for the day) and continuing all today various websites have been really slow to load. When I do a trace route various hops along the Comcast backbone appear to be dropping randomly. If that's the case I'm surprised more people haven't reported this.

My service is generally rock solid, so I don't think it's just my problem.... But I have been seeing occasional drops at my cable modem's IP when I run tracert, so I supposed it could be the modem suddenly is getting flaky.

EMTA/Cable Modem is an Arris TM722G

Downstream 1 5.83 dBmV 36.17 dB 256QAM
Downstream 2 6.55 dBmV 36.39 dB 256QAM
Downstream 3 5.71 dBmV 36.61 dB 256QAM
Downstream 4 6.57 dBmV 36.61 dB 256QAM

Upstream 1 47.00 dBmV DOCSIS 2.0 64QAM
Upstream 3 47.00 dBmV DOCSIS 2.0 64QAM
Upstream 4 49.50 dBmV DOCSIS 1.x 16QAM

Example Tracert output:
Tracing route to hotmail.com [65.55.72.151]
over a maximum of 30 hops:

1 3 ms 3 ms 4 ms 192.168.1.1
2 * 13 ms 14 ms 96.120.14.33
3 20 ms 11 ms 14 ms te-6-8-ur08.sacramento.ca.ccal.comcast.net [69.139.197.49]
4 34 ms 49 ms * c-69-139-222-49.hsd1.az.comcast.net [69.139.222. 49]
5 19 ms 21 ms 16 ms pos-0-3-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.90.17]
6 21 ms * 19 ms pos-0-2-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.87.182]
7 20 ms 16 ms * pos-0-0-0-0-pe01.529bryant.ca.ibone.comcast.net [68.86.86.122]
8 * * * Request timed out.
9 30 ms 24 ms 23 ms ge-7-1-0-0.pao-64cb-1b.ntwk.msn.net [207.46.40.163]
10 * 27 ms 17 ms xe-4-1-2-0.bay-16c-1b.ntwk.msn.net [207.46.40.24]
11 62 ms 59 ms 57 ms xe-8-0-0-0.sn1-96cb-1a.ntwk.msn.net [207.46.43.117]
12 * * * Request timed out.
13 57 ms 59 ms 58 ms origin.sn132w.snt132.mail.live.com [65.55.72.151]

Trace complete.

Tracing route to www.google.com [74.125.129.105]
over a maximum of 30 hops:

1 2 ms 3 ms 3 ms 192.168.1.1
2 14 ms 16 ms 14 ms 96.120.14.33
3 11 ms 18 ms 14 ms te-6-8-ur09.sacramento.ca.ccal.comcast.net [69.139.197.57]
4 21 ms * 18 ms c-69-139-222-93.hsd1.az.comcast.net [69.139.222.93]
5 * 22 ms 17 ms ge-1-41-ur01.reedley.ca.fresno.comcast.net [68.85.196.73]
6 23 ms 18 ms 25 ms pos-0-0-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.90.125]
7 * * 31 ms pos-0-6-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.86.202]
8 22 ms 24 ms 22 ms pos-0-0-0-0-pe01.529bryant.ca.ibone.comcast.net[68.86.86.122]
9 * 80 ms 83 ms 66.208.228.226
10 24 ms 25 ms * 72.14.232.138
11 24 ms 22 ms * 209.85.250.66
12 37 ms 37 ms * 216.239.49.198
13 54 ms 39 ms * 72.14.233.202
14 38 ms 52 ms 39 ms 64.233.174.131
15 * * * Request timed out.
16 39 ms 41 ms 47 ms pd-in-f105.1e100.net [74.125.129.105]

Trace complete.


Oedipus

join:2005-05-09
kudos:1

Just because a tracert hop doesn't respond doesn't mean that it's indicative of a problem.


SpHeRe31459

join:2002-10-09
Sacramento, CA
kudos:1

1 edit

Yeah I know that, but there's clearly something wrong. The hops that do respond often drop one of the three pings. All kinds of websites load incredibly slowly and/or timeout entirely....
So I'm using the tools at my disposal to check it out....


SpHeRe31459

join:2002-10-09
Sacramento, CA
kudos:1
reply to SpHeRe31459

Got into the Comcast Account site from work (since it failed to load from home every time). And it shows that

"There is a known technical issue in your area. Technicians are working toward a resolution."

So I guess that's good, and I'm not crazy, and it's not my equipment.


Extide

join:2000-06-11
84129
reply to SpHeRe31459

Even after the service issue has been fixed, you will still see random dropouts on tracert's. That is normal.



EG
The wings of love
Premium
join:2006-11-18
Union, NJ
kudos:9

said by Extide:

Even after the service issue has been fixed, you will still see random dropouts on tracert's. That is normal.

It's "normal" as long as they don't propagate to the farther upstream hops and to the destination server. If they do, it may indeed indicate an actual packet loss issue.