>From slicehost St. Louis: traceroute to twitter.com (168.143.161.20), 30 hops max, 60 byte packets 1 174.143.199.2 (174.143.199.2) 4.000 ms 4.000 ms 4.000 ms 2 98.129.84.172 (98.129.84.172) 4.000 ms 4.000 ms 4.000 ms 3 edge3-core7-vlan3307.dfw1.rackspace.net (174.143.123.115) 4.000 ms edge3-core7-vlan2307.dfw1.rackspace.net (174.143.123.113) 4.000 ms edge3-core7-vlan3307.dfw1.rackspace.net (174.143.123.115) 4.000 ms 4 dls-bb1-link.telia.net (213.248.88.173) 4.000 ms 4.000 ms 4.000 ms 5 verio-ic-127187-dls-bb1.c.telia.net (213.248.81.62) 4.000 ms 0.000 ms 0.000 ms 6 * * *
traceroute to twitter.com (128.121.146.100), 30 hops max, 60 byte packets 1 174.143.199.2 (174.143.199.2) 4.000 ms 4.000 ms 4.000 ms 2 98.129.84.172 (98.129.84.172) 0.000 ms 0.000 ms 0.000 ms 3 98.129.84.178 (98.129.84.178) 104.006 ms 104.006 ms 104.006 ms 4 gateway.above.net (209.133.126.41) 40.002 ms 40.002 ms 40.002 ms 5 64.125.12.218.available.above.net (64.125.12.222) 4.000 ms 4.000 ms 4.000 ms 6 po-4.r02.dllstx09.us.bb.gin.ntt.net (129.250.2.93) 4.000 ms 4.000 ms 4.000 ms 7 xe-6-2.r01.dllstx09.us.bb.gin.ntt.net (129.250.4.174) 0.000 ms 0.000 ms 0.000 ms 8 * * * traceroute to twitter.com (168.143.162.116), 30 hops max, 60 byte packets 1 174.143.199.2 (174.143.199.2) 4.001 ms 4.001 ms 4.001 ms 2 98.129.84.172 (98.129.84.172) 0.000 ms 0.000 ms 0.000 ms 3 edge3-core7-vlan2307.dfw1.rackspace.net (174.143.123.113) 0.000 ms edge3-core7-vlan3307.dfw1.rackspace.net (174.143.123.115) 0.000 ms edge3-core7-vlan2307.dfw1.rackspace.net (174.143.123.113) 0.000 ms 4 dls-bb1-link.telia.net (213.248.88.173) 36.002 ms 36.002 ms 36.002 ms 5 verio-ic-127187-dls-bb1.c.telia.net (213.248.81.62) 100.005 ms 100.005 ms 100.005 ms 6 * * * >From AT&T DSL in Alabama: traceroute to twitter.com (168.143.162.116), 64 hops max, 40 byte packets 1 192.168.1.254 (192.168.1.254) 1.940 ms 2.202 ms 1.527 ms 2 72.157.0.8 (72.157.0.8) 8.080 ms 14.058 ms 11.673 ms 3 72.157.48.18 (72.157.48.18) 9.230 ms 8.685 ms 8.809 ms 4 72.157.48.243 (72.157.48.243) 16.000 ms 20.867 ms 17.520 ms 5 axr00mgm-so-0-1-0.bellsouth.net (65.83.239.80) 16.704 ms 32.931 ms 16.616 ms 6 205.152.170.27 (205.152.170.27) 32.417 ms * 16.573 ms 7 pxr00mna-so-1-0-0.bellsouth.net (65.83.236.62) 16.955 ms 17.866 ms 17.136 ms 8 12.83.2.32 (12.83.2.32) 16.129 ms 17.257 ms 16.649 ms 9 74.175.192.66 (74.175.192.66) 24.977 ms 25.824 ms 26.831 ms 10 cr2.attga.ip.att.net (12.122.140.186) 30.323 ms 26.766 ms cr1.attga.ip.att.net (12.122.141.186) 28.070 ms 11 ggr6.attga.ip.att.net (12.122.89.241) 25.732 ms 25.075 ms 25.209 ms 12 192.205.36.158 (192.205.36.158) 26.543 ms 25.269 ms 25.468 ms 13 p64-5-0-0.r21.dllstx09.us.bb.gin.ntt.net (129.250.5.26) 44.591 ms 44.821 ms 44.474 ms 14 * * * >From datacenter in downtown Atlanta: traceroute to twitter.com (168.143.162.36), 30 hops max, 38 byte packets 1 atl-datacenter-r2.capitalinternet.com (208.32.175.2) 0.964 ms 0.526 ms 0.712 ms 2 atl-downtown-r1.capitalinternet.com (199.0.160.1) 1.309 ms 1.567 ms 1.213 ms 3 199.0.160.20 (199.0.160.20) 1.063 ms 1.326 ms 1.090 ms 4 * * * -- ivey On Sun, Oct 18, 2009 at 9:14 AM, John Kalucki <[email protected]> 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 Kalucki > http://twitter.com/jkalucki > Services, Twitter Inc. > > > > On Oct 18, 6:40 am, Dewald Pretorius <[email protected]> wrote: > > Does anyone else have problems connecting to the API at the moment > > (Sunday morning October 18)? > > > > Dewald >
