OK. Definitely not Ping Plotter...
The next step is determine which hop in the route this latency is *starting* at. To do this, set your "# of times to trace" to 5. Run the trace to your destination. Set your "samples to include" to "ALL", then Edit / Copy as Text. Replace back here with the collected data (feel free to XXX out any data in your route you feel comprimises your security - such as the IP address at hop 1, etc.). Here's an example when I trace to that destination myself...
Target Name:
www.attbi.com IP: 63.240.76.8
Date/Time: 6/16/2002 9:38:52 PM
1 1 ms 1 ms 1 ms 1 ms 1 ms [10.0.0.1]
2 51 ms 50 ms 50 ms 51 ms 52 ms [205.160.15.3]
3 61 ms 52 ms 52 ms 51 ms 52 ms [205.160.15.2]
4 80 ms 68 ms 69 ms 69 ms 69 ms sl-gw7-che-5-0-0-ts22.sprintlink.net [144.232.251.105]
5 73 ms 68 ms 70 ms 69 ms 70 ms sl-bb20-che-0-0.sprintlink.net [144.232.15.246]
6 106 ms 104 ms 108 ms 107 ms 103 ms sl-bb21-tac-9-0.sprintlink.net [144.232.18.10]
7 105 ms 109 ms 106 ms 105 ms 107 ms sl-bb21-sea-8-2.sprintlink.net [144.232.9.222]
8 105 ms 105 ms 102 ms 107 ms 111 ms sprint-gw.st6wa.ip.att.net [192.205.32.173]
9 105 ms 106 ms 104 ms 105 ms 104 ms gbr4-p40.st6wa.ip.att.net [12.123.44.134]
10 119 ms 118 ms 126 ms 118 ms 125 ms tbr2-p012702.cgcil.ip.att.net [12.122.11.209]
11 117 ms 117 ms 120 ms 119 ms 137 ms tbr1-p013902.cgcil.ip.att.net [12.122.11.205]
12 137 ms 136 ms 136 ms 135 ms 137 ms tbr1-p012402.n54ny.ip.att.net [12.122.11.213]
13 134 ms 136 ms 135 ms 135 ms 155 ms gbr2-p10.n54ny.ip.att.net [12.122.11.6]
14 137 ms 133 ms 135 ms 136 ms 135 ms gar1-p370.n54ny.ip.att.net [12.123.1.133]
15 137 ms 135 ms 136 ms 135 ms 135 ms mdf1-gsr12-2-pos2-0.nyc3.attens.net [12.122.255.162]
16 139 ms 138 ms 140 ms 144 ms 139 ms sccsbix11-1-4.attbi.com [63.240.64.34]
17 135 ms 135 ms 133 ms 134 ms 141 ms
www.attbi.com [63.240.76.8]
Ping statistics for
www.attbi.comPackets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 133ms, Maximum = 141ms, Average = 135ms
You can probably summarize which hop it's starting at by just talking about it here - but having some data to look at is always good too...
If this slowness is happening close to you (ie: hop 1-3), then this is something to do with your ISP. Try playing around with different destinations to see if it's all destinations or just a few of them. Once you've (we've) determined where the likely source of the problem is, you can create a strategy on solving the problem (ie: who to contact).
Now, before we get too far, what kind of performance do you see regularily? Is this something that you notice when you're using your browser or playing online games? Tying the data you're seeing to some problem that's affecting you is an important part of getting something fixed. If these symptoms aren't causing you any other problems, then you're going to have a hard time convincing anyone that they should be helping at all.
Previous Topic
Index
