Tracert's

**11Bravo** · 11-30-07, 09:44 PM

[img width=700 height=559]http://i177.photobucket.com/albums/w206/pathfinder75thb/Trace-30Nov.jpg[/img]

http://i177.photobucket.com/albums/w...race-30Nov.jpg

**Benandorf** · 11-30-07, 11:25 PM

Not hard, guys. Right click on the window, click select all, then hit Enter to copy it. Paste it here, and viola.

**Blue_Thunder27** · 12-01-07, 03:43 AM

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Nico>tracert 64.182.81.109

Tracing route to danfish1.propagation.net [64.182.81.109]
over a maximum of 30 hops:

1 9 ms 9 ms 9 ms adsl-69-109-59-254.dsl.irvnca.pacbell.net [69.10
9.59.254]
2 9 ms 9 ms 9 ms dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]

3 9 ms 10 ms 10 ms bb2-g4-0.irvnca.sbcglobal.net [151.164.43.143]
4 10 ms 10 ms 11 ms 151.164.93.167
5 11 ms 11 ms 10 ms bpr2-ge-2-1-0.LosAngelesEquinix.savvis.net [151.
164.248.214]
6 34 ms 19 ms 11 ms cr2-pos-0-0-3-0.lay.savvis.net [204.70.203.50]
7 * * * Request timed out.
8 * * * Request timed out.
9 44 ms 44 ms 44 ms 208.172.130.130
10 44 ms 44 ms 44 ms 64.182.192.37
11 44 ms 45 ms 44 ms danfish1.propagation.net [64.182.81.109]

Trace complete.

C:\Documents and Settings\Nico>tracert 64.182.81.109

Tracing route to danfish1.propagation.net [64.182.81.109]
over a maximum of 30 hops:

1 10 ms 9 ms 9 ms adsl-69-109-59-254.dsl.irvnca.pacbell.net [69.10
9.59.254]
2 10 ms 9 ms 9 ms dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]

3 10 ms 9 ms 10 ms bb2-g4-0.irvnca.sbcglobal.net [151.164.43.143]
4 11 ms 10 ms 10 ms 151.164.93.167
5 10 ms 11 ms 10 ms bpr2-ge-2-1-0.LosAngelesEquinix.savvis.net [151.
164.248.214]
6 11 ms * 12 ms cr2-pos-0-0-3-0.lay.savvis.net [204.70.203.50]
7 * * * Request timed out.
8 * * * Request timed out.
9 44 ms 44 ms 44 ms 208.172.130.130
10 45 ms 44 ms 44 ms 64.182.192.37
11 44 ms 44 ms 45 ms 64.182.81.109

Trace complete.

C:\Documents and Settings\Nico>tracert 64.182.81.109

Tracing route to 64.182.81.109 over a maximum of 30 hops

1 9 ms 9 ms 9 ms adsl-69-109-59-254.dsl.irvnca.pacbell.net [69.10
9.59.254]
2 10 ms 9 ms * dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]

3 10 ms 10 ms 9 ms bb2-g4-0.irvnca.sbcglobal.net [151.164.43.143]
4 10 ms 10 ms 10 ms 151.164.93.167
5 11 ms 10 ms 10 ms bpr2-ge-2-1-0.LosAngelesEquinix.savvis.net [151.
164.248.214]
6 12 ms 12 ms 13 ms cr2-pos-0-0-3-0.lay.savvis.net [204.70.203.50]
7 * * * Request timed out.
8 * * * Request timed out.
9 45 ms 43 ms 44 ms 208.172.130.130
10 44 ms 44 ms 44 ms 64.182.192.37
11 45 ms 45 ms 44 ms danfish1.propagation.net [64.182.81.109]

Trace complete.

C:\Documents and Settings\Nico>

**11Bravo** · 12-01-07, 08:32 PM

Seems to me that Dallas.Savvis.Net is the culprit. Timeout's are never good. It means that it took too long to get a response.

**cop1991** · 12-01-07, 08:45 PM

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

D:\Documents and Settings\Garrett>tracert 72.232.220.90

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 <1 ms 141 ms <1 ms 192.168.0.1
2 23 ms 15 ms 14 ms 73.140.73.1
3 7 ms * 12 ms ge-3-2-ur01.va.richmond.comcast.net [68
.86.127.229]
4 13 ms 12 ms * 68.86.172.222
5 14 ms 13 ms 16 ms po-50-ar01.staplesmllrd.va.richmond.comcast.net
[68.86.172.162]
6 26 ms 34 ms 19 ms COMCAST-IP.edge1.Washington1.Level3.net [4.79.23
1.14]
7 19 ms 19 ms 16 ms xe-11-2-0.edge1.Washington1.Level3.net [4.79.231
.13]
8 22 ms 15 ms 15 ms vlan89.csw3.Washington1.Level3.net [4.68.17.190]

