Over the past few days we have implemented rate limiting on selected services across the ASF.
As our foundation grows, so do the number of users and robots utilizing our services. In order to accommodate as many as possible with what resources we have, we have opted to implement rate-limiting to ensure that everyone can get their fair share of use of our services across the globe. The first services to have rate-limiting implemented are:
- JIRA (issues.apache.org)
- MoinMoin Wiki (wiki.apache.org)
- BugZilla (bz.apache.org)
If you are a normal user of our services:
This very likely will never affect you, and you can go about your business just like normal :) If you DO experience errors or 429 (rate limited) response codes, please do let us know.
If you are a robot or otherwise automated tool:
There are now limits in place for how much CPU time you can use, varying from service to service. If you get limited, you will receive a HTTP 429 response instead of the normal 200, and a short text blob will explain that you have crossed our resource limits and have been rate-limited. It will also explain why, and when you can expect to be unblocked again (generally within two minutes time). Scrapers, bots etc using our services should check for a 429 response code and act accordingly (or just slow down the discovery pace in general, as that benefits all of us).
A general note about the rate limiting system, now and in the future:
Rate limits are applied across IP blocks to discourage distributed abuse, thus if you have 126.96.36.199 abusing a service, 188.8.131.52 would potentially also be affected by the rate limits till they expire.
Later this year, we will be rolling out rate limits on more services, and we encourage people automating tasks to honor the 429 responses across all ASF services.
We would also like to point out that there are, as before, additional global limits in place regarding the use of our services, which can be found at: https://www.apache.org/dev/infra-ban.html