Taylor, Yeah this was definitely NOT good. In the past, when there is a service disruption, your api group would post something on your status page and tweet about it... Instead, I'm finding out about this from my customers...
Did y'all tweet about this or present this somewhere where I could find it? Jeffrey Tweettronics.com On Sun, Mar 20, 2011 at 3:14 PM, Waldron Faulkner <waldronfaulk...@gmail.com> wrote: > Without prior notice, I can understand (circumstances), but without > any kind of subsequent announcement?? Means we have to discover issues > ourselves, verify that they're Twitter related (and not internal), > then search around for existing discussion on the topic. Saves us a > lot of time and headaches if Twitter would just announce stuff like > this. > > On Mar 18, 2:51 pm, Taylor Singletary <taylorsinglet...@twitter.com> > wrote: >> We're working to reinstate the usual limits on the Search API; due to the >> impact of the Japanese earthquake and resultant query increase against the >> Search API, some rates were adjusted to cope & better serve queries. Will >> give everyone an update with the various limits are adjusted. >> >> @episod <http://twitter.com/episod> - Taylor Singletary - Twitter Developer >> Advocate >> >> On Fri, Mar 18, 2011 at 11:39 AM, Hayes Davis <ha...@appozite.com> wrote: >> > Hi, >> >> > We're seeing this as well starting at approximately the same time as >> > described. We've backed off on searching but are seeing no reduction in the >> > sporadic limiting. It also appears that the amount of results returned on >> > successful queries is severely limited. Some queries that often have 1500 >> > tweets from the last 5 days are returning far fewer results from only the >> > last day. >> >> > Could we get an update on this? >> >> > Hayes >> >> > On Fri, Mar 18, 2011 at 10:13 AM, Eric <e...@telvetto.com> wrote: >> >> >> 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 >> >> > -- >> > 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 > > -- > 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 > -- 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