9 18 ms 28 ms 17 ms ae-81-81.ebr1.Washington1.Level3.net [4.69.134.1
37]
10 41 ms 32 ms 34 ms ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
11 196 ms 152 ms 91 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21]
12 51 ms 47 ms 50 ms ae-63-63.csw1.Dallas1.Level3.net [4.69.136.154]

13 51 ms 49 ms 51 ms ae-12-69.car2.Dallas1.Level3.net [4.68.19.4]
14 49 ms 49 ms 49 ms DATABANK-HO.car2.Dallas1.Level3.net [4.71.170.2]

15 49 ms 54 ms 48 ms 63.164.96.databank.com [63.164.96.62]
16 49 ms 51 ms 50 ms lt-pod2a.lt.com [63.164.96.226]
17 * * * Request timed out.
18 50 ms 293 ms 88 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

Trace complete.

Mine to the new 2142 server.

**...bigdog...** · 12-01-07, 10:03 PM

that god damn level 3 fucking rotuaskheagfkj;lakj;ldskj;lasdkj;lklaj;dfskjldsf

**KromMonkey** · 12-01-07, 10:31 PM

Here are a series of traces to the 2142 server (72.232.220.90) which I did over a 15 minute period. I have 2 hops (6 &10) that are timing out and on occassion the following hop will tank which is causing me "snapshot" lag every 15 seconds or so.

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 3 ms 4 ms 4 ms 71.244.18.1
3 5 ms 4 ms 4 ms P15-1.LCR-01.DLLSTX.verizon-gni.net [130.81.37.5
0]
4 6 ms 7 ms 7 ms so-6-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.
81.17.173]
5 6 ms 7 ms 7 ms 64.128.212.137
6 * * * Request timed out.
7 7 ms 7 ms 7 ms 209.163.157.254
8 7 ms 7 ms 7 ms 63.164.96.databank.com [63.164.96.66]
9 6 ms 7 ms 7 ms lt-pod2b.lt.com [63.164.96.238]
10 * * * Request timed out.
11 7 ms 9 ms 14 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms 71.244.18.1
3 3 ms 4 ms 4 ms P15-1.LCR-01.DLLSTX.verizon-gni.net [130.81.37
0]
4 6 ms 19 ms 24 ms so-6-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [13
81.17.173]
5 5 ms 7 ms 7 ms 64.128.212.137
6 * * * Request timed out.
7 7 ms 11 ms 6 ms 209.163.157.254
8 7 ms 7 ms 7 ms 63.164.96.databank.com [63.164.96.58]
9 6 ms 7 ms 7 ms lt-pod2b.lt.com [63.164.96.238]
10 * * * Request timed out.
11 8 ms 14 ms 7 ms 90.220.232.72.static.reverse.ltdomains.com [72
32.220.90]

Trace complete.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 4 ms 4 ms 71.244.18.1
3 5 ms 4 ms 4 ms P15-1.LCR-01.DLLSTX.verizon-gni.net [130.81.37.5
0]
4 6 ms 7 ms 7 ms so-6-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.
81.17.173]
5 6 ms 7 ms 7 ms 64.128.212.137
6 * * * Request timed out.
7 6 ms 7 ms 7 ms 209.163.157.254
8 6 ms 7 ms 7 ms 63.164.96.databank.com [63.164.96.66]
9 7 ms 7 ms 7 ms lt-pod2a.lt.com [63.164.96.226]
10 * * * Request timed out.
11 11 ms 12 ms 7 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 3 ms 4 ms 4 ms 71.244.18.1
3 3 ms 5 ms 4 ms P15-1.LCR-01.DLLSTX.verizon-gni.net [130.81.37.5
0]
4 6 ms 7 ms 7 ms so-6-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.
81.17.173]
5 6 ms 7 ms 7 ms 64.128.212.137
6 * * * Request timed out.
7 1012 ms 7 ms 7 ms 209.163.157.254
8 7 ms 7 ms 7 ms 63.164.96.databank.com [63.164.96.66]
9 6 ms 7 ms 7 ms lt-pod2a.lt.com [63.164.96.226]
10 * * * Request timed out.
11 7 ms 7 ms 7 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

Trace complete.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 4 ms 4 ms 71.244.18.1
3 3 ms 4 ms 4 ms P15-1.LCR-01.DLLSTX.verizon-gni.net [130.81.37.5
0]
4 6 ms 7 ms 7 ms so-6-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.
81.17.173]
5 6 ms 7 ms 7 ms 64.128.212.137
6 * * * Request timed out. 7 7 ms 7 ms 7 ms 209.163.157.254
8 7 ms 7 ms 7 ms 63.164.96.databank.com [63.164.96.58]
9 6 ms 7 ms 7 ms lt-pod2a.lt.com [63.164.96.226]
10 * * * Request timed out.
11 285 ms 7 ms 19 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

