[AusNOG] Twitter Routing

Chris - Pike IT Services admin at pikeitservices.com.au
Mon Apr 30 00:13:10 EST 2012 

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  *  *  * 
 10  *  *  * 
 11 te-7-4.car2.SanJose2.Level3.net (4.59.4.93) 168 msec 164 msec 164 msec
 12 TWITTER-INC.car2.SanJose2.Level3.net (4.59.4.18) 172 msec 172 msec 172 msec
 13 xe-0-0-0.smf1-er2.twttr.com (199.16.159.33) 180 msec
    xe-10-0-0.smf1-er1.twttr.com (199.16.159.49) 172 msec
    xe-0-0-0.smf1-er2.twttr.com (199.16.159.33) 180 msec
 14 r-199-59-148-82.twttr.com (199.59.148.82) 172 msec 172 msec 172 msec

iiNet uses the same path as Telstra

Pacnet is going direct:

Router: syd001.pacific.net.au 
Query: trace 
Addr: 199.59.148.82

Type escape sequence to abort.
Tracing the route to r-199-59-148-82.twttr.com (199.59.148.82)

  1 vl98.switch1.syd.pacific.net.au (210.23.140.1) 0 msec
    vl96.switch2.syd.pacific.net.au (61.8.2.1) 0 msec
    vl98.switch1.syd.pacific.net.au (210.23.140.1) 0 msec
  2 Gi-1-0-1.GW1.SYD3.asianetcom.net (203.192.130.233) [AS 10026] 4 msec
    vl63.switch2.syd.pacific.net.au (125.255.94.122) 0 msec
    Gi-1-0-1.GW1.SYD3.asianetcom.net (203.192.130.233) [AS 10026] 0 msec
  3 Gi-1-0-1.GW1.SYD3.asianetcom.net (203.192.130.233) [AS 10026] 0 msec
    gi5-3-991.gw2.syd1.asianetcom.net (202.147.14.157) [AS 10026] 4 msec
    Gi-1-0-1.GW1.SYD3.asianetcom.net (203.192.130.233) [AS 10026] 0 msec
  4 gi0-0-0-981.gw2.sjc1.asianetcom.net (203.192.174.138) [AS 10026] 160 msec
    gi5-3-991.gw2.syd1.asianetcom.net (202.147.14.157) [AS 10026] 0 msec
    gi0-0-0-981.gw2.sjc1.asianetcom.net (203.192.174.138) [AS 10026] 160 msec
  5 gi0-0-0-981.gw2.sjc1.asianetcom.net (203.192.174.138) [AS 10026] 156 msec
    paix2.cr2.pao1.twttr.com (198.32.176.124) 168 msec
    gi0-0-0-981.gw2.sjc1.asianetcom.net (203.192.174.138) [AS 10026] 160 msec
  6 ae51.smf1-er1.twttr.com (199.16.159.29) 164 msec
    paix2.cr2.pao1.twttr.com (198.32.176.124) 160 msec
    ae51.smf1-er1.twttr.com (199.16.159.29) 160 msec
  7 ae51.smf1-er1.twttr.com (199.16.159.29) 164 msec
    r-199-59-148-82.twttr.com (199.59.148.82) 164 msec
    ae51.smf1-er1.twttr.com (199.16.159.29) 164 msec


Apologies for the large data dump but was hoping people with more knowledge could see why this is happening and thought it was good to include as much of my testing as possible.

Regards,

Chris Pike
Pike IT Services

Mobile: +61 458 068 854 
Web: www.pikeitservices.com.au

More information about the AusNOG mailing list