Thanks Ryan, but unfortunately that does not help me. It does not tell my users that most, if not all calls to the API are being rejected with connection refused. In other words, from my perspective, the API is completely down / inoperative / unresponsive.
My issue has nothing to do with OAuth. Dewald On Aug 16, 7:41 pm, Ryan Sarver <rsar...@twitter.com> wrote: > Everyone, > > Please see the updated post on status.twitter.com > -http://status.twitter.com/post/164410057/trouble-with-oauth-and-api-c.... > > We are continuing to assess the issue and will report back when we know more. > > Thanks for your patience, Ryan > > On Sun, Aug 16, 2009 at 2:32 PM, Hwee-Boon Yar<hweeb...@gmail.com> wrote: > > > Can you confirm if OAuth access is the only known issue? I feel silly > > repeating the same question over and over again: "Even / > > rate_limit_status calls are timing out on my server. I have no API > > access *at all*". > > > -- > > Hwee-Boon > > > On Aug 17, 5:21 am, Chad Etzel <jazzyc...@gmail.com> wrote: > >> We've asked the keeper-o-the-blog to post something to that effect. > >> Hopefully it will appear soon. > >> -Chad > > >> On Sun, Aug 16, 2009 at 4:42 PM, Dewald Pretorius<dpr...@gmail.com> wrote: > > >> > Can you at the very least PLEASE publish something on > >> > status.twitter.com about the API being down and/or very unresponsive > >> > at times, so that I have a link where I can refer my users, so that > >> > they can see I am not shitting them? > > >> > Dewald