Author Topic: Need some help from the community (Read 17234 times)

Skuzzy · « **on:** January 07, 2005, 05:15:08 PM »

As you may or may not be aware of, we have been trying to get an issue solved with Savvis, and its Chicago hub.

In this thread, I would like as many trace routes or PingPlots posted as possible from as many locations as possible. No proxy services please, we need real IP addresses.

First, trace to the Main Arena server 216.91.187.39.
Then trace to 216.39.66.70 and post that as well so we can do some comparisons on the results.

Thank you for the help folks, it is appreciated.

AWRoost · « **Reply #1 on:** January 07, 2005, 05:43:24 PM »

Skuzzy I have 2 plots for you but I am not allowed to post attachments. How to post these to you ?

Roost

MOSQ · « **Reply #2 on:** January 07, 2005, 06:03:32 PM »

Target Name: N/A
IP: 216.91.187.39
Date/Time: 1/7/2005 4:00:16 PM

1 3 ms 3 ms 3 ms 3 ms 3 ms [198.36.165.193]
2 8 ms 7 ms 10 ms 8 ms 8 ms por-edge-02.inet.qwest.net [63.227.220.37]
3 7 ms 24 ms 8 ms 9 ms 12 ms pdx-core-02.inet.qwest.net [205.171.130.17]
4 27 ms 31 ms 33 ms 27 ms 37 ms bur-core-02.inet.qwest.net [205.171.205.106]
5 27 ms 27 ms 27 ms 26 ms 33 ms lap-brdr-01.inet.qwest.net [205.171.213.50]
6 27 ms 28 ms 27 ms 59 ms 27 ms bpr1-so-6-0-0.LosAngelesEquinix.savvis.net [208.174.196.13]
7 27 ms 27 ms 31 ms 37 ms 27 ms dcr1-so-4-2-0.LosAngeles.savvis.net [208.172.44.105]
8 119 ms 119 ms 120 ms 119 ms 120 ms acr1.Denver.savvis.net [208.172.162.61]
9 138 ms 138 ms 162 ms 138 ms 166 ms [208.172.163.134]
10 105 ms 105 ms 109 ms 106 ms 134 ms [216.91.187.39]

Target Name: N/A
IP: 216.39.66.70
Date/Time: 1/7/2005 4:02:08 PM

1 3 ms 3 ms 3 ms [198.36.165.193]
2 17 ms 14 ms 8 ms por-edge-02.inet.qwest.net [63.227.220.37]
3 8 ms 26 ms 22 ms pdx-core-02.inet.qwest.net [205.171.130.17]
4 27 ms 26 ms 68 ms bur-core-02.inet.qwest.net [205.171.205.106]
5 31 ms 36 ms 41 ms lap-brdr-01.inet.qwest.net [205.171.213.50]
6 41 ms 27 ms 27 ms bpr1-so-6-0-0.LosAngelesEquinix.savvis.net [208.174.196.13]
7 46 ms 41 ms 55 ms dcr1-so-4-2-0.LosAngeles.savvis.net [208.172.44.105]
8 62 ms 61 ms 102 ms bcr1.Dallas.savvis.net [208.172.130.63]
9 62 ms 62 ms 79 ms ohr1-pos-4-0.FortWorthda1.savvis.net [208.172.131.82]
10 63 ms 66 ms 85 ms csr1-ve242.FortWorthda1.savvis.net [216.39.64.58]
11 64 ms 64 ms 62 ms [216.39.67.142]
12 62 ms 62 ms 79 ms [216.39.66.70]

214thCavalier · « **Reply #3 on:** January 07, 2005, 06:05:39 PM »

Text version tracing 216.91.187.39

