Page 1 of 1
Trace a route for me!
Posted: Wed May 24, 2006 7:46 am
by Tricord
We have several uplinks in my hosting company. One of them, which ends up in Cogent and Level3, is very expensive while almost no traffic goes over it. We're looking into dropping that link.
Before that, I'd like to know how it will affect the routes to our network, especially to people far away (asia, americas, etc..)
So, the idea is, collect a few traceroutes, then turn off the link for 12 hours and collect traceroutes again, then compare.
Could everyone post a traceroute to tricord.be here, along with your location (country, state) and provider? In a few days, I'll turn off the link and will ask everyone to trace again.
Thanks!
Posted: Wed May 24, 2006 7:51 am
by Unix
Code: Select all
Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 66.98.244.1 gphou-66-98-244-1.ev1.net
2 0 0 0 66.98.241.16 gphou-66-98-241-16.ev1.net
3 0 0 0 66.98.240.11 gphou-66-98-240-11.ev1.net
4 0 1 1 38.112.25.157 f0-4.na21.b015619-0.iah01.atlas.cogentco.com
5 44 4 1 66.28.64.61 g0-1.core01.iah01.atlas.cogentco.com
6 26 26 29 154.54.2.14 p13-0.core01.ord01.atlas.cogentco.com
7 47 47 47 66.28.4.109 p14-0.core01.bos01.atlas.cogentco.com
8 124 124 124 130.117.0.45 p3-0.core01.lon02.atlas.cogentco.com
9 128 128 129 130.117.1.157 p4-0.core01.bru01.atlas.cogentco.com
10 129 129 130 130.117.19.254 belgiannetworksolutions.demarc.cogentco.com
11 120 120 120 83.96.193.170 rtr.intx.stone-is.stone-is.com
12 113 113 113 87.238.162.13 be2.1-eurohost.com
Trace complete
Offut AFB, Nebrasksa
Cox Omaha
Posted: Wed May 24, 2006 8:17 am
by CDN_Merlin
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms intcon.kottlumber.com [192.168.200.1]
2 15 ms 21 ms 12 ms access-3-f2-0-461.storm.ca [209.87.237.129]
3 28 ms 52 ms 31 ms core-g0-0-1000.storm.ca [209.87.239.129]
4 75 ms 63 ms 42 ms A-p2-0-0-S1.gw1.mtl1.rogerstelecom.net [207.107.
188.229]
5 50 ms 51 ms 55 ms g8-0-3-S1.bb1.mtl1.rogerstelecom.net [207.107.25
4.1]
6 91 ms 62 ms 50 ms p2-2-S1.bb1.tor1.rogerstelecom.net [209.5.21.49]
7 57 ms 54 ms 74 ms p13-1.core01.yyz01.atlas.cogentco.com [154.54.10
.113]
8 79 ms 57 ms 63 ms v3490.mpd01.yyz02.atlas.cogentco.com [154.54.3.2
30]
9 93 ms 55 ms 50 ms v3493-mpd01.yyz01.atlas.cogentco.com [154.54.5.8
5]
10 53 ms 78 ms 57 ms g2-0-0-3490-core01.yyz01.atlas.cogentco.com [154
.54.5.73]
11 60 ms 97 ms 61 ms p6-0.core01.bos01.atlas.cogentco.com [66.28.4.21
7]
12 138 ms 135 ms 120 ms p10-0.core01.lon02.atlas.cogentco.com [130.117.0
.186]
13 152 ms 136 ms 167 ms p4-0.core01.bru01.atlas.cogentco.com [130.117.1.
157]
14 147 ms 146 ms 144 ms BelgianNetworkSolutions.demarc.cogentco.com [130
.117.19.254]
15 169 ms 147 ms 140 ms as-stone-is.demarc.bru1.benesol.be [85.158.208.2
34]
16 156 ms 134 ms 139 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Ottawa, Canada
ISP: Storm Internet.
Posted: Wed May 24, 2006 8:37 am
by Testiculese
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 13 ms 19 ms 10 ms 192.168.1.1
3 4 ms 7 ms 4 ms 192.168.1.254
4 9 ms 9 ms 14 ms 207.106.213.98
5 14 ms 19 ms 13 ms 169.130.98.17
6 24 ms 19 ms 19 ms 169.130.98.67
7 20 ms 28 ms 27 ms g1-16.mpd01.iad01.atlas.cogentco.com [154.54.11.213]
8 34 ms 32 ms 29 ms v3495-mpd01.dca01.atlas.cogentco.com [154.54.5.61]
9 20 ms 24 ms 24 ms g1-0-0.core02.dac01.atlas.cogentco.com [154.54.5.49]
10 110 ms 111 ms 104 ms p6-0.core01.par01.atlas.cogentco.com [66.28.4.205]
11 114 ms 112 ms 120 ms p13-0.core01.lon02.atlas.cogentco.com [130.117.1.121]
12 113 ms 117 ms 114 ms ten-6-0.core02.lon01.atlas.cogentco.com [130.117.1.161]
13 111 ms 118 ms 121 ms p4-0.core01.bru01.atlas.cogentco.com [130.117.1.157]
14 100 ms 99 ms 104 ms BelgianNetworkSolutions.demarc.cogentco.com [130.117.19.254]
15 123 ms 121 ms 113 ms rtr.intx.stone-is.stone-is.com [83.96.193.170]
16 118 ms 122 ms 112 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Pennsylvania, USA
I don't know my provider here at work...
Posted: Wed May 24, 2006 8:56 am
by Vindicator
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 12-215-166-52.client.mchsi.com [12.215.166.52]
2 25 ms 12 ms 11 ms 10.26.128.1
3 21 ms 25 ms 25 ms 12-215-19-97.client.mchsi.com [12.215.19.97]
4 32 ms 39 ms 39 ms 12-215-4-86.client.mchsi.com [12.215.4.86]
5 36 ms 34 ms 46 ms 12.123.193.158
6 34 ms 48 ms 34 ms tbr1-p013602.cgcil.ip.att.net [12.122.11.37]
7 35 ms 34 ms 34 ms ggr2-p310.cgcil.ip.att.net [12.123.6.65]
8 59 ms 54 ms 59 ms so-9-1.car4.Chicago1.Level3.net [4.68.127.165]
9 54 ms 55 ms 52 ms ae-1-55.bbr1.Chicago1.Level3.net [4.68.101.129]
10 126 ms 129 ms 125 ms so-1-0-0.mp2.Brussels1.Level3.net [212.187.128.2
]
11 131 ms 125 ms 133 ms ge-11-2.ipcolo1.Brussels1.Level3.net [212.3.239.
117]
12 128 ms 147 ms 131 ms ge-0-1-0-503.br0.bru1.benesol.be [212.3.234.94]
13 127 ms 126 ms 128 ms as-stone-is.demarc.bru1.benesol.be [85.158.208.2
34]
14 214 ms 131 ms 127 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
southern Illinois, USA
ISP: Mediacom
Posted: Wed May 24, 2006 9:46 am
by Sir Sam II
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms [hidden]
2 11 ms 11 ms 11 ms [hidden]
3 11 ms 11 ms 11 ms [hidden]
4 24 ms 24 ms 23 ms ftldfl-01-so-0-0-1.xspedius.net [206.222.122.221]
5 24 ms 25 ms 25 ms xspedius.fldfl.ip.att.net [12.119.94.17]
6 54 ms 54 ms 54 ms 12.123.33.62
7 53 ms 53 ms 53 ms tbr1-cl1474.attga.ip.att.net [12.122.12.121]
8 52 ms 53 ms 53 ms tbr2-cl17.wswdc.ip.att.net [12.122.10.69]
9 54 ms 55 ms 55 ms gar1-p390.ascva.ip.att.net [12.123.8.53]
10 60 ms 61 ms 61 ms 12.117.208.26
11 127 ms 128 ms 126 ms so-2-1-0.lon11.ip.tiscali.net [213.200.80.57]
12 124 ms 127 ms 126 ms realroot-lon-gw.ip.tiscali.net [213.200.77.226]
13 132 ms * 131 ms ge0-2-0-44.br0.bebru1.realroute.net [193.27.64.177]
14 132 ms 133 ms 132 ms stone-is-gw.bru1.realroute.net [83.143.241.86]
15 130 ms 131 ms 134 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Florida, USA
ISP: Xspedius
Posted: Wed May 24, 2006 12:19 pm
by fliptw
192.168.0.1
d142-59-32-1.abhsia.telus.net
CLGRAB01DR00.bb.telus.com
clgrab31br01.bb.telus.com
toroonxngr00.bb.telus.com
Cogent.toroonxngr00.bb.telus.com
v3490.mpd01.yyz02.atlas.cogentco.com
v3493-mpd01.yyz01.atlas.cogentco.com
g2-0-0-3490-core01.yyz01.atlas.cogentco.com
p6-0.core01.bos01.atlas.cogentco.com
p3-0.core01.lon02.atlas.cogentco.com
p4-0.core01.bru01.atlas.cogentco.com
BelgianNetworkSolutions.demarc.cogentco.com
as-stone-is.demarc.bru1.benesol.be
be2.1-eurohost.com
Calgary, AB
TELUS
Posted: Wed May 24, 2006 12:41 pm
by Grendel
Code: Select all
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 4 ms 4 ms 4 ms [local]
2 4 ms 4 ms 4 ms [local]
3 25 ms 34 ms 23 ms tuk-edge-03.inet.qwest.net [67.134.196.189]
4 13 ms 13 ms 13 ms tuk-core-01.inet.qwest.net [205.171.11.49]
5 58 ms 31 ms 31 ms svx-core-01.inet.qwest.net [67.14.1.62]
6 52 ms 31 ms 31 ms sjp-brdr-01.inet.qwest.net [205.171.214.134]
7 32 ms 32 ms 32 ms so-5-2-0.sjc10.ip.tiscali.net [213.200.66.233]
8 180 ms * 169 ms so-2-1-0.lon11.ip.tiscali.net [213.200.80.57]
9 185 ms 169 ms 169 ms realroot-lon-gw.ip.tiscali.net [213.200.77.226]
10 171 ms 172 ms 171 ms ge0-2-0-44.br0.bebru1.realroute.net [193.27.64.177]
11 171 ms 172 ms 190 ms stone-is-gw.bru1.realroute.net [83.143.241.86]
12 170 ms 170 ms 170 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
USA, Oregon
QWest (?) T1
Posted: Wed May 24, 2006 2:38 pm
by CDN_Merlin
Home ISP: Rogers Cable
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 * * * Request timed out.
2 6 ms 7 ms 7 ms gw03.rchrd.phub.net.cable.rogers.com [66.185.90.
113]
3 7 ms 6 ms 6 ms gw01.rchrd.phub.net.cable.rogers.com [66.185.83.
181]
4 17 ms 10 ms 6 ms gw01.flfrd.phub.net.cable.rogers.com [66.185.82.
129]
5 14 ms 11 ms 11 ms gw02.mtnk.phub.net.cable.rogers.com [66.185.82.1
25]
6 * * * Request timed out.
7 69 ms 205 ms 224 ms v3490.mpd01.yyz02.atlas.cogentco.com [154.54.3.2
30]
8 24 ms 25 ms 25 ms v3492-mpd01.yyz01.atlas.cogentco.com [154.54.5.8
1]
9 27 ms 24 ms 25 ms g3-0-0-3491-core01.yyz01.atlas.cogentco.com [154
.54.5.77]
10 34 ms 34 ms 33 ms p6-0.core01.bos01.atlas.cogentco.com [66.28.4.21
7]
11 106 ms 106 ms 109 ms p10-0.core01.lon02.atlas.cogentco.com [130.117.0
.186]
12 111 ms 111 ms 111 ms p4-0.core01.bru01.atlas.cogentco.com [130.117.1.
157]
13 113 ms 114 ms 113 ms BelgianNetworkSolutions.demarc.cogentco.com [130
.117.19.254]
14 125 ms 114 ms 115 ms as-stone-is.demarc.bru1.benesol.be [85.158.208.2
34]
15 113 ms 112 ms 112 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Posted: Wed May 24, 2006 3:13 pm
by Krom
Northern Wisconsin USA
Code: Select all
Tracing route to tricord.be [87.238.162.13] over a maximum of 30 hops:
1 22 ms 65 ms 24 ms lcrsalcobr5.lcrswicoro1.centurytel.net [69.29.181.15]
2 17 ms 17 ms 18 ms j2-rt.lax.centurytel.net [207.230.192.159]
3 32 ms 31 ms 28 ms 4.79.68.9
4 28 ms 30 ms 30 ms ae-1-55.bbr1.Chicago1.Level3.net [4.68.101.129]
5 120 ms 123 ms 127 ms so-3-0-0.mp1.brussels1.level3.net [212.187.128.6]
6 121 ms 121 ms 130 ms ge-11-1.ipcolo1.brussels1.level3.net [212.3.239.83]
7 131 ms 121 ms 121 ms ge-0-1-0-503.br0.bru1.benesol.be [212.3.234.94]
8 122 ms 122 ms 121 ms as-stone-is.demarc.bru1.benesol.be [85.158.208.234]
9 120 ms 121 ms 119 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Posted: Wed May 24, 2006 3:57 pm
by Testiculese
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms be2.1-eurohost.com [87.238.162.13]
2 8 ms 8 ms 8 ms 10.7.43.1
3 11 ms 8 ms 8 ms P12-1.LCR-01.PHLAPA.verizon-gni.net [130.81.33.74]
4 15 ms 14 ms 14 ms so-6-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.81.17.129]
5 14 ms 14 ms 14 ms 130.81.15.138
6 17 ms 15 ms 14 ms p15-0.core02.jfk02.atlas.cogentco.com [66.28.4.14]
7 92 ms 92 ms 92 ms p5-0.core01.ams03.atlas.cogentco.com [130.117.1.169]
8 101 ms 95 ms 95 ms p5-0.core01.bru01.atlas.cogentco.com [130.117.1.134]
9 97 ms 101 ms 96 ms BelgianNetworkSolutions.demarc.cogentco.com [130.117.19.254]
10 96 ms 99 ms 97 ms as-stone-is.demarc.bru1.benesol.be [85.158.208.234]
11 104 ms 97 ms 96 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
PA< USA again, Verizon DSL
Posted: Wed May 24, 2006 3:59 pm
by Tricord
A few American traces go via RealRoute (that's another of our uplinks). Interesting. I'll be curious to see how the current Level3 and Cogent routes will change when I drop that link. I'll do that tomorrow. Thanks to everyone so far!
Posted: Wed May 24, 2006 6:30 pm
by Top Gun
I'd be happy to help, but how exactly would I go about getting traceroute data?
Re:
Posted: Wed May 24, 2006 6:45 pm
by Krom
Top Gun wrote:I'd be happy to help, but how exactly would I go about getting traceroute data?
In Windows XP: Start > Run > "CMD" (without quotes): "tracert tricord.be" (without quotes). Highlight the output > copy/paste.
Posted: Wed May 24, 2006 7:21 pm
by DCrazy
Got this when I did it from rerun.cs.loyola.edu (Debian GNU/Linux):
traceroute: unknown host tricord.be
Strange. Windows from my machine gave me this:
tracert wrote:
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms not.giving.my.ip
2 <1 ms <1 ms <1 ms 10.10.33.4
3 <1 ms <1 ms <1 ms 10.10.32.2
4 1 ms 1 ms 1 ms 10.10.15.3
5 <1 ms <1 ms <1 ms nok-par-1.loyola.edu [144.126.253.2]
6 1 ms 1 ms 1 ms 144.126.253.250
7 15 ms 17 ms 19 ms A7-0-0-1106.EDGE-RTR1.BALT2.verizon-gni.net [151.196.227.17]
8 9 ms 6 ms 4 ms so-0-1-1-0.CORE-RTR1.BALT2.verizon-gni.net [130.81.10.117]
9 5 ms 7 ms 8 ms so-5-1-0-0.BB-RTR1.RES.verizon-gni.net [130.81.18.120]
10 9 ms 4 ms 5 ms so-6-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81.10.90]
11 4 ms 4 ms 5 ms 130.81.15.74
12 6 ms 6 ms 7 ms p10-0.core01.iad01.atlas.cogentco.com [154.54.2.29]
13 4 ms 4 ms 6 ms v3492-mpd01.iad01.atlas.cogentco.com [154.54.3.222]
14 6 ms 8 ms 9 ms v3495-mpd01.dca01.atlas.cogentco.com [154.54.5.61]
15 6 ms 6 ms 5 ms g1-0-0.core02.dca01.atlas.cogentco.com [154.54.5.49]
16 92 ms 90 ms 92 ms p6-0.core01.par01.atlas.cogentco.com [66.28.4.205]
17 92 ms 92 ms 92 ms p13-0.core01.lon02.atlas.cogentco.com [130.117.1.121]
18 90 ms 94 ms 90 ms g2-0-0.core02.lon01.atlas.cogentco.com [130.117.1.209]
19 96 ms 95 ms 94 ms p4-0.core01.bru01.atlas.cogentco.com [130.117.1.157]
20 99 ms 98 ms 95 ms BelgianNetworkSolutions.demarc.cogentco.com [130.117.19.254]
21 96 ms 95 ms 96 ms as-stone-is.demarc.bru1.benesol.be [85.158.208.234]
22 96 ms 96 ms 107 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Both are going through Verizon.
Posted: Wed May 24, 2006 9:24 pm
by dissent
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 169 ms 160 ms 160 ms nas44.Chicago1.Level3.net [209.247.5.14]
2 141 ms 160 ms 149 ms unknown.Level3.net [63.215.0.2]
3 146 ms 160 ms 149 ms ae-1-55.bbr1.Chicago1.Level3.net [4.68.101.129]
4 253 ms 235 ms 235 ms so-1-0-0.mp2.Brussels1.Level3.net [212.187.128.2]
5 242 ms 257 ms 246 ms ge-11-1.ipcolo1.Brussels1.Level3.net [212.3.239.83]
6 242 ms 257 ms 246 ms ge-0-1-0-503.br0.bru1.benesol.be [212.3.234.94]
7 253 ms 257 ms 246 ms as-stone-is.demarc.bru1.benesol.be [85.158.208.234]
8 242 ms 246 ms 257 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
USA, Illinois, MSN
Posted: Wed May 24, 2006 10:02 pm
by Mobius
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms a001-m001.dune.clear.net.nz [203.167.236.129]
2 1 ms 1 ms 1 ms 10.73.0.9
3 6 ms 6 ms 6 ms 10.69.32.249
4 13 ms 13 ms 13 ms 10.65.0.249
5 73 ms 15 ms 15 ms 10.65.0.10
6 14 ms 14 ms 14 ms ge-0-1-0-915.icore1.acld.telstraclear.net [203.98.42.9]
7 14 ms 14 ms 14 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
8 15 ms 15 ms 15 ms ge-0-2-0-914.xcore2.acld.telstraclear.net [203.98.42.18]
9 153 ms 144 ms 148 ms so.jb.wils.telstraclear.net [203.98.42.66]
10 144 ms 151 ms 143 ms 65.244.201.221
11 143 ms 145 ms 144 ms GigabitEthernet3-0.GW1.LAX1.ALTER.NET [157.130.245.21]
12 142 ms 141 ms 143 ms 0.so-0-0-0.XL1.LAX1.ALTER.NET [152.63.112.218]
13 155 ms 149 ms 157 ms 0.so-1-1-0.XL1.LAX7.ALTER.NET [152.63.57.78]
14 149 ms 150 ms 149 ms 0.so-6-0-0.BR1.LAX7.ALTER.NET [152.63.112.41]
15 157 ms 150 ms 150 ms so-2-0-0.gar1.LosAngeles1.Level3.net [209.0.227.37]
16 143 ms 147 ms 143 ms ae-2-52.bbr2.LosAngeles1.Level3.net [4.68.102.33]
17 297 ms 293 ms 299 ms so-1-0-0.mp2.Brussels1.Level3.net [212.187.128.2]
18 290 ms 289 ms 292 ms ge-11-1.ipcolo1.Brussels1.Level3.net [212.3.239.83]
19 290 ms 288 ms 284 ms ge-0-1-0-503.br0.bru1.benesol.be [212.3.234.94]
20 286 ms 288 ms 285 ms as-stone-is.demarc.bru1.benesol.be [85.158.208.234]
21 287 ms 288 ms 285 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
SUCK ON MY FIRST HOP PING TIMES FOOS! 
P.S. It's 10Mb/s up and 10Mb/s down fibre optic to the door!!
Posted: Wed May 24, 2006 11:51 pm
by Testiculese
Highlight the output? Geez, all the newfangled tech these days..to think I was piping the output for no reason..
Posted: Thu May 25, 2006 5:05 am
by Krom
Yeah, I used 'tracert tricord.be > trace.txt' / 'notepad trace.txt' when I did it, only thing is I had to edit in the line breaks.
Posted: Thu May 25, 2006 11:11 am
by Tricord
Mobi, don't wet your pants
I've turned down the link now, could everyone re-trace the route to
tricord.be? In particular those who already posted a trace above.
Thanks!
Posted: Thu May 25, 2006 11:30 am
by CDN_Merlin
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms intcon.kottlumber.com [192.168.200.1]
2 14 ms 12 ms 10 ms access-3-f2-0-461.storm.ca [209.87.237.129]
3 45 ms 25 ms 36 ms core-g0-0-1000.storm.ca [209.87.239.129]
4 48 ms 58 ms 44 ms A-p2-0-0-S1.gw1.mtl1.rogerstelecom.net [207.107.
188.229]
5 47 ms 28 ms 53 ms g8-0-4-S1.bb1.mtl1.rogerstelecom.net [207.107.25
4.65]
6 49 ms 66 ms 76 ms sl-gw1-pen-13-3.sprintlink.net [144.228.166.13]
7 111 ms 49 ms 46 ms sl-bb20-pen-5-0.sprintlink.net [144.232.5.1]
8 58 ms 59 ms 43 ms sl-bb23-pen-14-0.sprintlink.net [144.232.16.26]
9 62 ms 52 ms 76 ms sl-bb26-nyc-13-0-0.sprintlink.net [144.232.20.12
2]
10 44 ms 54 ms 50 ms sl-bb25-nyc-8-0.sprintlink.net [144.232.13.189]
11 39 ms 58 ms 53 ms sl-bb24-nyc-10-0.sprintlink.net [144.232.13.181]
12 91 ms 68 ms 65 ms sl-gw29-nyc-0-0.sprintlink.net [144.232.13.16]
13 68 ms 78 ms 129 ms sl-tisca1-2-0.sprintlink.net [160.81.43.102]
14 * * 203 ms so-2-1-0.lon11.ip.tiscali.net [213.200.80.57]
15 128 ms 141 ms 143 ms realroot-lon-gw.ip.tiscali.net [213.200.77.226]
16 144 ms 139 ms 141 ms ge0-2-0-44.br0.bebru1.realroute.net [193.27.64.1
77]
17 147 ms 140 ms 129 ms stone-is-gw.bru1.realroute.net [83.143.241.86]
18 131 ms 150 ms 139 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
ISP: Storm Internet (work)
Will do home later tonight
Posted: Thu May 25, 2006 12:11 pm
by Krom
Code: Select all
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 21 ms 29 ms 19 ms wey-eth-gw.dial.redwing.net [66.44.156.1]
2 26 ms 39 ms 29 ms hag-wey-gw.direct.redwing.net [66.44.145.1]
3 37 ms 29 ms 39 ms hag-bdr-hag-gw.direct.redwing.net [66.44.145.25]
4 279 ms 458 ms 290 ms air-hag-gw.direct.airstreamcomm.net [64.33.129.137]
5 32 ms 39 ms 49 ms air-edith-1.airstreamcomm.net [64.33.146.177]
6 24 ms 49 ms 39 ms 12.126.248.61
7 74 ms 79 ms 69 ms tbr1-p012701.cgcil.ip.att.net [12.122.2.222]
8 64 ms 69 ms 109 ms tbr1-cl14.n54ny.ip.att.net [12.122.10.1]
9 73 ms 69 ms 79 ms gar1-p300.nylny.ip.att.net [12.123.3.97]
10 78 ms 69 ms 69 ms ge-2-1-2.nyc33.ip.tiscali.net [12.118.94.46]
11 143 ms 139 ms * so-2-1-0.lon11.ip.tiscali.net [213.200.80.57]
12 149 ms 139 ms 139 ms realroot-lon-gw.ip.tiscali.net [213.200.77.226]
13 135 ms 139 ms 149 ms ge0-2-0-44.br0.bebru1.realroute.net [193.27.64.177]
14 * 131 ms 149 ms stone-is-gw.bru1.realroute.net [83.143.241.86]
15 134 ms 139 ms 149 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Note, this is at home instead of work so the routes are different even though there is only a 20 mile difference in location, I go through the twin cities then to chicago vs work that goes directly to chicago.
Posted: Thu May 25, 2006 2:38 pm
by CDN_Merlin
Home ISP: Rogers Cable
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 * * * Request timed out.
2 7 ms 5 ms 5 ms gw03.rchrd.phub.net.cable.rogers.com [66.185.90.113]
3 7 ms 7 ms 5 ms gw01.rchrd.phub.net.cable.rogers.com [66.185.83.181]
4 11 ms 11 ms 11 ms gw01.slnt.phub.net.cable.rogers.com [66.185.82.134]
5 27 ms 27 ms 30 ms igw01.vaash.phub.net.cable.rogers.com [66.185.80.190]
6 54 ms 53 ms 55 ms if-15-0.core2.AEQ-Ashburn.teleglobe.net [209.58.27.33]
7 53 ms 54 ms 53 ms so-5-0-1-0.was10.ip.tiscali.net [213.200.66.93]
8 101 ms 108 ms 101 ms so-2-1-0.lon11.ip.tiscali.net [213.200.80.57]
9 125 ms 125 ms 127 ms realroot-lon-gw.ip.tiscali.net [213.200.77.226]
10 125 ms 126 ms 126 ms ge0-2-0-44.br0.bebru1.realroute.net [193.27.64.177]
11 125 ms 125 ms 125 ms stone-is-gw.bru1.realroute.net [83.143.241.86]
12 125 ms 127 ms 126 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Posted: Thu May 25, 2006 2:54 pm
by Grendel
Code: Select all
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 4 ms 4 ms 4 ms [local]
2 18 ms 4 ms 4 ms [local]
3 14 ms 12 ms 13 ms tuk-edge-03.inet.qwest.net [67.134.196.189]
4 19 ms 13 ms 24 ms tuk-core-01.inet.qwest.net [205.171.11.49]
5 32 ms 42 ms 31 ms svx-core-01.inet.qwest.net [67.14.1.62]
6 42 ms 31 ms 46 ms sjp-brdr-01.inet.qwest.net [205.171.214.134]
7 31 ms 159 ms 63 ms so-5-2-0.sjc10.ip.tiscali.net [213.200.66.233]
8 * 171 ms 172 ms so-2-1-0.lon11.ip.tiscali.net [213.200.80.57]
9 169 ms 169 ms 183 ms realroot-lon-gw.ip.tiscali.net [213.200.77.226]
10 171 ms 171 ms 171 ms ge0-2-0-44.br0.bebru1.realroute.net [193.27.64.177]
11 172 ms 182 ms 171 ms stone-is-gw.bru1.realroute.net [83.143.241.86]
12 170 ms 170 ms 170 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Posted: Thu May 25, 2006 4:07 pm
by Isaac
Austin Texas.. yea haw
isaac's comp wrote:
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 4 ms 4 ms 2 ms cpe-70-113-13-37.austin.res.rr.com [70.113.13.37
]
2 12 ms 10 ms 12 ms 10.64.160.1
3 11 ms 13 ms 12 ms gig2-4.austtxa-rtr2.austin.rr.com [24.27.12.89]
4 14 ms 12 ms 10 ms srp0-0.austtxrdc-rtr2.austin.rr.com [24.27.12.34
]
5 11 ms 11 ms 11 ms pos10-3.austtxrdc-rtr4.texas.rr.com [66.68.1.106
]
6 20 ms 21 ms 21 ms son0-1-1.hstqtxl3-rtr1.texas.rr.com [24.93.33.22
1]
7 20 ms 23 ms 22 ms tenge-2-4.car1.Houston1.Level3.net [4.79.88.25]
8 19 ms 21 ms 18 ms ge-2-0-0.mp1.Houston1.Level3.net [4.68.97.241]
9 67 ms 80 ms 70 ms ae-2-0.bbr1.Washington1.Level3.net [4.68.128.201
]
10 70 ms 93 ms 67 ms ae-14-53.car4.Washington1.Level3.net [4.68.121.8
1]
11 67 ms 72 ms 66 ms 4.68.111.94
12 137 ms 137 ms 134 ms so-2-1-0.lon11.ip.tiscali.net [213.200.80.57]
13 138 ms 137 ms 162 ms realroot-lon-gw.ip.tiscali.net [213.200.77.226]
14 152 ms 155 ms 157 ms ge0-2-0-44.br0.bebru1.realroute.net [193.27.64.1
77]
15 152 ms 152 ms 153 ms stone-is-gw.bru1.realroute.net [83.143.241.86]
16 151 ms * 154 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Posted: Thu May 25, 2006 4:11 pm
by Testiculese
Did you switch, Tri? I'll re-run mine whenever.
Posted: Thu May 25, 2006 5:58 pm
by Top Gun
From little ol' Delaware in the US, via my school's network. I can get another when I go home tomorrow:
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms chp-7k-e-1-2-sub3.nss.udel.edu [128.175.67.1]
2 <1 ms <1 ms 1 ms chp-br1-ge-1-1-0.nss.udel.edu [128.175.111.4]
3 2 ms 2 ms 2 ms g1.ba21.b003003-1.phl01.atlas.cogentco.com [38.112.7.61]
4 2 ms 2 ms 2 ms g9-0.core01.phl01.atlas.cogentco.com [38.112.34.141]
5 4 ms 4 ms 4 ms p5-0.core02.jfk02.atlas.cogentco.com [66.28.4.1]
6 82 ms 82 ms 82 ms p5-0.core01.ams03.atlas.cogentco.com [130.117.1.169]
7 82 ms 82 ms * t3-1.mpd01.ams03.atlas.cogentco.com [130.117.0.34]
8 82 ms 83 ms 83 ms ge-1-2-0-0.cr1.rb2f.amsix-nkf.proserve.nl [195.69.144.214]
9 92 ms 93 ms 93 ms ge-0-0-0-1.cr1.gs.nl.proserve.nl [80.84.254.13]
10 93 ms 93 ms 92 ms ge-0-0-0-1.cr1.tc2.nl.proserve.nl [80.84.254.9]
11 92 ms 92 ms 92 ms fe-0-0-2.cr2.lcl.be.proserve.nl [83.96.193.26]
12 92 ms 93 ms 93 ms rtr.intx.stone-is.stone-is.com [83.96.193.170]
13 87 ms 87 ms 87 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Posted: Thu May 25, 2006 7:49 pm
by Vindicator
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 12.206.241.233
2 15 ms 35 ms 14 ms 10.3.254.1
3 21 ms 21 ms 20 ms 12-215-14-17.client.mchsi.com [12.215.14.17]
4 36 ms 36 ms 33 ms 12-215-4-90.client.mchsi.com [12.215.4.90]
5 55 ms 52 ms 59 ms tbr1-p012301.cgcil.ip.att.net [12.123.6.9]
6 54 ms 50 ms 66 ms tbr1-cl14.n54ny.ip.att.net [12.122.10.1]
7 53 ms 60 ms 51 ms ar2-p30.n54ny.ip.att.net [12.123.0.65]
8 52 ms 55 ms 55 ms ge-2-1-6.nyc33.ip.tiscali.net [12.118.94.38]
9 119 ms 127 ms 124 ms so-2-1-0.lon11.ip.tiscali.net [213.200.80.57]
10 128 ms 127 ms 120 ms realroot-lon-gw.ip.tiscali.net [213.200.77.226]
11 127 ms 146 ms 125 ms ge0-2-0-44.br0.bebru1.realroute.net [193.27.64.1
77]
12 128 ms 128 ms 123 ms stone-is-gw.bru1.realroute.net [83.143.241.86]
13 125 ms 135 ms 128 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Same location/ISP as above.
Posted: Thu May 25, 2006 7:52 pm
by Duper
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms dslrouter [192.168.1.1]
2 3 ms 3 ms 3 ms dslrouter [192.168.1.1]
3 26 ms 26 ms 28 ms L100.DSL-04.PTLDOR.verizon-gni.net [71.111.176.1]
4 48 ms 61 ms 25 ms P1-3.LCR-02.PTLDOR.verizon-gni.net [130.81.34.90]
5 51 ms 50 ms 50 ms so-6-0-0-0.PEER-RTR1.SJC80.verizon-gni.net [130.81.17.133]
6 51 ms 51 ms 51 ms so-6-1-0-0.gar2.SanJose1.Level3.net [4.79.54.1]
7 50 ms 51 ms 53 ms ae-24-54.car4.SanJose1.Level3.net [4.68.123.110]
8 108 ms 107 ms 123 ms ge-4-0-0.sjc10.ip.tiscali.net [4.68.111.166]
9 226 ms 188 ms 187 ms so-2-1-0.lon11.ip.tiscali.net [213.200.80.57]
10 193 ms 193 ms 193 ms realroot-lon-gw.ip.tiscali.net [213.200.77.226]
11 194 ms 264 ms 223 ms ge0-2-0-44.br0.bebru1.realroute.net [193.27.64.177]
12 193 ms 239 ms 193 ms stone-is-gw.bru1.realroute.net [83.143.241.86]
13 192 ms 229 ms 192 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Portland Oregon, USA Verzion DSL
Posted: Thu May 25, 2006 8:05 pm
by Mobius
Tracing route to tricord.be [87.238.162.13]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms a001-m001.dune.clear.net.nz [203.167.236.129]
2 1 ms <1 ms <1 ms 10.73.0.9
3 6 ms 6 ms 6 ms 10.69.32.249
4 13 ms 13 ms 13 ms 10.65.0.249
5 15 ms 16 ms 15 ms 10.65.0.10
6 14 ms 14 ms 14 ms ge-0-1-0-915.icore1.acld.telstraclear.net [203.98.42.9]
7 * 14 ms 14 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
8 15 ms 15 ms 15 ms ge0-0-0.nzsx-core1.akl.telstraclear.net [203.98.4.3]
9 139 ms 140 ms 140 ms unknown.net.reach.com [202.84.219.101]
10 172 ms 171 ms 171 ms i-3-0.dal-core01.net.reach.com [202.84.249.106]
11 197 ms 196 ms 196 ms i-10-0.chi-core01.net.reach.com [202.84.143.69]
12 197 ms 197 ms 197 ms ibx-chi.ip.tiscali.net [206.223.119.19]
13 288 ms 286 ms 286 ms so-2-1-0.lon11.ip.tiscali.net [213.200.80.57]
14 285 ms 285 ms 285 ms realroot-lon-gw.ip.tiscali.net [213.200.77.226]
15 300 ms 300 ms 301 ms ge0-2-0-44.br0.bebru1.realroute.net [193.27.64.177]
16 307 ms 307 ms 307 ms stone-is-gw.bru1.realroute.net [83.143.241.86]
17 302 ms 301 ms 304 ms be2.1-eurohost.com [87.238.162.13]
Trace complete.
Posted: Fri May 26, 2006 3:55 am
by Tricord
That was interesting.
It seems that everything ends up via Tiscali in transit to RealRoute in London. From there it goes straight to us.
That means people accessing overseas through Level3, have to switch to Tiscali first, go to London, switch to RealRoute, then go to Brussels and enter our own network.
Dropping the link had no real effect on smokeping (ping statistics from our network throughout the world) to local ISP's, nor networks overseas (US, NZ, AUS, etc..). Pings did go up from 15ms to 90ms to scandinavia (but who cares?
)
We currently have three uplinks. Two full transit, one peering in three exchanges. Very redundant. We can lose any of these three and all traffic will be rerouted through the other two without any noticeable difference. However, if we drop a full transit link, we have redundant peering but no longer redundant transit. This means that if the peering link goes down, all traffic can follow the transit link, but not the other way around. If RealRoute goes down, about 20-25% of our traffic will be dropped because it can't be delivered by peering.
So, dilemma. Do I keep paying for a transit link that serves only as a backup for about 20% of our traffic in case the other transit link goes down? Knowing that the backup link costs about the same as the other two together?
Argh, why are these connections so expensive?
