[AusNOG] TPG/Twitter Netops?

[Matt Moor]

Hi Noggers,

Anyone from TPG or Twitter around? Just looking to scratch an itch; 
Twitter.com/80 has timed out from TPG DSL in Sydney for several days 
now. Affected range appears to be 27.32/16. Connection gets established, 
but all requests flowing down it get blackholed. Seems to be the case 
with everything in 199.59.148.0/22.

Feel free to contact me off list for further testing and/or a packet trace.

Cheers,

Matt

mattm at grayscale-2:~
$ traceroute twitter.com
traceroute: Warning: twitter.com has multiple addresses; using 199.59.148.11
traceroute to twitter.com (199.59.148.11), 64 hops max, 52 byte packets
  1  gateway.local (x.x.x.x)  2.600 ms  2.445 ms  2.581 ms
  2  10.20.21.182 (10.20.21.182)  18.687 ms  16.600 ms  19.438 ms
  3  202.7.173.37 (202.7.173.37)  17.180 ms  17.598 ms  19.666 ms
  4  syd-sot-ken-crt1-ge-5-1-0 (202.7.162.173)  23.935 ms  19.435 ms  
20.126 ms
  5  * * *
  6  * * *
  7  twitter-inc.car3.sanjose1.level3.net (4.71.113.194)  206.926 ms  
209.611 ms  264.292 ms
  8  199.16.159.37 (199.16.159.37)  207.086 ms  261.449 ms  209.694 ms
  9  twitter.com (199.59.148.11)  205.927 ms  210.433 ms  207.610 ms

mattm at grayscale-2:~
$ sudo lft www.twitter.com:80
Tracing .....****....T
TTL LFT trace to twitter.com (199.59.148.11):80/tcp
  1  gateway.local (x.x.x.x) 2.2/2.5ms
  2  10.20.21.182 17.1/15.6ms
  3  202.7.173.37 18.4/21.6ms
  4  syd-sot-ken-crt1-ge-5-1-0.tpgi.com.au (202.7.162.173) 19.1/23.0ms
**  [neglected] no reply packets received from TTLs 5 through 8
**  [4.2-3 BSD bug?] the next gateway may errantly reply with reused TTLs
  9  [target open] twitter.com (199.59.148.11):80 251.1ms