,Sample Times,,08/01/2005 00:07:54,08/01/2005 00:07:57,08/01/2005 00:07:59,08/01/2005 00:08:02,08/01/2005 00:08:04,08/01/2005 00:08:07,08/01/2005 00:08:09,08/01/2005 00:08:12,08/01/2005 00:08:14,08/01/2005 00:08:17
1,SpeedTouch.lan,10.0.0.138,1,1,1,2,1,1,1,1,1,1
2,lon1-adsl6.nildram.net,213.208.106.124,20,18,19,21,18,20,19,32,18,18
3,lon1-10.nildram.net,213.208.106.195,19,19,19,19,17,19,20,19,19,19
4,lon1-6.nildram.net,195.149.20.132,19,18,18,18,20,19,18,19,16,17
5,ldn-b1-geth14-3.telia.net,213.248.100.69,18,19,19,19,19,18,18,19,19,17
6,cw-01448-ldn-b1.telia.net,213.248.74.214,19,20,19,19,18,18,21,18,17,20
7,dcr1-loopback.Chicago.savvis.net,208.172.2.99,129,128,128,177,126,127,128,128,128,127
8,acr2-so-0-0-0.Chicago.savvis.net,208.172.3.82,126,125,126,126,126,125,125,126,126,125
9, -------------- ,208.172.1.202,199,199,199,198,199,198,199,199,200,198
10, -------------- ,216.91.187.39,203,202,201,201,204,201,202,201,201,200

So why do i get a 75ms jump between hops 8 and 9 when its already across the pond and on Savvis network ?

Tracing to 216.39.66.70

,Sample Times,,08/01/2005 00:15:05,08/01/2005 00:15:08,08/01/2005 00:15:10,08/01/2005 00:15:13,08/01/2005 00:15:15,08/01/2005 00:15:18,08/01/2005 00:15:20,08/01/2005 00:15:23,08/01/2005 00:15:25,08/01/2005 00:15:28
1,SpeedTouch.lan,10.0.0.138,N/A,2,1,1,2,1,1,1,1,1
2,lon1-adsl6.nildram.net,213.208.106.124,24,17,23,18,19,19,48,19,19,19
3,lon1-10.nildram.net,213.208.106.195,20,19,19,19,19,19,20,19,18,19
4,lon1-6.nildram.net,195.149.20.132,19,18,18,18,18,18,20,18,20,19
5,246.ge6-0.mpr1.lhr1.uk.above.net,213.161.78.109,20,19,18,20,19,20,20,19,19,19
6,pos0-0.pr1.lhr1.uk.above.net,208.184.231.70,18,17,19,18,20,19,18,17,18,19
7,bcr1-ge-4-3-0.Londonlnx.savvis.net,195.66.224.39,20,19,19,19,19,19,19,19,19,20
8,bcr1.Dallas.savvis.net,208.172.130.63,124,124,127,125,125,149,124,125,123,126
9,ohr1-pos-4-0.FortWorthda1.savvis.net,208.172.131.82,125,123,124,123,125,126,125,125,124,126
10,csr1-ve242.FortWorthda1.savvis.net,216.39.64.58,124,126,202,125,500,125,124,125,125,125
11, -------------- ,216.39.67.142,125,125,124,124,124,125,126,124,125,123
12, -------------- ,216.39.66.70,127,126,125,124,126,126,125,127,124,126

From my point of view only seeing half the data the 216.39.66.70 route looks better if it was not for hop 10 csr1-ve242.FortWorthda1.savvis.net as it frequently spikes into the 400 or 500 hundred range. It only shows once here but every time i test for a count of 10 it registers a high spike.

Btw if you want to look at a wall of text let me know how many counts you want.

Skuzzy · « **Reply #4 on:** January 07, 2005, 06:12:23 PM »

Post them as text. You can save PingPlotter output as text and just do a cut and paste tot eh bulletin board post. Thank you.

nsty1 · « **Reply #5 on:** January 07, 2005, 06:18:20 PM »

Target Name: 216.91.187.39.
IP: 216.91.187.39
Date/Time: 1/7/2005 5:13:25 PM

