Ryan,
Are you still experiencing this? I just tried several user timelines
(w/o authentication) from my home computer (outside of twitter
network) with no errors...
-Chad
On Mon, Oct 19, 2009 at 5:51 PM, Ryan Rosario <uclamath...@gmail.com> wrote:
>
> I keep getting {"request":"/statuses/user_timeline.json?
> user_id=TheUserID&count=200","error":"This method requires
> authentication."}
> when I try to pull a user's tweets. This never used to happen. Earlier
> today I did not need to authenticate to do this.
>
> Even when I pass my username and password, I still get this error:
> curl -uMyUsername:MyPassword
> http://twitter.com/statuses/user_timeline.json?user_id=MyUserID\&count=200
> I keep getting {"request":"/statuses/user_timeline.json?
> user_id=TheUserID&count=200","error":"This method requires
> authentication."}
>
> Did something change in the past few hours???
>
> Thanks,
> Ryan
>
>
>
> On Oct 19, 1:06 pm, Arnaldo de Moraes Pereira <eggh...@gmail.com>
> wrote:
>> I'm also experiencing that today. It started to get slow several days ago,
>> but today is worse.
>>
>> Regards,
>> Arnaldo
>>
>>
>>
>>
>>
>> On Mon, Oct 19, 2009 at 5:58 PM, Dewald Pretorius <dpr...@gmail.com> wrote:
>>
>> > I've also been seeing intermittent connection refuses and really very
>> > slow performance at times today.
>>
>> > Dewald
>>
>> > On Oct 19, 3:13 pm, Michael Steuer <mste...@gmail.com> wrote:
>> > > Hi All,
>>
>> > > While it's not complete unreachability like yesterday morning, I'm again
>> > > experiencing, let's call it spotty reachability this morning... Requests
>> > > time out or are really slow to complete... Anyone else seeing this?
>>
>> > > Thanks,
>>
>> > > Michael.
>>
>> > > On 10/19/09 9:45 AM, "John Kalucki" <jkalu...@gmail.com> wrote:
>>
>> > > > Dewald, are you down, getting weird headers, or OK?
>>
>> > > > If you can't connect at all, traceroutes are best. If you get weird
>> > > > headers, a copy of the header (and your IP address) are best.
>>
>> > > > Thanks.
>>
>> > > > On Oct 18, 7:23 am, Dewald Pretorius <dpr...@gmail.com> wrote:
>> > > >> traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte
>> > > >> packets
>> > > >> 1 81.b5.85ae.static.theplanet.com (174.133.181.129) 1.351 ms
>> > 1.439
>> > > >> ms 1.464 ms
>> > > >> 2 et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5) 0.198 ms
>> > 0.229
>> > > >> ms 0.266 ms
>> > > >> 3 et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154) 0.444 ms
>> > > >> et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
>> > > >> 0.224 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154) 0.466 ms
>> > > >> 4 et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58) 0.519 ms
>> > > >> et1-2.ibr02.hstntx2.theplanet.com (70.87.253.169) 0
>> > > >> .454 ms 0.522 ms
>> > > >> 5 xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5) 167.161 ms
>> > > >> 167.045 ms 167.206 ms
>> > > >> 6 xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228) 1.185 ms
>> > > >> 1.164 ms 1.180 ms
>> > > >> 7 p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129) 6.424
>> > > >> ms 6.331 ms 6.358 ms
>> > > >> 8 po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74) 6.400 ms
>> > > >> 6.451 ms 6.489 ms
>> > > >> 9 * * *
>>
>> > > >> --------------------------
>>
>> > > >> traceroute to twitter.com (168.143.162.116), 30 hops max, 40 byte
>> > > >> packets
>> > > >> 1 81.b5.85ae.static.theplanet.com (174.133.181.129) 0.387 ms
>> > 0.432
>> > > >> ms 0.475 ms
>> > > >> 2 et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5) 0.211 ms
>> > 0.257
>> > > >> ms 0.273 ms
>> > > >> 3 et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154) 0.472 ms
>> > > >> et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
>> > > >> 0.221 ms 0.249 ms
>> > > >> 4 et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58) 0.404 ms 0.466
>> > > >> ms 0.553 ms
>> > > >> 5 xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5) 107.597 ms
>> > > >> 107.679 ms 107.742 ms
>> > > >> 6 xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228) 1.136 ms
>> > > >> 1.114 ms 1.035 ms
>> > > >> 7 p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129) 6.293
>> > > >> ms 8.708 ms 6.335 ms
>> > > >> 8 po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74) 6.433 ms
>> > > >> 6.486 ms 6.535 ms
>> > > >> 9 * * *
>>
>> > > >> -----------------------------
>>
>> > > >> traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
>> > > >> packets
>> > > >> 1 81.b5.85ae.static.theplanet.com (174.133.181.129) 0.429 ms
>> > 0.515
>> > > >> ms 0.567 ms
>> > > >> 2 et2-5.ibr02.hstntx1.theplanet.com (207.218.245.5) 8.956 ms
>> > 8.986
>> > > >> ms 9.024 ms
>> > > >> 3 et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58) 0.439 ms 0.493
>> > > >> ms 0.546 ms
>> > > >> 4 xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5) 1.156 ms
>> > > >> 1.206 ms 1.254 ms
>> > > >> 5 xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228) 1.114 ms
>> > > >> 1.113 ms 1.131 ms
>> > > >> 6 p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129) 6.280
>> > > >> ms 6.256 ms 6.717 ms
>> > > >> 7 po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74) 6.377 ms
>> > > >> 6.444 ms 6.499 ms
>> > > >> 8 * * *
>>
>> > > >> On Oct 18, 11: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
>>
>> --
>> Arnaldo M Pereira
>
