We're also seeing 400s on different boxes across different IP addresses with different queries (so it does not appear to be server or query specific). These began on all boxes at 2 a.m. UTC. We've backed off on both number and rate of queries with no effect. We've also noticed an increase in sporadic fail whales via browser based search (atom and html) from personal accounts, although we haven't attempted to quantify it.
On Mar 18, 7:40 am, zaver <zave...@hotmail.com> wrote: > Hello, > > After the latest performance issues with the search api i have been > seeing a lot of 420 response codes.From yesterday until now i only get > 420 responses on the every search i make. In particular, i search for > about 100 keywords simultaneously every 6 mins. Why is this happening? > Was there any change on the Search API limit? > > Any help is greatly appreciated. > > Thanks, > Zaver -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
