We've confirmed the issue... fixing it is taking more time than anticipated. – Kevin Montrose
Color me happy.
The throttle is now applied to api.stackoverflow.com so we have an undefined max requests per minute with an undefined burst allowance before 503 errors begin to be thrown.
It appears that the threshold has been raised significantly and interestingly it seems that the api.stackoverflow.com threshold is still higher than the other endpoints.
see What is the throttle interval or threshold? for current test results
Hey guys, we seem to be getting some love on the 503 throttle issue but need some help with some repro reports.
I have noticed just one other dev getting reports of 503 here, but trust me, if you haven't run into them yet it is just a matter of time and you will find yourself very frustrated and hacking in compensation code with something that does not resemble a smile on your face.
This is a critical issue and your help is needed to verify and prioritize this problem.
You don't need to download anything, simply paste this into a file and view it in a browser while monitoring via Fiddler or Charles.
An answer with your observations would be welcome but all that is really needed is a comment of repro/no-repro.
- Expected results by api.stackoverflow.com alt text http://img594.imageshack.us/img594/1862/200stackoverflow.png
- 503 throttling on api.stackapps.com alt text http://img101.imageshack.us/img101/8947/503stackapps.png
- 503 throttling on api.stackauth.com alt text http://img641.imageshack.us/img641/8687/503stackauth.png