Incorrect rate limits returned for "application/rate_limit_status.json"


#1

Are the rate limits for the calls to “statuses/user_timeline.json” not being recorded properly and represented through the “application/rate_limit_status.json” calls? The rate that I see returned by the API says that I only have 15 calls within the window while the documentation shows 180 per window. I can still call “user_timeline.json” in the API up to 180 per window, but the limit and remaining is incorrect. Is anyone else seeing this or am I not checking it correctly?

"resources":{"statuses":{
"/statuses/mentions_timeline":{"limit":15,"remaining":15,"reset":1352135299},
"/statuses/user_timeline/:id":{"limit":15,"remaining":15,"reset":1352135299},
"/statuses/home_timeline/:id":{"limit":15,"remaining":15,"reset":1352135299},
"/statuses/show/:id":{"limit":180,"remaining":180,"reset":1352135299},
"/statuses/retweets/:id":{"limit":15,"remaining":15,"reset":1352135299},
"/statuses/oembed":{"limit":180,"remaining":180,"reset":1352135299}
}}

#2

We have some imbalances between what that method returns and the rates you’ll see reflected on this site and in the actual HTTP headers you get back. We’re working to not only correct the imbalance but also make the cause of the imbalance moot.


#3

Thank you. I found some more discussions regarding the issue.


#4

ﻳﻘﻮﻟﻮﺁ ﻋُﻠﻤﺂﺀ ﺍﻟﻨﻔﺲ
[ﻋﻨﺪﻣﺂ ﺗﺸﻌﺮ ﺑﺎﻟﻀﻴﻘﮧ ﻓﺠﺂﮪ ﻓﺄﻋﻠَﻢ
ٲﻥ ٲﺣﺪ ﻣُﺸﺘﺂﻕ ٳﻟﻴﮓ ]
ﻟﺬﻟﮓ ﻳﺮﺣﻢّ ٲﻣﮕﻢ ﻵ‌ ﺗﺸﺘﺂﻗﻮﻥ ﻟﻲ
ﻣﺎﻫﻲ ﺣﺂﻟﮧ ﺗﺮﻯ ﮔﻞ ﺷﻮﻱّ متﻀﺂﻳقه!!