Results 11 to 14 of 14
Thread: Help with Tracert
-
-
-
03-10-10, 03:39 PM #13
Re: Help with Tracert
Same;
1, -------------- ,192.168.1.1
2,,-
3,ge-7-43-ur01.troutdale.or.bverton.comcast.net,68.85.148.49
4,te-9-3-ar01.troutdale.or.bverton.comcast.net,68.87.216.89
5,te-0-0-0-1-cr01.seattle.wa.ibone.comcast.net,68.86.90.81
6,te-3-2.car1.Seattle1.Level3.net,4.79.104.105
7,ae-32-52.ebr2.Seattle1.Level3.net,4.68.105.62
8,ae-2-2.ebr2.Denver1.Level3.net,4.69.132.54
9,ae-1-100.ebr1.Denver1.Level3.net,4.69.132.37
10,ae-2-2.ebr2.Dallas1.Level3.net,4.69.132.106
11,ae-3-80.edge3.Dallas1.Level3.net,4.69.145.136
12,DATABANK-HO.edge3.Dallas1.Level3.net,4.71.170.6
13,dbce10glt.layeredtech.com,66.18.0.142
14,,-
15,dallas.hypernia.com,72.233.112.146
2 and 14 missing
-
03-12-10, 06:02 PM #14
Re: Help with Tracert
Your largest ping increase is on the Level 3 fiber ring from Seattle to Denver (hop7 to hop8). This is expected.
You have a very brief increase in latency by 30 ms on the Comcast Seattle backbone (hop5)
You have another brief increase in latency by 40 ms on a Level 3 edge router. (hop11)
Keep in mind though, traceroutes stop being useful when the issue is intermittent.
This doesnt say much. Since you show no consistant lag.
You will need to
A) Test latency during your worst period of lag
B) Do a pathping test or ping plot along this host route to determine consistant sources of lag.
C) Test other hosts within the same area (similar routes) to see if its server peer related.
Even than there isn't much of anything you can do unless the problem is on premise (in your home), or on-net (within Comcast or first peer)
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks