You are most likely right. Given the shared pool of IPs, they could get blacklisted at any time:
https://dev.twitter.com/docs/rate-limiting This is going to become a progressively more serious problem as time goes on (GAE becomes more successful, useful public services add rate limiting). Star this issue: http://code.google.com/p/googleappengine/issues/detail?id=6644 For now it's probably best to make calls to external services through a proxy with a dedicated IP address you control. I'd love to hear suggestions for "cheapest possible solution" - $11/mo for a 256MB rackspacecloud instance is as good as I can come up with. Jeff On Fri, Aug 24, 2012 at 10:26 AM, JH <[email protected]> wrote: > As of yesterday my app, ticker-app, can no longer connect to Twitter's API. > It has worked fine for over a year. As of yesterday any urlfetch call to > twitter.com times out with DeadlineExceeded. However, using other app ID's > I have they can still urlfetch to twitter. I have to assume it has > something to do with which data center ticker-app is hosted in? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/eMHHC7P3PtUJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
