SG Broadband Community

Can someone help me interpret this tracert. Ive been having some serious slow down problems lately and im sure its comcasts fault (imagine that) lol


C:\Documents and Settings\Matt>tracert yahoo.com

Tracing route to yahoo.com [216.109.112.135]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 9 ms 8 ms 73.22.224.1
3 8 ms * 9 ms GE-2-16-ur02.pompanobeach.fl.pompano.comcast.net
[68.86.161.133]
4 11 ms 7 ms * te-9-1-ur01.pompanobeach.fl.pompano.comcast.net
[68.86.164.81]
5 9 ms * 15 ms te-9-4-ur01.hallandale.fl.pompano.comcast.net [6
8.86.164.77]
6 10 ms 9 ms * te-9-4-ur02.northdade.fl.pompano.comcast.net [68
.86.164.73]
7 * 44 ms 44 ms te-9-4-ur01.northdade.fl.pompano.comcast.net [68
.86.164.69]
8 43 ms 44 ms 43 ms te-9-4-ur03.northdade.fl.pompano.comcast.net [68
.86.165.2]
9 45 ms 43 ms 42 ms te-9-3-ar01.northdade.fl.pompano.comcast.net [68
.86.164.65]
10 48 ms 47 ms 48 ms te-2-3.car2.Miami1.Level3.net [4.79.98.1]
11 * 65 ms * ae-4-4.ebr2.Atlanta2.Level3.net [4.69.133.10]
12 66 ms 55 ms 70 ms ae-1-100.ebr1.Atlanta2.Level3.net [4.69.132.33]

13 78 ms 72 ms 71 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
14 70 ms 72 ms * ae-11-51.car1.Washington1.Level3.net [4.68.121.1
8]
15 * 72 ms 71 ms 4.79.228.2
16 76 ms * 74 ms ge-0-0-0-p110.msr2.dcn.yahoo.com [216.115.108.5]

17 73 ms * 72 ms ge7-1.bas1-m.dcn.yahoo.com [216.109.120.205]
18 69 ms 70 ms 70 ms w2.rc.vip.dcn.yahoo.com [216.109.112.135]

Trace complete.

C:\Documents and Settings\Matt>

Your tracerts look good though imho it could be a few things causing the slowdowns though. We could try tweaking a few other things to make it go faster.

What's ur speeds now?

actually doenst really look that good....

the PINGS are very good...but the HOPS are too many = slower.

consider this....18 hops to reach Yahoo and another 18 hops to get back.....total = 36 hops

the more hops you take the worse problems if any trouble happend in any of the hops, in fact it's faster having 100ms and 10 hops than 50ms and 20 hops.

your connection is fine though, nothing you can do about it unless its some configuration or tweak needed.

Let me ask you this...

Define your slow connection to me, not just by pinging Yahoo! web site main page, which that will almost always be fast, since they spent a fortune getting descent pipes to the Internet for their web servers.

Are you only doing Yahoo! in your tests or are other site being slower, if that is the case, ping their site and let's see the numbers.

Not all servers have the same TTL, latency, and bandwidth that Yahoo has for their web servers, so it's really comparing apples to oranges. I can better help you if you can tell me if it's slow all the time or during certain hours and if you are running other applications that require a lot of processor power and network resources, there are so many variables we need to rule out first.