1 114 ms nas1.albuquerque1.nm.us.da.qw est.net [67.0.192.1]
2 119 ms [67.0.192.62]
3 111 ms alb-core-02.inet.qwest.net [67.0.192.101]
4 104 ms alb-core-01.inet.qwest.net [205.171.151.9]
5 114 ms tsn-core-01.inet.qwest.net [205.171.205.122]
6 105 ms tsn-core-02.inet.qwest.net [205.171.149.14]
7 133 ms dal-core-01.inet.qwest.net [205.171.205.54]
8 136 ms dal-brdr-02.inet.qwest.net [205.171.25.46]
9 135 ms bcr1-so-3-0-0.Dallas.savvis.net [208.172.131.201]
10 192 ms acr1.Denver.savvis.net [208.172.162.61]
11 209 ms [208.172.163.134]
12 177 ms [216.91.187.39]

Ping statistics for 216.91.187.39.
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 177ms, Maximum = 177ms, Average = 177ms

Target Name: N/A
IP: 216.39.66.70
Date/Time: 1/7/2005 5:15:24 PM

1 129 ms nas1.albuquerque1.nm.us.da.qw est.net [67.0.192.1]
2 110 ms [67.0.192.93]
3 124 ms alb-core-01.inet.qwest.net [67.0.192.97]
4 119 ms tsn-core-01.inet.qwest.net [205.171.205.122]
5 111 ms tsn-core-02.inet.qwest.net [205.171.149.14]
6 149 ms dal-core-01.inet.qwest.net [205.171.205.54]
7 141 ms dal-brdr-02.inet.qwest.net [205.171.25.46]
8 158 ms bcr1-so-3-0-0.Dallas.savvis.net [208.172.131.201]
9 150 ms ohr1-pos-4-0.FortWorthda1.savvis.net [208.172.131.82]
10 143 ms csr1-ve242.FortWorthda1.savvis.net [216.39.64.58]
11 166 ms [216.39.67.142]
12 146 ms [216.39.66.70]

Ping statistics for 216.39.66.70
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 146ms, Maximum = 146ms, Average = 146ms

XtrmeJ · « **Reply #6 on:** January 07, 2005, 06:24:11 PM »

FYI Skuzzy, your link in the News, Announcement & Information Forum does not work.

Heater · « **Reply #7 on:** January 07, 2005, 06:26:14 PM »

Tracing route to 216.39.66.70 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.138
2 9 ms 8 ms 9 ms 195.190.244.169
3 10 ms 10 ms 10 ms 42.ge-2-1-1.xr1.d12.xs4all.net [194.109.5.133]
4 10 ms 11 ms 10 ms 0.so-2-3-0.xr1.sara.xs4all.net [194.109.5.102]
5 23 ms 10 ms 11 ms acr2-ge-3-1-0.Amsterdamamx.savvis.net [208.174.49.133]
6 10 ms 11 ms 10 ms acr1-ae0.Amsterdamamx.savvis.net [208.174.48.89]
7 127 ms 127 ms 127 ms bcr1.Dallas.savvis.net [208.172.130.63]
8 128 ms 128 ms 127 ms ohr1-pos-4-0.FortWorthda1.savvis.net [208.172.131.82]
9 399 ms 128 ms 128 ms csr1-ve242.FortWorthda1.savvis.net [216.39.64.58]
10 127 ms 128 ms 128 ms 216.39.67.142
11 129 ms 128 ms 129 ms 216.39.66.70

Trace complete.

Tracing route to 216.91.187.39 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.138
2 9 ms 8 ms 9 ms 195.190.244.169
3 9 ms 9 ms 10 ms 42.ge-2-1-1.xr2.d12.xs4all.net [194.109.5.149]
4 10 ms 10 ms 10 ms 0.so-3-3-0.xr1.sara.xs4all.net [194.109.5.106]
5 10 ms 10 ms 10 ms acr2-ge-3-1-0.Amsterdamamx.savvis.net [208.174.49.133]
6 11 ms 10 ms 10 ms acr1-ae0.Amsterdamamx.savvis.net [208.174.48.89]
7 110 ms 111 ms 111 ms dcr2-loopback.Chicago.savvis.net [208.172.2.100]
8 111 ms 111 ms 111 ms acr2-so-0-0-0.Chicago.savvis.net [208.172.3.82]
9 116 ms 117 ms 116 ms 208.172.1.202
10 116 ms 116 ms 117 ms 216.91.187.39

