Automation check-in and rate limit changes on GitLab.com
Blog post from GitLab
GitLab.com plans to implement additional rate limits on both unauthenticated and authenticated traffic starting January 18, 2021, to enhance the platform's stability and availability. Unauthenticated requests will be restricted to 500 per minute from a single IP address, while authenticated API traffic will be capped at 2,000 requests per minute per user, and other HTTP traffic at 1,000 requests per minute per user. All traffic not specifically covered by these rules will face a general limit of 2,000 requests per minute per IP address. These restrictions primarily affect automated traffic, such as that from Git clients and custom automations, rather than individual users browsing the site. Users with automation systems are advised to handle rate-limit responses appropriately by using the Retry-After headers provided when a request is blocked with a 429 status code. GitLab aims to further refine these limits in the future, adapting them as the platform's usage evolves.
No tracked trend matches for this post yet.