Slow Internet, did tracert and ping, heres results.

[Marinski]

Internet has been very slow for the past week. Many calls to comcast and hours spent on the phone with nothing acomplished. They are sending a tech out on tuesday to check it out. Im learning to use trace router and ping. I'd much appreciate if somebody with a little more experience with this can help interpret it. Did 3 trace routes to: google.com,yahoo.com, and microsoft.com and a ping. On the second hop of each trace there is a request timed out (not sure if this means anything) and the ping 50% packets lost. Heres the results.

C:\Documents and Settings\HP_Owner>tracert www.google.com

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

1 1 ms <1 ms <1 ms 72.14.203.104
2 * * * Request timed out.
3 8 ms * 7 ms ge-2-2-ur02.macomb.mi.michigan.comcast.net [68.8
6.120.113]
4 10 ms 8 ms 9 ms te-9-2-ur02.clinton3.mi.michigan.comcast.net [68
.87.190.245]
5 * 7 ms * te-9-2-ur02.clinton2.mi.michigan.comcast.net [68
.87.190.241]
6 12 ms 9 ms * te-9-2-ur02.fraser.mi.michigan.comcast.net [68.8
7.190.237]
7 11 ms 9 ms 9 ms te-9-1-ur03.stclairshors.mi.michigan.comcast.net
[68.87.190.233]
8 16 ms * * te-9-3-ur02.stclairshors.mi.michigan.comcast.net
[68.87.190.229]
9 21 ms 31 ms 11 ms te-9-2-ur02.grosspoint.mi.michigan.comcast.net [
68.87.190.225]
10 11 ms 20 ms 9 ms te-8-2-ur03.lyndon.mi.michigan.comcast.net [68.8
7.190.221]
11 21 ms 8 ms * te-8-1-ur02.lyndon.mi.michigan.comcast.net [68.8
7.190.217]
12 10 ms * * te-9-2-ar02.taylor.mi.michigan.comcast.net [68.8
7.190.213]
13 * * * Request timed out.
14 23 ms * 11 ms 12.124.15.169
15 * 20 ms * gbr2-p70.dtrmi.ip.att.net [12.123.139.26]
16 37 ms 18 ms 19 ms tbr2-p012601.dtrmi.ip.att.net [12.122.12.181]
17 * * * Request timed out.
18 18 ms 17 ms 17 ms 12.123.6.25
19 30 ms 18 ms 17 ms so-8-1.car4.Chicago1.Level3.net [209.0.227.77]
20 41 ms 18 ms 18 ms ae-11-53.car1.Chicago1.Level3.net [4.68.101.66]

21 18 ms 19 ms 18 ms 4.79.208.18
22 18 ms 18 ms 28 ms 72.14.232.53
23 18 ms 19 ms 18 ms 72.14.232.46
24 21 ms 33 ms 20 ms 64.233.175.94
25 21 ms 18 ms 22 ms 72.14.203.104

Trace complete.

C:\Documents and Settings\HP_Owner>ping google.com

Pinging google.com [72.14.207.99] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=56ms TTL=232
Request timed out.
Reply from 72.14.207.99: bytes=32 time=55ms TTL=232
Request timed out.

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 56ms, Average = 55ms

C:\Documents and Settings\HP_Owner>tracert www.yahoo.com

