GoKawiilGitLab.com to tie API rate limits to subscription tier starting October 2026
GitLab is overhauling how it throttles requests on GitLab.com, moving from flat limits to caps tied to each subscription plan, applied per user and per top-level group. Free accounts and unauthenticated traffic hit the new limits on October 19, 2026, with two brownout previews on October 7 and 14; Premium and Ultimate users follow in January 2027. Unauthenticated requests, including automation hitting the API without credentials, will be capped at 60 requests per hour per IP regardless of account tier.
GoKawiil's interpretation of the reporting above, not reported fact.
As automation and AI-agent workloads increasingly hammer GitLab.com's API, tier-based throttling gives GitLab a lever to protect performance while nudging heavy users toward paid plans and proper authentication. Teams relying on scripts or bots without credentials could see sudden failures once the cap kicks in, making the preview windows a critical, if narrow, testing opportunity.
- Rate limits will scale with subscription tier instead of being uniform across GitLab.com.
- Free-tier and unauthenticated traffic changes first on October 19, 2026; Premium/Ultimate follow in January 2027.
- Unauthenticated requests are capped at 60/hour per IP even on paid accounts, so automation must authenticate to avoid disruption.
Source: about.gitlab.com, 2026-09-17
Published there as: “Rate limits on GitLab.com are changing”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.