I have exchanged emails with Twitter on this and I believe they are
working on it.

We use search extensively at www.Twaller.com . The errors in search
that we are seing is as follows:

(1) HTTP status code: 403
     Message:The request is understood, but it has been refused.  An
accompanying error message will explain why.

(2)HTTP status code: 503
Message:Service Unavailable: The Twitter servers are up, but
overloaded with requests. Try again later. The search and trend
methods use this to indicate when you are being rate limited.

(3) HTTP status code: -1
Message:Read timed out

These errors are becoming more and more frequent lately.


On Sep 1, 5:41 pm, Dewald Pretorius <dpr...@gmail.com> wrote:
> Twitter team, can you please do something about the performance and
> rate limiting of the Search API.
> It is becoming completely unworkable. I have jumped through all the
> hoops, with unique User Agents, sleeping my scripts in-between API
> calls, and yet the rate limiting is just becoming more severe, and the
> performance is just becoming slower and slower.
> Please help. A lot of us are using Search to provide services, and I
> am sure it is not only my service that is hurting very much under the
> present circumstances.
> Dewald

Reply via email to