I'm guessing that if you do a request that counts against your rate limit (rate_limit_status requests do not) from just 1 of your IPs, and then request the rate limit status on each of them, you will see that the one that made the non-rate_limit_status request now has 19,999, while the other two still have 20,000.
My understanding is that each white-listed IP gets 20k authenticated GET requests per hour per authenticating account and an extra 20k non-authenticated GET requests per hour, whether the IPS are listed for the same account or not. As I understand it, across your 3 IPs, you should get 60k authenticated requests per hour per authenticating account, and an extra 60k non-authenticated GET requests per hour. Let us know what you find, as I've never heard about rate limit issues from someone with more than one white-listed IP. Hope this helps. Jim Renkel -----Original Message----- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of TwitterNoob Sent: Saturday, September 26, 2009 05:02 To: Twitter Development Talk Subject: [twitter-dev] Twitter Rate Limit for IPs Hi, I recently got whitelisted for 3 IPs which is listed under one single account. Does this mean that each IP will have a rate limit of 20,000 requests/hour for the REST API so collectively all 3 IPs should give 60,000 requests/hour for the REST API or does this mean that all 3 whitelisted IPs under one single account will have 20,000 requests/ hour for the REST API collectively? I used this command "curl -u user:password http://twitter.com/account/rate_limit_status.xml"; to get the rate limit status for each of the 3 servers with those IPs but it seems like all 3 IPs have only 20,000 requests/hour collectively. I'm a little confused about this because initially I thought that each IP whitelisted should give me an additional 20,000 requests/hour but maybe I'm wrong so I would greatly appreciate it if someone can answer this or show me a better way of querying for the rate limit status of each individual server. Many thanks to the benevolent stranger(s) for answering this...