Trace complete.

Cheers

Roscoroo · « **Reply #8 on:** January 07, 2005, 06:28:11 PM »

my problems been with the SanJose' Savvis routor for the last month ...

but i already posted those If you need more i'll keep getting pingplots with that one .

BTW the info thread link doesnt work to here Skuzzy .

steely07 · « **Reply #9 on:** January 07, 2005, 06:35:25 PM »

Link from announcements is broken Skuzzy (it's been truncated,, "http://www.hitechcreations.com/foru...threadid=139562 ")

Target Name: N/A
IP: 216.39.66.70
Date/Time: 8/01/2005 11:33:47 AM

1 0 ms 0 ms 0 ms 0 ms [192.168.0.1]
2 11 ms 12 ms 11 ms 11 ms loop0.lns1.syd3.internode.on. net [150.101.197.97]
3 12 ms 10 ms 11 ms 13 ms fa0-0-227.cor1.syd3.internode.on.net [150.101.197.129]
4 13 ms 11 ms 11 ms 184 ms gi0-3.bdr1.syd1.agile.on.net [150.101.199.237]
5 170 ms 170 ms 170 ms 171 ms POS1-1.IG2.LAX9.ALTER.NET [208.222.8.221]
6 165 ms 166 ms 167 ms 166 ms 0.so-7-0-0.XR2.LAX9.ALTER.NET [152.63.116.86]
7 167 ms 165 ms 165 ms 166 ms 0.so-2-0-0.XL2.LAX9.ALTER.NET [152.63.115.166]
8 173 ms 171 ms 171 ms 171 ms POS7-0.BR3.LAX9.ALTER.NET [152.63.115.5]
9 166 ms 170 ms 167 ms 168 ms [204.255.173.14]
10 173 ms 171 ms 172 ms 172 ms dcr2-ae3.LosAngeles.savvis.net [208.172.44.133]
11 203 ms 200 ms 202 ms 200 ms bcr1.Dallas.savvis.net [208.172.130.63]
12 202 ms 203 ms 202 ms 201 ms ohr1-pos-4-0.FortWorthda1.savvis.net [208.172.131.82]
13 530 ms 201 ms 203 ms 201 ms csr1-ve242.FortWorthda1.savvis.net [216.39.64.58]
14 207 ms 202 ms 200 ms 202 ms [216.39.67.142]
15 204 ms 204 ms 201 ms 201 ms [216.39.66.70]

Ping statistics for 216.39.66.70
Packets: Sent = 4, Received = 4, Lost = 0 (0.0%)
Round Trip Times: Minimum = 201ms, Maximum = 204ms, Average = 202ms

Target Name: N/A
IP: 216.91.187.39
Date/Time: 8/01/2005 11:37:08 AM

1 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.0.1]
2 12 ms 11 ms 11 ms 12 ms 11 ms loop0.lns1.syd3.internode.on. net [150.101.197.97]
3 13 ms 12 ms 11 ms 12 ms 12 ms fa0-0-227.cor1.syd3.internode.on.net [150.101.197.129]
4 12 ms 13 ms 14 ms 13 ms 12 ms gi0-3.bdr1.syd1.agile.on.net [150.101.199.237]
5 166 ms 168 ms 166 ms 166 ms 166 ms POS2-1.IG2.LAX9.ALTER.NET [208.222.8.225]
6 161 ms 163 ms 162 ms 162 ms 162 ms 0.so-7-0-0.XR2.LAX9.ALTER.NET [152.63.116.86]
7 162 ms 162 ms 163 ms 162 ms 163 ms 0.so-2-0-0.XL2.LAX9.ALTER.NET [152.63.115.166]
8 167 ms 168 ms 168 ms 168 ms 166 ms POS7-0.BR3.LAX9.ALTER.NET [152.63.115.5]
9 182 ms 163 ms 164 ms 164 ms 163 ms [204.255.173.14]
10 164 ms 164 ms 164 ms 164 ms 164 ms dcr1-ae3.LosAngeles.savvis.net [208.172.44.9]
11 267 ms 266 ms 267 ms 267 ms 269 ms acr1.Denver.savvis.net [208.172.162.61]
12 286 ms 282 ms 282 ms 281 ms 283 ms [208.172.163.134]
13 250 ms 250 ms 251 ms 250 ms 250 ms [216.91.187.39]

