We are seeing this HTML META REFRESH as well from our clients. We are a mobile application and seeing this issue more and more frequently to the point that application is not functioning properly, its hard for use to provide any specific ip data as the carriers are most likely proxying the requests from the device.
It is not limited to a specific api call either, it is a systemic issue across a wide range of calls we make. There was a ticket related to the issue in the bug tracker for search, but it has been closed and I think it should be re-opened as it is still a problem http://code.google.com/p/twitter-api/issues/detail?id=968 Any feedback would be appreciated. On Sep 6, 3:01 pm, Rich <rhyl...@gmail.com> wrote: > Yeah it's happening to me again, same as my previous email, except the > time stamp will be around 2 minutes ago > > On Sep 6, 4:05 pm, twittme_mobi <nlupa...@googlemail.com> wrote: > > > > > Hi Ryan, > > > I am getting the same error - i can found it in the logs of my app > > every day - at least 20 times. > > > 1. The IP of the machine making requests to the Twitter API. If you're > > behind NAT, please be sure to send us your *external* IP. > > > ---> > > Name: twittme.mobi > > Address: 22.214.171.124 > > > 2. The IP address of the machine you're contacting in the Twitter > > cluster. You can find this on UNIX machines via the "host" or > > "nslookup" commands, and on Windows machines via the "nslookup" > > command. > > > ---> > > Name: twitter.com > > Address: 126.96.36.199 > > > 3. The Twitter API URL (method) you're requesting and any other > > details about the request (GET vs. POST, parameters, headers, etc.). > > > ---> > > 'account/rate_limit_status.xml' > > > 4. Your host operating system, browser (including version), relevant > > cookies, and any other pertinent information about your environment. > > > ---> > > Linux, mobile browser,firefox, no cookies used. > > > 5. What kind of network connection you have and from which provider, > > and what kind of network connectivity devices you're using. > > > ---> > > devices are mostly mobile..probably using mobile connections or > > wireless. > > > Thanks! > > > On Sep 5, 2:54 pm, Alex <hyc...@gmail.com> wrote: > > > > hi Ryan, > > > any update on this issue ?