Tracing route to www.yahoo.akadns.net [216.109.118.78]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms p15.www.dcn.yahoo.com [216.109.118.78]
2 * * * Request timed out.
3 9 ms 8 ms 9 ms ge-2-2-ur02.macomb.mi.michigan.comcast.net [68.8
6.120.113]
4 9 ms 11 ms * te-9-2-ur02.clinton3.mi.michigan.comcast.net [68
.87.190.245]
5 * * 7 ms te-9-2-ur02.clinton2.mi.michigan.comcast.net [68
.87.190.241]
6 10 ms 10 ms 20 ms te-9-2-ur02.fraser.mi.michigan.comcast.net [68.8
7.190.237]
7 18 ms * 10 ms te-9-1-ur03.stclairshors.mi.michigan.comcast.net
[68.87.190.233]
8 20 ms 9 ms 10 ms te-9-3-ur02.stclairshors.mi.michigan.comcast.net
[68.87.190.229]
9 13 ms 20 ms 11 ms te-9-2-ur02.grosspoint.mi.michigan.comcast.net [
68.87.190.225]
10 * * 17 ms te-8-2-ur03.lyndon.mi.michigan.comcast.net [68.8
7.190.221]
11 26 ms * 11 ms te-8-1-ur02.lyndon.mi.michigan.comcast.net [68.8
7.190.217]
12 13 ms 11 ms 29 ms te-9-2-ar02.taylor.mi.michigan.comcast.net [68.8
7.190.213]
13 * * * Request timed out.
14 12 ms 11 ms 11 ms 12.124.15.169
15 30 ms 29 ms * gbr1-p70.dtrmi.ip.att.net [12.123.139.22]
16 41 ms * 47 ms tbr1-p012501.dtrmi.ip.att.net [12.122.12.169]
17 31 ms 29 ms 41 ms tbr2-cl19.phlpa.ip.att.net [12.122.10.38]
18 36 ms 36 ms 45 ms tbr1-cl9.wswdc.ip.att.net [12.122.2.85]
19 * 42 ms 28 ms 12.122.81.245
20 * * * Request timed out.
21 * 76 ms 65 ms ae1.p420.msr2.dcn.yahoo.com [216.115.96.185]
22 45 ms 43 ms 33 ms 216.109.120.201
23 30 ms 71 ms 28 ms p15.www.dcn.yahoo.com [216.109.118.78]

Trace complete.

C:\Documents and Settings\HP_Owner>tracert www.microsoft.com

Tracing route to lb1.www.ms.akadns.net [207.46.20.60]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 207.46.20.60
2 * * * Request timed out.
3 7 ms 8 ms * ge-2-2-ur02.macomb.mi.michigan.comcast.net [68.8
6.120.113]
4 7 ms * 12 ms te-9-2-ur02.clinton3.mi.michigan.comcast.net [68
.87.190.245]
5 10 ms * * te-9-2-ur02.clinton2.mi.michigan.comcast.net [68
.87.190.241]
6 * 26 ms 12 ms te-9-2-ur02.fraser.mi.michigan.comcast.net [68.8
7.190.237]
7 * * 10 ms te-9-1-ur03.stclairshors.mi.michigan.comcast.net
[68.87.190.233]
8 * 8 ms * te-9-3-ur02.stclairshors.mi.michigan.comcast.net
[68.87.190.229]
9 18 ms * * te-9-2-ur02.grosspoint.mi.michigan.comcast.net [
68.87.190.225]
10 54 ms 30 ms 56 ms te-8-2-ur03.lyndon.mi.michigan.comcast.net [68.8
7.190.221]
11 22 ms 17 ms * te-8-1-ur02.lyndon.mi.michigan.comcast.net [68.8
7.190.217]
12 * 19 ms * te-9-2-ar02.taylor.mi.michigan.comcast.net [68.8
7.190.213]
13 13 ms 12 ms * pos-6-1-ar01.taylor.mi.michigan.comcast.net [68.
87.191.149]
14 39 ms * * 12.118.112.13
15 * * * Request timed out.
16 63 ms 69 ms 68 ms tbr2-cl18.cgcil.ip.att.net [12.122.10.134]
17 63 ms * 62 ms tbr1-cl22.cgcil.ip.att.net [12.122.9.133]
18 * 62 ms 94 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
19 79 ms 61 ms 59 ms 12.123.12.57
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 

[James Bond]

Well, even though it says its timing out on the 2nd hop each trace route, that doesn't necessarily meaning you're running slow.
Each connection to the internet has to jump through several routers to get to its destination... You'll notice that the first few hops are always the same, thats because its going through your router, to your isp, then your isp is routing it in certain directions. That second hop, even though it says its timing out, basically is just 'now allowing you to see it', and it returns a time-out error. Since its happening near your isp, it will happen every time you traceroute anything.

Your ping wasn't going too slow, but it did lose some packets which is definitely no good.
You might try pinging a few more sites, and running some speed tests: http://www.dslreports.com/stest

Tyler