[AusNOG] Twitter Routing

[Martin Hepworth]

Chris
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

Martin

On Sunday, 29 April 2012, Chris - Pike IT Services wrote:

> Does anyone have any ideas why most ISP's are routing to Twitter via
> Japan/Singapore when the server is in San Jose?
>
> The current route has packetloss on Bigpond (on both HFC and ADSL2+ in
> different states (NSW + QLD)
>
> I have used a few looking glasses to compare and it seems common on a few
> ISP's
>
> My ADSL:
>
> Tracing route to r-199-59-148-82.twttr.com [199.59.148.82] with TTL of 32:
>
> <removed LAN and Bigpond internal IP's>
> 5 17ms 14ms 14ms bundle-ether15.ken43.sydney.telstra.net [110.142.193.141]
> 6 18ms 14ms 14ms bundle-ether9.ken-core4.sydney.telstra.net [203.50.11.30]
> 7 15ms 14ms 14ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29]
> 8 17ms 13ms 13ms 203.50.13.154
> 9 14ms 13ms 13ms i-0-0-1-0.sydo-core01.bi.telstraglobal.net[202.84.144.250]
> 10 132ms 133ms 132ms i-4-0-0.siko-core02.bx.telstraglobal.net[202.84.140.138]
> 11 135ms 135ms 135ms i-0-2-0-0.siko01.bi.telstraglobal.net [202.84.219.46]
> 12 * * * Request timed out.
> 13 * * 203ms if-2-2.tcore2.tv2-tokyo.as6453.net [180.87.180.2]
> 14 203ms 203ms 202ms 180.87.181.6
> 15 328ms 327ms 367ms 199.16.159.15
> 16 332ms * 331ms xe-11-0-0.smf1-er2.twttr.com [199.16.159.55]
> 17 * * * Request timed out.
> 18 * 332ms 332ms r-199-59-148-82.twttr.com [199.59.148.82]
>
> Internode:
>
> Tracing the route to r-199-59-148-82.twttr.com (199.59.148.82)
>
>  1 gi1-2-950.cor1.syd6.internode.on.net (150.101.199.50) 0 msec 0 msec 0
> msec
>  2 gi6-0-0-134.bdr1.syd6.internode.on.net (150.101.195.229) 100 msec 100
> msec 100 msec
>  3 te15-1-0.bdr1.adl6.internode.on.net (150.101.134.185) 100 msec 96 msec
> 96 msec
>  4 pos0-1-0.cor1.per1.internode.on.net (150.101.199.238) 52 msec *  52
> msec
>  5 po0-3-0.bdr1.sin1.internode.on.net (203.16.211.229) 96 msec 96 msec
> 100 msec
>  6 202.79.197.113 100 msec 96 msec 100 msec
>  7 xe-0-3-0.sjc2-cr2.twttr.com (199.16.159.23) 216 msec 212 msec 220 msec
>  8 xe-11-0-0.smf1-er1.twttr.com (199.16.159.51) 216 msec 216 msec 216 msec
>  9 r-199-59-148-82.twttr.com (199.59.148.82) 240 msec 240 msec 240 msec
>
> AAPT seems to be using the correct path:
>
> Tracing the route to r-199-59-148-82.twttr.com (199.59.148.82)
>
>  1 fastethernet6-0-1.cor5.mel.connect.com.au (192.189.54.28) 0 msec 0
> msec 4 msec
>  2 gi1-24-205.mflindist01.nw.aapt.net.au (202.10.15.106) 4 msec 4 msec 4
> msec
>  3 te0-3-4-0.mflincore01.aapt.net.au (202.10.12.11) 12 msec 12 msec 16
> msec
>  4 te0-0-4-0.sglebcore01.aapt.net.au (202.10.10.72) 16 msec 16 msec 12
> msec
>  5 te2-2.sglebdist01.aapt.net.au (202.10.12.6) 12 msec 16 msec 16 msec
>  6 te2-1.sglebbrdr01.aapt.net.au (202.10.14.7) 16 msec 12 msec 12 msec
>  7 xe7-0-0-420.sebr2.global-gateway.net.nz (202.50.238.213) 12 msec 12
> msec 16 msec
>  8  *  *  *
>  9



-- 
-- 
Martin Hepworth
Oxford, UK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20120429/cda5759f/attachment.html>