we are seeing the same issue at our end. It gets better in the night (PST) and then breaks in the morning. I don't even see 403 but only 200s. Our (5 minutely) search request comes back with none, one or two results at the max though i know every minute there are about a 100 messages (as we'v been getting consistently till 10/21 or so) (No breach of limit at our end!!)
On Oct 26, 12:47 pm, briantroy <brian.cosin...@gmail.com> wrote: > Everything below ONLY PERTAINS TO THE SEARCH API: > > 1) Since late last week I've noticed a significant number of 403 > errors (403 Error from JSON: since_id too recent, poll less > frequently). These usually indicate I'm hitting a server with an > "older" view of the search index - since it thinks the ID I sent in > since_id is newer than the newest it has. These trouble me because > when I get a 200 after the 403 sometimes I get everything back to my > since_id, sometimes I don't. I appears some indexes have gaps until > they catch up. > > QUESTION: Are there any ongoing search indexing issues that you are > aware of? > > 2) Since late last week I've noticed that some search API requests > appear to get "stuck" returning an empty json result (no new tweets). > This can go on for HOURS (today one got stuck like this for 12 hours). > When I restart my process sometimes this clears up (I get the backlog) > - other times it does not (I continue to get 0 tweets in the json). > All of the requests return HTTP 200 and valid json. > > QUESTION: Are they any ongoing caching issues with the search API? > > These issues are new in the last 7 days (since about last Thursday). > My IP is whitelisted. I'm sending both a valid user agent and referrer > header. My processes are throttled by the volume of tweets the > receive. I've made no changes to my processing since late September. > > Any assistance would be appreciated. My user's are comparing what they > see from my service to search.twitter.com and telling me we are > broken. > > Regards, > > Brian Roy > justSignal
