This is also a problem for Twibes, hosted on App Engine. Users can't
log in due to OAuth calls failing.
On Aug 7, 7:48 am, chenyuejie wrote:
> Yes, seems they just simply restrict large requests from same IP to
> avoid DDoS attacks, for I can run my app in local, but can't do
> anything in AppEn
I submitted a ticket, here:
http://code.google.com/p/twitter-api/issues/detail?id=914
Waiting for a API Team answer.
Yes, seems they just simply restrict large requests from same IP to
avoid DDoS attacks, for I can run my app in local, but can't do
anything in AppEngine...
On Aug 7, 9:13 pm, Mario Menti wrote:
> Don't think it's related to app engine, probably just some heavy
> traffic ip addresses. Twitterf
Don't think it's related to app engine, probably just some heavy
traffic ip addresses. Twitterfeed is hosted on multiple servers and
services (none of them app engine) and all our whitelisted ips don't
work, so we've been dead for the last 24 hours.
Sent from my iPhone
On 7 Aug 2009, at 13
The situation is getting beyond a Joke now
I have paying customer who I am issuing refunds and credit notes to because
twollo is unable to access Twitter.
Did the denial of service attack come from the app engine or something?
Paul
2009/8/7 Rich
>
> I'm getting occasional bouts of being ab
I'm getting occasional bouts of being able to connect. It looks like
the server IP has been rate limited quite low (even though it's a
whitelisted IP) and even though I'm using the user's own Rate Limit
checking.
On Aug 7, 11:49 am, Rich wrote:
> Yep, I think I replied to you on Twitter, but ye
Yep, I think I replied to you on Twitter, but yes I've got the same
issue. Curl is reporting timeouts but if I switch IPs it's fine.
Looks like the w/list IPs have been blocked.
I've emailed the api@ email address but who knows!
On Aug 7, 11:47 am, David W wrote:
> Good morning,
>
> Requests f