Ping statistics for 216.91.187.39
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 250ms, Maximum = 251ms, Average = 250ms

eagl · « **Reply #10 on:** January 07, 2005, 06:35:38 PM »

C:\WINDOWS>tracert 216.91.187.39

Tracing route to 216.91.187.39 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 8 ms 10.132.23.254
3 8 ms 7 ms 10 ms cmbg-t2cam1-a-ge94.inet.ntl.com [80.1.202.21]
4 7 ms 7 ms 7 ms cmbg-t2core-a-ge-wan61.inet.ntl.com [80.1.201.25]
5 11 ms 13 ms 34 ms pop-bb-a-so-200-0.inet.ntl.com [62.253.188.193]
6 9 ms 11 ms 12 ms 195.50.91.69
7 12 ms 10 ms 10 ms ge-6-0.core2.London1.Level3.net [212.187.131.46]
8 * 14 ms 19 ms bcr1-so-4-0-0.Londonlnx.savvis.net [206.24.169.29]
9 105 ms 104 ms 104 ms dcr1-loopback.Chicago.savvis.net [208.172.2.99]
10 105 ms 105 ms 104 ms acr2-so-1-0-0.Chicago.savvis.net [208.172.3.86]
11 112 ms 111 ms 110 ms 208.172.1.202
12 112 ms 111 ms 112 ms 216.91.187.39

Trace complete.

C:\WINDOWS>tracert 216.39.66.70

Tracing route to 216.39.66.70 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 7 ms 10.132.23.254
3 9 ms 8 ms 7 ms cmbg-t2cam1-b-ge94.inet.ntl.com [80.1.202.149]
4 7 ms 8 ms 9 ms cmbg-t2core-b-ge-wan61.inet.ntl.com [80.1.201.153]
5 8 ms 9 ms 10 ms nth-bb-b-so-210-0.inet.ntl.com [62.253.188.197]
6 12 ms 11 ms 11 ms sl-gw11-lon-8-0.sprintlink.net [213.206.159.245]
7 12 ms 31 ms 12 ms sl-bb20-lon-11-0.sprintlink.net [213.206.128.56]
8 12 ms 11 ms 11 ms sl-bb22-lon-14-0.sprintlink.net [213.206.128.53]
9 59 ms 25 ms 11 ms bcr1-so-5-0-0.Londonlnx.savvis.net [206.24.169.41]
10 122 ms 120 ms 120 ms bcr1.Dallas.savvis.net [208.172.130.63]
11 123 ms 121 ms 123 ms ohr1-pos-4-0.FortWorthda1.savvis.net [208.172.131.82]
12 123 ms 125 ms 121 ms csr1-ve242.FortWorthda1.savvis.net [216.39.64.58]
13 123 ms 122 ms 129 ms 216.39.67.142
14 124 ms 124 ms 125 ms 216.39.66.70

Trace complete.

SunKing · « **Reply #11 on:** January 07, 2005, 06:48:55 PM »

Target Name: N/A
IP: 216.91.187.39
Date/Time: 1/7/2005 4:46:24 PM to 1/7/2005 4:47:54 PM

1 18 ms 28 ms 18 ms 32 ms 36 ms 13 ms 26 ms [10.184.24.1]
2 21 ms 31 ms 23 ms 15 ms 15 ms 32 ms 17 ms [12.244.16.145]
3 36 ms 13 ms 22 ms 27 ms 39 ms 12 ms 23 ms [12.244.69.153]
4 23 ms 49 ms 23 ms 74 ms 25 ms 57 ms 34 ms [12.127.32.89]
5 24 ms 38 ms 33 ms 60 ms 25 ms 47 ms 20 ms tbr1-p012301.sffca.ip.att.net [12.123.13.173]
6 16 ms 20 ms 14 ms 42 ms 33 ms 25 ms 35 ms ggr2-p300.sffca.ip.att.net [12.123.13.190]
7 33 ms 15 ms 51 ms 22 ms 12 ms 22 ms 16 ms dcr1-so-3-0-0.sanfranciscosfo.savvis.net [192.205.32.110]
8 113 ms 121 ms 137 ms 117 ms 185 ms 161 ms 143 ms acr1.Denver.savvis.net [208.172.162.61]
9 171 ms 96 ms 101 ms 126 ms 147 ms 119 ms 103 ms [208.172.163.134]
10 103 ms 114 ms 98 ms 111 ms 133 ms 99 ms 116 ms [216.91.187.39]

Ping statistics for 216.91.187.39
Packets: Sent = 7, Received = 7, Lost = 0 (0.0%)
Round Trip Times: Minimum = 98ms, Maximum = 133ms, Average = 110ms

Target Name: N/A
IP: 216.39.66.70
Date/Time: 1/7/2005 4:48:39 PM

1 20 ms [10.184.24.1]
2 25 ms [12.244.16.129]
3 12 ms [12.244.69.153]
4 44 ms [12.127.32.89]
5 20 ms tbr1-p012301.sffca.ip.att.net [12.123.13.173]
6 20 ms ggr2-p300.sffca.ip.att.net [12.123.13.190]
7 39 ms dcr1-so-3-0-0.sanfranciscosfo.savvis.net [192.205.32.110]
8 83 ms bcr1.Dallas.savvis.net [208.172.130.63]
9 66 ms ohr1-pos-4-0.FortWorthda1.savvis.net [208.172.131.82]
10 56 ms csr1-ve242.FortWorthda1.savvis.net [216.39.64.58]
11 83 ms [216.39.67.142]
12 75 ms [216.39.66.70]

Ping statistics for 216.39.66.70
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 75ms, Maximum = 75ms, Average = 75ms

WMLute · « **Reply #12 on:** January 07, 2005, 06:49:58 PM »

Host Information
1,ip68-229-216-1.ok.ok.cox.net,68.229.216.1
2, -------------- ,68.12.10.113
3,mtc3dsrc02-gew0303.rd.ok.cox.net,68.12.14.13
4,mtc3bbrc02-pos0101.rd.ok.cox.net,68.1.0.108
5,so-1-1-0-0.gar1.Dallas1.Level3.net,4.78.232.1
6,ge-11-1.core1.Dallas1.Level3.net,4.68.122.104
7,acr1-so-3-1-0.Dallas.savvis.net,209.245.240.170
8,acr1.Denver.savvis.net,208.172.162.61
9, -------------- ,208.172.163.134
10, -------------- ,216.91.187.39

Sample Information
"1/7/05 6:45:20 PM",15,N/A,19,19,22,N/A,28,*,74,67
"1/7/05 6:45:25 PM",11,9,10,16,16,N/A,21,122,61,65
"1/7/05 6:45:30 PM",11,18,10,11,16,N/A,17,121,73,63
"1/7/05 6:45:35 PM",10,9,10,196,17,N/A,15,127,67,61
"1/7/05 6:45:40 PM",10,10,19,16,23,N/A,30,122,70,66
"1/7/05 6:45:45 PM",17,10,9,11,15,16,16,122,65,68
"1/7/05 6:45:50 PM",14,9,9,13,17,N/A,16,117,67,63
"1/7/05 6:45:55 PM",12,10,12,13,16,N/A,20,116,63,63
"1/7/05 6:46:00 PM",11,9,10,11,17,N/A,17,120,62,66
"1/7/05 6:46:05 PM",21,13,13,25,16,N/A,15,120,67,66
"1/7/05 6:46:10 PM",12,12,19,11,16,N/A,15,118,64,66
"1/7/05 6:46:15 PM",13,13,11,10,14,N/A,15,*,63,62
"1/7/05 6:46:20 PM",14,12,19,16,24,N/A,16,*,63,63
"1/7/05 6:46:25 PM",23,11,9,10,14,N/A,16,118,64,66
"1/7/05 6:46:30 PM",99,14,17,11,17,N/A,21,120,71,67
"1/7/05 6:46:35 PM",11,52,13,10,15,N/A,16,114,62,62
"1/7/05 6:46:40 PM",13,8,13,152,17,N/A,50,120,64,66

Host Information
1,ip68-229-216-1.ok.ok.cox.net,68.229.216.1
2, -------------- ,68.12.10.121
3,mtc3dsrc01-gew0304.rd.ok.cox.net,68.12.14.9
4,mtc3bbrc01-pos0101.rd.ok.cox.net,68.1.0.104
5, -------------- ,68.1.0.101
6,so-1-1-0-0.gar1.Dallas1.Level3.net,4.78.232.1
7,ge-10-0.core1.Dallas1.Level3.net,4.68.122.8
8,acr1-so-3-1-0.Dallas.savvis.net,209.245.240.170
9,acr1.Denver.savvis.net,208.172.162.61
10, -------------- ,208.172.163.134
11, -------------- ,216.91.187.38

Sample Information
"1/7/05 6:47:03 PM",11,13,18,89,71,21,N/A,28,119,76,63
"1/7/05 6:47:08 PM",11,26,11,18,11,15,N/A,14,114,62,63
"1/7/05 6:47:13 PM",12,11,238,10,14,15,N/A,14,117,62,61
"1/7/05 6:47:18 PM",15,11,13,12,10,15,N/A,14,120,63,65
"1/7/05 6:47:23 PM",13,11,11,13,12,17,N/A,17,118,65,67
"1/7/05 6:47:28 PM",10,12,9,9,10,100,N/A,18,119,62,64
"1/7/05 6:47:33 PM",11,10,13,16,12,18,N/A,16,119,64,62
"1/7/05 6:47:38 PM",10,10,9,12,12,19,20,20,117,65,63
"1/7/05 6:47:43 PM",18,21,17,199,11,14,N/A,16,120,71,69
"1/7/05 6:47:48 PM",12,12,10,18,11,18,N/A,24,118,69,67
"1/7/05 6:47:53 PM",23,17,15,11,*,16,N/A,13,115,65,65
"1/7/05 6:47:58 PM",17,26,15,17,29,26,N/A,17,117,73,65
"1/7/05 6:48:03 PM",15,12,10,10,11,18,N/A,14,122,63,64
"1/7/05 6:48:08 PM",12,9,9,15,11,16,N/A,15,118,61,64
"1/7/05 6:48:13 PM",12,12,11,11,16,39,N/A,14,119,63,65
"1/7/05 6:48:18 PM",14,14,136,13,9,20,24,28,119,63,73

nsty1 · « **Reply #13 on:** January 07, 2005, 06:57:14 PM »

hope this ends up helping all of us on dial-up.

thanks Skuzzy

MrDick · « **Reply #14 on:** January 07, 2005, 07:13:09 PM »

traceroute to 216.91.187.39 (216.91.187.39), 30 hops max, 38 byte packets
1 192.168.0.1 (192.168.0.1) 0.303 ms 0.342 ms 0.204 ms
2 69.170.0.1 (69.170.0.1) 26.732 ms * 30.266 ms
3 69.161.30.177 (69.161.30.177) 15.836 ms 16.908 ms 24.699 ms
4 67.20.47.201 (67.20.47.201) 27.730 ms 19.630 ms 32.579 ms
5 24.51.101.89 (24.51.101.89) 22.582 ms 19.486 ms 27.955 ms
6 unk-426d0eb9.adelphiacom.net (66.109.14.185) 28.074 ms 24.009 ms 23.955 ms
7 so-03-00-00.c1.dca91.adelphiacom.net (66.109.0.109) 31.449 ms 39.652 ms 35.702 ms
8 unk-426d019a.adelphiacom.net (66.109.1.154) 72.437 ms 23.725 ms 32.198 ms
9 ge-6-4.car4.Washington1.Level3.net (4.78.40.1) 27.331 ms ge-6-2.car4.Washington1.Level3.net (4.78.40.9) 37.775 ms 26.155 ms
10 cpr2-gigabitethernet3-2.VirginiaEquinix.savvis.net (208.173.52.77) 35.079 ms 23.339 ms 24.304 ms
11 dcr2-so-4-2-0.Washington.savvis.net (206.24.227.66) 29.704 ms 36.123 ms 42.697 ms
12 dcr1-loopback.Chicago.savvis.net (208.172.2.99) 44.569 ms dcr2-loopback.Chicago.savvis.net (208.172.2.100) 45.636 ms dcr1-loopback.Chicago.savvis.net (208.172.2.99) 59.640 ms
13 acr2-so-0-0-0.Chicago.savvis.net (208.172.3.82) 44.998 ms 45.364 ms acr2-so-1-0-0.Chicago.savvis.net (208.172.3.86) 55.077 ms
14 208.172.1.202 (208.172.1.202) 83.984 ms 95.296 ms 92.035 ms
15 216.91.187.39 (216.91.187.39) 48.696 ms 49.276 ms 51.391 ms

traceroute to 216.39.66.70 (216.39.66.70), 30 hops max, 38 byte packets
1 192.168.0.1 (192.168.0.1) 0.372 ms 0.319 ms 0.210 ms
2 * * *
3 * * 69.161.30.177 (69.161.30.177) 25.885 ms
4 67.20.47.201 (67.20.47.201) 17.820 ms 17.216 ms 18.307 ms
5 24.51.101.89 (24.51.101.89) 31.210 ms 23.513 ms 27.834 ms
6 unk-426d0eb9.adelphiacom.net (66.109.14.185) 24.820 ms 20.755 ms 26.322 ms
7 so-03-00-00.c1.dca91.adelphiacom.net (66.109.0.109) 47.846 ms 31.327 ms 29.700 ms
8 unk-426d019a.adelphiacom.net (66.109.1.154) 22.589 ms 23.941 ms 27.964 ms
9 6-1.car4.Washington1.Level3.net (4.78.40.5) 27.454 ms ge-6-4.car4.Washington1.Level3.net (4.78.40.1) 27.925 ms 23.923 ms
10 cpr2-gigabitethernet2-2.VirginiaEquinix.savvis.net (208.173.52.73) 23.326 ms 31.376 ms 24.080 ms
11 dcr2-so-4-2-0.Washington.savvis.net (206.24.227.66) 37.455 ms 23.318 ms 35.943 ms
12 bcr1.Dallas.savvis.net (208.172.130.63) 64.680 ms 63.489 ms 55.938 ms
13 ohr1-pos-4-0.FortWorthda1.savvis.net (208.172.131.82) 60.942 ms 64.267 ms 63.193 ms
14 csr1-ve242.FortWorthda1.savvis.net (216.39.64.58) 68.275 ms 63.572 ms 60.060 ms
15 216.39.67.142 (216.39.67.142) 67.849 ms 63.351 ms 64.045 ms
16 216.39.66.70 (216.39.66.70) 73.189 ms * 59.867 ms