Let's see who has the best tracert to xenforo.com.
Here's mine:
http://pastebin.ca/1918489
Why does my connection go through weird routes?
Here's mine:
http://pastebin.ca/1918489
Why does my connection go through weird routes?
Looks pretty normal, hop out of your router, hop to the ISP's infrastructure, bounces through a few of its internal nodes to get close to the planet datacenter, where XenForo's server is housed, then bounces through their internal infrastructure, and finally to XenForo's server.
killercreation.co.uk is a hosting company in the UK, I wouldn't be too surprised if they are routing their servers through their own network before handing it off to above.net's backbone to connect to USA.Whoops, my other one (for another website) is wierd. It goes through killercreation.co.uk, before going onto above.net.
root@xfprod:~# traceroute xenforo.com
traceroute to xenforo.com (174.123.247.179), 30 hops max, 40 byte packets
1 xenforo.com (174.123.247.179) 0.096 ms 0.020 ms 0.019 ms
root@xfprod:~#
Tracing route to xenforo.com [174.123.247.179]
over a maximum of 30 hops:
1 4 ms 4 ms 5 ms 192.168.1.1
2 * * * Request timed out. <-- LOL router timed out XD
3 11 ms 9 ms 9 ms ge-9-1-ur01.martin.mn.minn.comcast.net [68.85.164.97]
4 10 ms 10 ms 9 ms te-2-3-ur02.martin.mn.minn.comcast.net [68.86.232.162]
5 12 ms 10 ms 11 ms te-2-1-ur01.minnetonka.mn.minn.comcast.net [68.86.232.38]
6 30 ms 22 ms 23 ms te-0-4-0-5-cr01.chicago.il.ibone.comcast.net [68.86.91.185]
7 49 ms 43 ms 42 ms pos-2-13-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.85.58]
8 58 ms 55 ms 60 ms pos-1-13-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.253]
9 65 ms 55 ms 56 ms pos-0-1-0-0-pe01.1950stemmons.tx.ibone.comcast.net [68.86.86.94] <-- WTF is this? o_O
10 74 ms 55 ms 56 ms theplanet-cr01.dallas.tx.ibone.comcast.net [75.149.228.2]
11 59 ms 67 ms 61 ms et1-1.ibr01.hstntx2.theplanet.com [70.87.253.50]
12 76 ms 62 ms 70 ms et3-3.ibr01.hstntx1.theplanet.com [70.87.253.153]
13 69 ms 59 ms 61 ms te2-1.dsr01.hstntx1.223.218.207.in-addr.arpa [207.218.223.34]
14 60 ms 60 ms 59 ms po2.car03.hstntx1.theplanet.com [207.218.245.10]
15 63 ms 59 ms 59 ms b3.f7.7bae.static.theplanet.com [174.123.247.179]
killercreation.co.uk is a hosting company in the UK, I wouldn't be too surprised if they are routing their servers through their own network before handing it off to above.net's backbone to connect to USA.
Also, this is not my, but hypothetically speaking the dev will win:
Code:root@xfprod:~# traceroute xenforo.com traceroute to xenforo.com (174.123.247.179), 30 hops max, 40 byte packets 1 xenforo.com (174.123.247.179) 0.096 ms 0.020 ms 0.019 ms root@xfprod:~#
1 <1 ms <1 ms <1 ms 192.168.1.254
2 4 ms 4 ms 4 ms 118.23.67.40
3 4 ms 4 ms 5 ms 118.23.67.62
4 7 ms 7 ms 7 ms 221.184.12.181
5 5 ms 5 ms 5 ms 122.1.246.193
6 5 ms 4 ms 5 ms 210.254.188.233
7 5 ms 5 ms 5 ms 60.37.27.69
8 6 ms 5 ms 6 ms 210.254.187.190
9 6 ms 6 ms 6 ms ae-5.r21.tokyjp01.jp.bb.gin.ntt.net [129.250.11.53]
10 145 ms 120 ms 119 ms as-0.r21.lsanca03.us.bb.gin.ntt.net [129.250.3.145]
11 159 ms 159 ms 160 ms xe-6-4.r03.hstntx01.us.bb.gin.ntt.net [129.250.3.122]
12 161 ms 160 ms 160 ms xe-6-3.r03.hstntx01.us.ce.gin.ntt.net [128.241.1.6]
13 159 ms 159 ms 159 ms et3-3.ibr02.hstntx1.theplanet.com [70.87.253.57]
14 159 ms 159 ms 161 ms te2-6.dsr01.hstntx1.245.218.207.in-addr.arpa [207.218.245.38]
15 164 ms 165 ms 165 ms po2.car03.hstntx1.theplanet.com [207.218.245.10]
16 164 ms 159 ms 160 ms b3.f7.7bae.static.theplanet.com [174.123.247.179]
1 <1 ms <1 ms <1 ms 192-168-1-1.tpgi.com.au [192.168.1.1]
2 58 ms 14 ms 91 ms 10.20.21.180
3 55 ms 13 ms 109 ms syd4-56k-009.tpgi.com.au [202.7.173.9]
4 41 ms 14 ms 111 ms syd-pow-cla-crt1-po-1.tpgi.com.au [202.7.162.141
]
5 190 ms 242 ms 159 ms 66.162.129.177
6 273 ms 253 ms 170 ms sjc1-pr1-xe-0-0-0-0.us.twtelecom.net [66.192.251
.170]
7 248 ms 258 ms 174 ms 68.86.87.17
8 282 ms 257 ms 242 ms 68.86.87.46
9 236 ms 242 ms 238 ms 68.86.87.38
10 216 ms 231 ms 328 ms pos-0-3-0-0-pe01.1950stemmons.tx.ibone.comcast.n
et [68.86.86.154]
11 265 ms 250 ms 234 ms theplanet-cr01.dallas.tx.ibone.comcast.net [75.1
49.228.2]
12 307 ms 279 ms 249 ms et1-1.ibr01.hstntx2.theplanet.com [70.87.253.50]
13 233 ms 301 ms 250 ms et3-3.ibr01.hstntx1.theplanet.com [70.87.253.153
]
14 308 ms 226 ms 246 ms te2-2.dsr01.hstntx1.223.218.207.in-addr.arpa [20
7.218.223.30]
15 284 ms 244 ms 271 ms po1.car03.hstntx1.theplanet.com [207.218.223.10]
16 254 ms 264 ms 233 ms b3.f7.7bae.static.theplanet.com [174.123.247.179
]
The Planet in Dallas Texas is the server?
I would not have guessed that.
The hop across the ocean always kills me.
Too bad Seattle to China doesn't get the same performance...Makes sense since Tokyo to Los Angeles takes 41 ms in fiber. And that's assuming a single line connection that runs directly from the heart of Tokyo in a straight line to LA.
Only a 4 ms difference...Too bad Seattle to China doesn't get the same performance...
I thought Andy was in Canada?Only a 4 ms difference...
http://www.wolframalpha.com/input/?i=seattle,+washington+to+china*
*Again, this is a straight line and does not account for the actual location of undersea cables, the amount of wiring in routers/switches/machines, etc. and the inherent processing latency when passing through machines.
Offtopic - Do you live in China? What's it like there?
Tracing route to xenforo.com [174.123.247.179]over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 23 ms 25 ms 186.32.166.1
3 14 ms 9 ms 21 ms amnet-a23.racsa.co.cr [65.182.11.23]
4 35 ms 39 ms 13 ms amnet-a69.racsa.co.cr [65.182.30.69]
5 31 ms 64 ms 25 ms 186.32.0.73
6 * * * Request timed out.
7 72 ms 76 ms 62 ms so-4-2-1.edge3.Miami1.Level3.net [4.59.82.25]
8 85 ms 89 ms 89 ms ae-31-51.ebr1.Miami1.Level3.net [4.69.138.94]
9 97 ms 116 ms 134 ms ae-2-2.ebr1.Dallas1.Level3.net [4.69.140.133]
10 115 ms 150 ms 114 ms ae-1-60.edge4.Dallas3.Level3.net [4.69.145.13]
11 100 ms 115 ms 98 ms THE-PLANET.edge4.Dallas3.Level3.net [4.59.32.30]
12 143 ms 149 ms 136 ms et1-1.ibr02.hstntx1.theplanet.com [70.87.253.54]
13 117 ms 96 ms 103 ms te2-6.dsr01.hstntx1.245.218.207.in-addr.arpa [207.218.245.38]
14 123 ms 106 ms 104 ms po2.car03.hstntx1.theplanet.com [207.218.245.10]
15 149 ms 133 ms 113 ms b3.f7.7bae.static.theplanet.com [174.123.247.179]
Trace complete.
Makes sense since Tokyo to Los Angeles takes 41 ms in fiber. And that's assuming a single line connection that runs directly from the heart of Tokyo in a straight line to LA.
It really depends on ISP's routing... I remember the major drop in Japan is owned by either NTT DOCOMO or whatever its called... so if you're using any other ISP, it'll also do some fun routings to get into NTT DOCOMO's network, and then out through the drop.For whatever reason, I used to get routed through Osaka to California/Seattle even though I live dead smack in the middle of central Tokyo. (Osaka is ~550km from Tokyo)
We use essential cookies to make this site work, and optional cookies to enhance your experience.