The same happened with me too...I thought I messed up something somewhere..
Ne way, hope to see better Twitter API response in the future.....
On Sat, Mar 27, 2010 at 2:17 AM, Cory <cory.imdi...@gmail.com> wrote:
> I think that was it, it's been much better now. I was worried because
> I'm in the middle of development and I thought I broke something!
> On Mar 25, 11:41 pm, John Kalucki <j...@twitter.com> wrote:
> > Do these errors coincide with this incident?
> > We threw a lot of 500s during this hour, and the 500s been slightly
> > from baseline since that issue was largely resolved. Ops is grinding down
> > that error rate as I type.
> > -John Kaluckihttp://twitter.com/jkalucki
> > Infrastructure, Twitter Inc.
> > On Thu, Mar 25, 2010 at 8:42 PM, Cory <cory.imdi...@gmail.com> wrote:
> > > I'm getting a bunch of Error 500 messages from different API calls
> > > today - is anyone else experiencing this? It isn't every call, but
> > > it's a good 1/3 of them. Sometimes a call will succeed, sometimes it
> > > will fail. The method being called doesn't seem to make a difference.
> > > I'm using oAuth, not sure if that matters.
> > > To unsubscribe from this group, send email to twitter-development-talk+
> > > unsubscribegooglegroups.com or reply to this email with the words
> > > ME" as the subject.
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
Thanks & Regards
Go Green, Use minimum natural resources!
To unsubscribe from this group, send email to
twitter-development-talk+unsubscribegooglegroups.com or reply to this email
with the words "REMOVE ME" as the subject.