Rate limitations announced for Projects, Groups, and Users APIs

GitLab has announced the introduction of rate limitations to its Projects, Groups, and Users APIs in response to increased user requests that have strained server performance. The rollout will be phased, beginning with temporary brownouts for the Groups and Projects APIs in February and March 2025, followed by a permanent implementation in April 2025. Similarly, the Users API will undergo brownouts in February 2025, with a permanent rollout in March 2025. To mitigate disruptions for Dedicated and Self-managed customers, the rate limits will initially be disabled by default in GitLab 18.0, allowing administrators to enable them as needed through a feature flag. This feature flag will be removed in GitLab 18.1, with predefined rate limits applied automatically unless previously altered. By GitLab 18.3, new installations will have default rate limits in place. The rate limitations, which vary per endpoint, are based on typical usage patterns and are designed to provide ample capacity for most users. Exceeding these limits will result in a "429 Too Many Requests" response, and while GitLab.com users cannot alter these limits, administrators of Self-managed instances can modify them or set them to zero to effectively disable the limitations. The change aims to maintain platform stability while accommodating the needs of researchers, developers, and integrators who frequently use these APIs.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.