Chris<div>Most of the Oz to USA Traffic goes this way (as witnessed last year with the quake off japan and the issues getting to/from australia for a day or two) and will do till the southern cross cables get their full bandwidth upgrade towards the end of this year<span></span></div>
<div><br></div><div>Martin<br><br>On Sunday, 29 April 2012, Chris - Pike IT Services wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Does anyone have any ideas why most ISP's are routing to Twitter via Japan/Singapore when the server is in San Jose?<br>
<br>
The current route has packetloss on Bigpond (on both HFC and ADSL2+ in different states (NSW + QLD)<br>
<br>
I have used a few looking glasses to compare and it seems common on a few ISP's<br>
<br>
My ADSL:<br>
<br>
Tracing route to <a href="http://r-199-59-148-82.twttr.com" target="_blank">r-199-59-148-82.twttr.com</a> [199.59.148.82] with TTL of 32:<br>
<br>
<removed LAN and Bigpond internal IP's><br>
5 17ms 14ms 14ms <a href="http://bundle-ether15.ken43.sydney.telstra.net" target="_blank">bundle-ether15.ken43.sydney.telstra.net</a> [110.142.193.141]<br>
6 18ms 14ms 14ms <a href="http://bundle-ether9.ken-core4.sydney.telstra.net" target="_blank">bundle-ether9.ken-core4.sydney.telstra.net</a> [203.50.11.30]<br>
7 15ms 14ms 14ms <a href="http://bundle-ether1.pad-gw2.sydney.telstra.net" target="_blank">bundle-ether1.pad-gw2.sydney.telstra.net</a> [203.50.6.29]<br>
8 17ms 13ms 13ms 203.50.13.154<br>
9 14ms 13ms 13ms <a href="http://i-0-0-1-0.sydo-core01.bi.telstraglobal.net" target="_blank">i-0-0-1-0.sydo-core01.bi.telstraglobal.net</a> [202.84.144.250]<br>
10 132ms 133ms 132ms <a href="http://i-4-0-0.siko-core02.bx.telstraglobal.net" target="_blank">i-4-0-0.siko-core02.bx.telstraglobal.net</a> [202.84.140.138]<br>
11 135ms 135ms 135ms <a href="http://i-0-2-0-0.siko01.bi.telstraglobal.net" target="_blank">i-0-2-0-0.siko01.bi.telstraglobal.net</a> [202.84.219.46]<br>
12 * * * Request timed out.<br>
13 * * 203ms <a href="http://if-2-2.tcore2.tv2-tokyo.as6453.net" target="_blank">if-2-2.tcore2.tv2-tokyo.as6453.net</a> [180.87.180.2]<br>
14 203ms 203ms 202ms 180.87.181.6<br>
15 328ms 327ms 367ms 199.16.159.15<br>
16 332ms * 331ms <a href="http://xe-11-0-0.smf1-er2.twttr.com" target="_blank">xe-11-0-0.smf1-er2.twttr.com</a> [199.16.159.55]<br>
17 * * * Request timed out.<br>
18 * 332ms 332ms <a href="http://r-199-59-148-82.twttr.com" target="_blank">r-199-59-148-82.twttr.com</a> [199.59.148.82]<br>
<br>
Internode:<br>
<br>
Tracing the route to <a href="http://r-199-59-148-82.twttr.com" target="_blank">r-199-59-148-82.twttr.com</a> (199.59.148.82)<br>
<br>
1 <a href="http://gi1-2-950.cor1.syd6.internode.on.net" target="_blank">gi1-2-950.cor1.syd6.internode.on.net</a> (150.101.199.50) 0 msec 0 msec 0 msec<br>
2 <a href="http://gi6-0-0-134.bdr1.syd6.internode.on.net" target="_blank">gi6-0-0-134.bdr1.syd6.internode.on.net</a> (150.101.195.229) 100 msec 100 msec 100 msec<br>
3 <a href="http://te15-1-0.bdr1.adl6.internode.on.net" target="_blank">te15-1-0.bdr1.adl6.internode.on.net</a> (150.101.134.185) 100 msec 96 msec 96 msec<br>
4 <a href="http://pos0-1-0.cor1.per1.internode.on.net" target="_blank">pos0-1-0.cor1.per1.internode.on.net</a> (150.101.199.238) 52 msec * 52 msec<br>
5 <a href="http://po0-3-0.bdr1.sin1.internode.on.net" target="_blank">po0-3-0.bdr1.sin1.internode.on.net</a> (203.16.211.229) 96 msec 96 msec 100 msec<br>
6 202.79.197.113 100 msec 96 msec 100 msec<br>
7 <a href="http://xe-0-3-0.sjc2-cr2.twttr.com" target="_blank">xe-0-3-0.sjc2-cr2.twttr.com</a> (199.16.159.23) 216 msec 212 msec 220 msec<br>
8 <a href="http://xe-11-0-0.smf1-er1.twttr.com" target="_blank">xe-11-0-0.smf1-er1.twttr.com</a> (199.16.159.51) 216 msec 216 msec 216 msec<br>
9 <a href="http://r-199-59-148-82.twttr.com" target="_blank">r-199-59-148-82.twttr.com</a> (199.59.148.82) 240 msec 240 msec 240 msec<br>
<br>
AAPT seems to be using the correct path:<br>
<br>
Tracing the route to <a href="http://r-199-59-148-82.twttr.com" target="_blank">r-199-59-148-82.twttr.com</a> (199.59.148.82)<br>
<br>
1 <a href="http://fastethernet6-0-1.cor5.mel.connect.com.au" target="_blank">fastethernet6-0-1.cor5.mel.connect.com.au</a> (192.189.54.28) 0 msec 0 msec 4 msec<br>
2 <a href="http://gi1-24-205.mflindist01.nw.aapt.net.au" target="_blank">gi1-24-205.mflindist01.nw.aapt.net.au</a> (202.10.15.106) 4 msec 4 msec 4 msec<br>
3 <a href="http://te0-3-4-0.mflincore01.aapt.net.au" target="_blank">te0-3-4-0.mflincore01.aapt.net.au</a> (202.10.12.11) 12 msec 12 msec 16 msec<br>
4 <a href="http://te0-0-4-0.sglebcore01.aapt.net.au" target="_blank">te0-0-4-0.sglebcore01.aapt.net.au</a> (202.10.10.72) 16 msec 16 msec 12 msec<br>
5 <a href="http://te2-2.sglebdist01.aapt.net.au" target="_blank">te2-2.sglebdist01.aapt.net.au</a> (202.10.12.6) 12 msec 16 msec 16 msec<br>
6 <a href="http://te2-1.sglebbrdr01.aapt.net.au" target="_blank">te2-1.sglebbrdr01.aapt.net.au</a> (202.10.14.7) 16 msec 12 msec 12 msec<br>
7 <a href="http://xe7-0-0-420.sebr2.global-gateway.net.nz" target="_blank">xe7-0-0-420.sebr2.global-gateway.net.nz</a> (202.50.238.213) 12 msec 12 msec 16 msec<br>
8 * * *<br>
9 </blockquote></div><br><br>-- <br>-- <br>Martin Hepworth<br>Oxford, UK<br>