We're talking to our operations team about it, who in turn is talking to our hosting provider. It seems that some aggressive IP filtering may have been catching some web-based third-party Twitter applications, as well as data centers used by mobile providers.
On Thu, Aug 6, 2009 at 12:52, Jonathan<[email protected]> wrote: > > I would also appreciate an answer to this question. My calls to the > Search API are failing because of circular redirection, and > > curl http://twitter.com > > returns nothing at all from my production server, which seems like a > sign that its IP has been blocked. > > My app works fine from my dev box. > > -jonathan > > On Aug 6, 1:35 pm, Dewald Pretorius <[email protected]> wrote: >> Chad, >> >> I know it's a little late in asking, but should we switch off cron >> jobs that make a lot of API calls while this DoS is going on, or while >> you are recovering from it? >> >> I don't want my IP addresses to be blocked because they are making a >> lot of calls! I've seen in the past that Ops lay down carpet bombing >> with cluster munitions when under attack. >> >> Will it help you to recover if we switched off the cron jobs? >> >> Right now most of my connections are just being refused. >> >> Do you guys at least check against the list of white listed IP >> addresses before you block an IP address in times like these? >> >> Will there be innocent bystanders caught in the cross-fire again? >> >> This is the kind of info that we developers need... >> >> Dewald > -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
