GitLab.com rate limits | GitLab Docs
/ GitLab.com rate limits Tier : Free, Premium, Ultimate Offering : GitLab.com The following rate limits apply to GitLab.com. GitLab Self-Managed and GitLab Dedicated instances have their own limits, which the operator of the instance controls. If you do not use GitLab.com, see rate limits or authenticated user rate limits instead. Rate limits by plan The limits in this section are proposed and are not in effect yet. The limits in current rate limits apply today and continue to apply after these changes take effect.
GitLab announces specific dates in advance. Before a limit is enforced, GitLab runs scheduled brownout windows, when the new limit is briefly active so you can see how the new limit affects your workloads. Rate limits are becoming tier-aware. Instead of a single number for everyone, limits reflect your plan and apply for each user and for each top-level group. Authenticated requests receive your plan’s full allowance.
Anonymous requests receive a much lower allowance, in line with similar platforms. Each plan has two limits for authenticated traffic, and the sustained limit takes precedence: A sustained limit, measured each hour. Use this number to plan your usage. A burst limit, measured each minute. GitLab sets this default so a short spike does not consume an entire hourly allowance at once. For steady work, you reach the sustained limit first.
Sending requests at the burst limit for a full hour would exceed the sustained limit on every plan. Treat the burst limit as a ceiling for short spikes, not a rate you can maintain. Requests at the burst limit reach the sustained limit in approximately 50 minutes in Free, 12 minutes in Premium, and 12.5 minutes in Ultimate. These limits apply to API requests, web requests, and authenticated Git over HTTPS requests. Each Git clone, fetch, or push counts as one request, and so does each Git LFS transfer.
Some unauthenticated requests do not count against the unauthenticated limit of 60 requests each hour from an IP address: Git over HTTPS requests Requests to the home page ( / ) Sign-in requests, including SAML SSO and sign-in with a third-party provider such as Google or GitHub Sign-up requests, including username availability checks and identity verification Requests to reset a password, confirm an email address, or unlock an account Free trial sign-up requests Container image requests to the dependency proxy OAuth 2.0 authorization, access token, device authorization, and dynamic client registration requests OpenID Connect discovery requests, such as the ones cloud providers make to verify CI/CD ID tokens OAuth discovery requests that MCP clients make before they sign in Terraform service discovery requests, made before installing modules from the Terraform module registry Feature flag polling from Unleash clients Requests that register a runner with a registration token SCIM provisioning requests from an identity provider Requests that Jira Cloud sends to the GitLab for Jira Cloud app , such as searching for and linking repositories Create-branch links from Jira that GitLab.com redirects to a GitLab Self-Managed or GitLab Dedicated instance Requests from the GitLab for Slack app Requests that trigger a pipeline with a pipeline trigger token Alerts that monitoring tools send to an alert integration endpoint These requests stay subject to the current limits .
The GitLab for Slack app also has its own limit for an IP address of 1,000 requests each hour and 100 requests each minute. Sustained limits Rate limit Free Premium Ultimate Authenticated traffic for a user 5,000 each hour 15,000 each hour 25,000 each hour Traffic for a top-level group 5,000 each hour Not yet confirmed Not yet confirmed Unauthenticated traffic from an IP address 60 each hour 60 each hour 60 each hour Burst limits Rate limit Free Premium Ultimate Authenticated traffic for a user 100 each minute, 300 for web traffic 1 1,250 each minute 2,000 each minute Traffic for a top-level group 400 each minute 5,000 each minute 10,000 each minute When you exceed a limit When a request is rate limited, GitLab responds with a 429 Too Many Requests status code.
Wait before you attempt the request again. Responses to throttled requests include a Retry-After header that tells you how many seconds remain until your quota resets, and a RateLimit-ResetTime header with the same information as a date and time. For project and group creation limits, the window is 24 hours, so Retry-After can be up to 86,400 seconds. All responses, throttled or not, include RateLimit-Limit , RateLimit-Remaining , and related headers that you can use to track your usage before you reach a limit.
For the full list, see response headers . To handle limits correctly: Wait for the duration given in Retry-After before you retry. Back off exponentially if you continue to be throttled. Monitor RateLimit-Remaining and slow down before you exhaust your quota. Rate limiting responses for the Projects, Groups, and Users APIs do not include informational headers. Response headers also do not reflect some other limits, so you can receive a 429 response even when the headers on your previous response showed remaining quota.
If you need more headroom If you reach a limit regularly, you have several options, from least to most committed: Optimize how you use the API. Batch requests, cache responses, use pagination, and honor the Retry-After header. Most usage stays below the limits. Authenticate your requests. Anonymous traffic receives the lowest allowance. Authenticating with a personal access token, an OAuth token, or a CI/CD job token gives you your plan’s full limits.
Upgrade your plan. Premium and Ultimate carry higher limits. Advanced Capacity will provide the option to raise the limits for a top-level group. Advanced Capacity Tier : Premium, Ultimate Offering : GitLab.com This page contains information related to upcoming products, features, and functionality. It is important to note that the information presented is for informational purposes only. Please do not rely on this information for purchasing or planning purposes.
The development, release, and timing of any products, features, or functionality may be subject to change or delay and remain at the sole discretion of GitLab Inc. Advanced Capacity raises the rate limits for a top-level group. The Advanced Capacity Pack is a flat annual add-on for a group with a sustained need above its plan’s limits. This add-on has no usage charges. Overage covers occasional spikes above your limit.
On each day your group exceeds its plan or Advanced Capacity Pack limit, you pay a fixed daily price. Your group cannot exceed the overage band you select when you buy or renew. For the bands, see GitLab pricing . Overage is on by default when you buy or renew a subscription. An Owner of the top-level group can turn off overage at any time, which keeps the group at its plan or Advanced Capacity Pack limit. The Enterprise Capacity Pack covers sustained needs above the Advanced Capacity Pack.
For more information, contact your account team or GitLab sales . If your usage is already above a new plan limit, requests above that limit are not rate-limited through your current subscription term. The new Premium and Ultimate limits are planned to take effect in January 2027, and GitLab does not enforce them until Advanced Capacity is available to buy. For more information, see GitLab pricing . Current rate limits These limits are in effect on GitLab.com today, and they continue to apply after rate limits by plan are introduced.
GitLab checks your plan’s limits first, then the limits in this table. Whichever limit is lower applies. A limit in this table can be lower than your plan’s limit, so you might reach it first. For example, authenticated API traffic for a user is limited to 2,000 requests each minute. On Free and Premium, the burst limit for your plan is lower, so you reach that first. On Ultimate, the burst limit is also 2,000 req
The rest of this page is on the live site.