Trace complete.

**IronStomach** · 12-02-07, 12:54 AM

Here's a strange one for ya...

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Me>tracert 72.232.220.90

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 7 ms 7 ms 7 ms rd1bb-ge5-0-0-16.vc.shawcable.net [64.59.158.242
]
4 8 ms 7 ms 17 ms rc1bb-pos15-0-0.vc.shawcable.net [66.163.69.121]

5 11 ms 11 ms 11 ms rc1wt-pos4-0-0.wa.shawcable.net [66.163.76.126]

6 33 ms 32 ms 32 ms rc1sj-pos0-0.cl.shawcable.net [66.163.77.70]
7 32 ms 33 ms 35 ms snjs.equinix.twtelecom.net [206.223.116.36]
8 * * * Request timed out.
9 1649 ms 74 ms 87 ms 209.163.157.254
10 75 ms 76 ms 76 ms 63.164.96.databank.com [63.164.96.58]
11 75 ms 76 ms 76 ms lt-pod2a.lt.com [63.164.96.226]
12 * * * Request timed out.
13 64 ms 74 ms 64 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

Trace complete.

**KromMonkey** · 12-02-07, 11:12 AM

Here are 2 more from this morning ran back to back to show that the issue is consistent and and not just occuring in the evening. Again, this is to the 2142 server.

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms FAILTE.home [192.168.1.1]
2 3 ms 4 ms 4 ms 71.244.18.1
3 3 ms 4 ms 4 ms P15-1.LCR-01.DLLSTX.verizon-gni.net [130.81.37.5
0]
4 6 ms 7 ms 7 ms so-6-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.81.17.173]
5 7 ms 7 ms 7 ms 64.128.212.137
6 * * * Request timed out.
7 355 ms 7 ms 7 ms 209.163.157.254 8 6 ms 7 ms 7 ms 63.164.96.databank.com [63.164.96.58]
9 6 ms 7 ms 7 ms lt-pod2b.lt.com [63.164.96.238]
10 * * * Request timed out.
11 5 ms 7 ms 7 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

Trace complete.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms FAILTE.home [192.168.1.1]
2 3 ms 17 ms 4 ms 71.244.18.1
3 3 ms 4 ms 4 ms P15-1.LCR-01.DLLSTX.verizon-gni.net [130.81.37.5
0]
4 6 ms 7 ms 7 ms so-6-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.81.17.173]
5 6 ms 7 ms 22 ms 64.128.212.137
6 * * * Request timed out. 7 5 ms 7 ms 7 ms 209.163.157.254
8 6 ms 7 ms 7 ms 63.164.96.databank.com [63.164.96.58]
9 6 ms 7 ms 7 ms lt-pod2b.lt.com [63.164.96.238]
10 * * * Request timed out.
11 8 ms 7 ms 7 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

Trace complete.

**Viktor_Olin** · 12-02-07, 09:12 PM

Unusually high pings for me tonight. I ran several tracerts, all of which gave results similar to this:

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.117.192.1
3 7 ms 8 ms 7 ms 172.22.33.45
4 10 ms 9 ms 10 ms atl-edge-18.inet.qwest.net [216.206.221.149]
5 17 ms 15 ms 17 ms atl-core-01.inet.qwest.net [205.171.21.161]
6 15 ms 15 ms 16 ms atl-brdr-04.inet.qwest.net [205.171.21.42]
7 17 ms 16 ms 16 ms sl-bb23-atl-10-3.sprintlink.net [144.232.9.85]
8 20 ms 17 ms 16 ms sl-bb24-atl-15-0.sprintlink.net [144.232.12.6]
9 17 ms 17 ms 17 ms sl-crs1-atl-0-12-0-3.sprintlink.net [144.232.12.35]
10 161 ms 159 ms 161 ms sl-crs1-fw-0-12-0-2.sprintlink.net [144.232.18.147]
11 161 ms 158 ms 159 ms sl-bb20-fw-15-0.sprintlink.net [144.232.11.143]
12 38 ms 37 ms 37 ms sl-st21-dal-13-0.sprintlink.net [144.232.20.81]
13 165 ms 166 ms 166 ms sl-lodst-128297-0.sprintlink.net [144.228.250.94]
14 161 ms 160 ms 166 ms 63.164.96.databank.com [63.164.96.54]
15 157 ms 157 ms 152 ms lt-pod2a.lt.com [63.164.96.226]
16 * * * Request timed out.
17 148 ms 149 ms 146 ms 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]

Trace complete.