So somewhere before you reach twitter.com, traceroute must get blocked. I just did a traceroute from my home (Verizon DSL) where I can access Twitter perfectly, and traceroute still doesn't complete:
michael-steuers-computer:~ msteuer$ traceroute twitter.com traceroute to twitter.com (128.121.146.100), 64 hops max, 52 byte packets 1 192.168.1.1 (192.168.1.1) 0.611 ms 0.311 ms 0.197 ms 2 10.35.27.1 (10.35.27.1) 21.969 ms 22.321 ms 21.706 ms 3 p0-3.lsanca-lcr-03.verizon-gni.net (130.81.34.248) 21.712 ms 21.478 ms 21.507 ms 4 so-6-1-2-0.lax01-bb-rtr1.verizon-gni.net (130.81.28.225) 21.958 ms 21.830 ms 22.000 ms 5 0.so-6-3-0.xt1.lax9.alter.net (152.63.10.153) 23.446 ms 23.323 ms 23.743 ms 6 0.so-5-1-0.xt1.lax7.alter.net (152.63.116.253) 48.239 ms 24.029 ms 23.228 ms 7 pos6-0.br2.lax7.alter.net (152.63.112.145) 23.472 ms 23.722 ms 23.467 ms 8 p64-6-1-3.r20.lsanca03.us.bb.gin.ntt.net (129.250.8.205) 25.215 ms 24.968 ms 24.735 ms 9 as-0.r21.snjsca04.us.bb.gin.ntt.net (129.250.4.96) 35.987 ms 36.747 ms 35.958 ms 10 po-2.r04.snjsca04.us.bb.gin.ntt.net (129.250.6.6) 36.516 ms 37.034 ms * 11 * * * So I don't know how helpful all these traceroute results are going to be for Twitter, given that both from networks that can connect, and those that can't the traceroutes fail in the "ntt.net" or "telia.net" networks On Oct 18, 7:33 am, TCI <ticoconid...@gmail.com> wrote: > Tracert disabled from host - fail! > But I assume that if we can't reach you, you should not be able to > reach us either? My server's IP is 174.120.0.108 (The Planet) > > On Oct 18, 8:14 am, John Kalucki <jkalu...@gmail.com> wrote: > > > > > I don't see any operational issues from here, but I'm not an > > operational guy. At first glance the system looks fine, and the > > operational team isn't in response mode. This is puzzling. > > > Seems like a connectivity issue upstream from twitter. At lest a few > > developers: please send a traceroute to this list. Also, if you aren't > > timing out, but rather are getting an HTTP error, send the response > > headers. After say 4 or 5 responses, they'll probably have enough info > > to triage this. > > > -John Kaluckihttp://twitter.com/jkalucki > > Services, Twitter Inc. > > > On Oct 18, 6:40 am, Dewald Pretorius <dpr...@gmail.com> wrote: > > > > Does anyone else have problems connecting to the API at the moment > > > (Sunday morning October 18)? > > > > Dewald
