Hey anyone...
I need posts of your trace routes to 192.12.119.204 for the Mass area
I want to see if anyone else drops or timeouts at certain places. I know we all connect though different IP's, but I want to see if your tracert's will show something.
Thanks
[JiF]Crash
post up your tracert's
-
- Forum User
- Posts: 76
- Joined: Fri Aug 25, 2006 12:45 pm
post up your tracert's
[JiF]Crash (Jiffer since 2002)
-
- Forum User
- Posts: 244
- Joined: Thu Aug 24, 2006 11:39 am
- Location: Worcester, MA
1 2 ms 1 ms 1 ms 1942.jiff.net [192.12.119.204]
2 9 ms 7 ms 7 ms 10.83.64.1
3 10 ms 9 ms 7 ms 172.20.15.21
4 11 ms 9 ms 9 ms 172.20.15.97
5 * 18 ms 20 ms so-7-1.car2.Boston1.Level3.net [4.79.0.89]
6 30 ms 18 ms 17 ms ae-5-5.ebr1.NewYork1.Level3.net [4.69.132.250]
7 194 ms 204 ms 204 ms ae-13-55.car3.NewYork1.Level3.net [4.68.97.146]
8 17 ms 15 ms 15 ms att-level3-oc192.NewYork1.Level3.net [4.68.127.150]
9 23 ms 21 ms 21 ms tbr2-p011601.n54ny.ip.att.net [12.123.3.61]
10 23 ms 23 ms 23 ms tbr1-cl16.cb1ma.ip.att.net [12.122.10.21]
11 23 ms 21 ms 22 ms gbr2-p80.cb1ma.ip.att.net [12.122.5.62]
12 21 ms 22 ms 21 ms gar3-p370.cb1ma.ip.att.net [12.123.40.189]
13 25 ms 27 ms 23 ms 12.125.47.34
14 * * * Request timed out.
15 27 ms 25 ms 24 ms 1942.jiff.net [192.12.119.204]
Trace complete.
2 9 ms 7 ms 7 ms 10.83.64.1
3 10 ms 9 ms 7 ms 172.20.15.21
4 11 ms 9 ms 9 ms 172.20.15.97
5 * 18 ms 20 ms so-7-1.car2.Boston1.Level3.net [4.79.0.89]
6 30 ms 18 ms 17 ms ae-5-5.ebr1.NewYork1.Level3.net [4.69.132.250]
7 194 ms 204 ms 204 ms ae-13-55.car3.NewYork1.Level3.net [4.68.97.146]
8 17 ms 15 ms 15 ms att-level3-oc192.NewYork1.Level3.net [4.68.127.150]
9 23 ms 21 ms 21 ms tbr2-p011601.n54ny.ip.att.net [12.123.3.61]
10 23 ms 23 ms 23 ms tbr1-cl16.cb1ma.ip.att.net [12.122.10.21]
11 23 ms 21 ms 22 ms gbr2-p80.cb1ma.ip.att.net [12.122.5.62]
12 21 ms 22 ms 21 ms gar3-p370.cb1ma.ip.att.net [12.123.40.189]
13 25 ms 27 ms 23 ms 12.125.47.34
14 * * * Request timed out.
15 27 ms 25 ms 24 ms 1942.jiff.net [192.12.119.204]
Trace complete.
- [JiF][AARP]Grimp
- Moderator
- Posts: 3803
- Joined: Thu Aug 24, 2006 9:23 pm
- Location: Massachusetts
- [JiF][AARP]Grimp
- Moderator
- Posts: 3803
- Joined: Thu Aug 24, 2006 9:23 pm
- Location: Massachusetts
I would not get too excited about drops and time outs in the middle of the trace route unless it affects the destination.
If your send 20 to the host and 20 come back in a resonable time the traceroute drops in the middle are not really a big deal.
If you drop them on a straight ping you got issues.
Pinging 192.12.119.204 with 32 bytes of data:
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=26ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=25ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=22ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=25ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=30ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=31ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=41ms TTL=113
Reply from 192.12.119.204: bytes=32 time=30ms TTL=113
Reply from 192.12.119.204: bytes=32 time=26ms TTL=113
Reply from 192.12.119.204: bytes=32 time=27ms TTL=113
Reply from 192.12.119.204: bytes=32 time=25ms TTL=113
Reply from 192.12.119.204: bytes=32 time=29ms TTL=113
Reply from 192.12.119.204: bytes=32 time=26ms TTL=113
Reply from 192.12.119.204: bytes=32 time=40ms TTL=113
Reply from 192.12.119.204: bytes=32 time=29ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=26ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=28ms TTL=113
Reply from 192.12.119.204: bytes=32 time=25ms TTL=113
Reply from 192.12.119.204: bytes=32 time=26ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=28ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=27ms TTL=113
Reply from 192.12.119.204: bytes=32 time=34ms TTL=113
Reply from 192.12.119.204: bytes=32 time=25ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=27ms TTL=113
Reply from 192.12.119.204: bytes=32 time=28ms TTL=113
Ping statistics for 192.12.119.204:
Packets: Sent = 46, Received = 46, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 41ms, Average = 26ms
If your send 20 to the host and 20 come back in a resonable time the traceroute drops in the middle are not really a big deal.
If you drop them on a straight ping you got issues.
Pinging 192.12.119.204 with 32 bytes of data:
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=26ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=25ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=22ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=25ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=30ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=31ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=41ms TTL=113
Reply from 192.12.119.204: bytes=32 time=30ms TTL=113
Reply from 192.12.119.204: bytes=32 time=26ms TTL=113
Reply from 192.12.119.204: bytes=32 time=27ms TTL=113
Reply from 192.12.119.204: bytes=32 time=25ms TTL=113
Reply from 192.12.119.204: bytes=32 time=29ms TTL=113
Reply from 192.12.119.204: bytes=32 time=26ms TTL=113
Reply from 192.12.119.204: bytes=32 time=40ms TTL=113
Reply from 192.12.119.204: bytes=32 time=29ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=26ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=28ms TTL=113
Reply from 192.12.119.204: bytes=32 time=25ms TTL=113
Reply from 192.12.119.204: bytes=32 time=26ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=28ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=27ms TTL=113
Reply from 192.12.119.204: bytes=32 time=34ms TTL=113
Reply from 192.12.119.204: bytes=32 time=25ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=24ms TTL=113
Reply from 192.12.119.204: bytes=32 time=23ms TTL=113
Reply from 192.12.119.204: bytes=32 time=27ms TTL=113
Reply from 192.12.119.204: bytes=32 time=28ms TTL=113
Ping statistics for 192.12.119.204:
Packets: Sent = 46, Received = 46, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 41ms, Average = 26ms