GitLab has proposed request-rate limits for GitLab.com that depend on the plan and apply to each user. The new limits are not in effect yet, and the current limits will remain after they take effect.

For authenticated traffic, each plan will have an hourly limit for sustained work and a per-minute limit for short spikes. The hourly user limit will be 5,000 requests on Free, 15,000 on Premium, and 25,000 on Ultimate.

When a limit is exceeded, GitLab will return 429 Too Many Requests and advises waiting for the time specified in the Retry-After header before retrying.

Claim check:

  • GitLab has proposed request-rate limits for GitLab.com that depend on the plan and apply to each user. (confirmed by the publication itself: evidence; «Rate limits are becoming tier-aware. Instead of a single number for everyone, limits reflect your plan and apply per user.»)
  • The new limits are not in effect yet, and the current limits will remain after they take effect. (confirmed by the publication itself: evidence; «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.»)
  • For authenticated traffic, each plan will have an hourly limit for sustained work and a per-minute limit for short spikes. (confirmed by the publication itself: evidence; «Each plan has two limits for authenticated traffic, and the hourly limit takes precedence: A sustained limit, measured each hour. This limit governs your usage, and is the number to plan against. A burst limit, measured each minute. This limit is a default set by GitLab, so that a short spike does not consume an entire hourly allowance at once.»)
  • The hourly user limit will be 5,000 requests on Free, 15,000 on Premium, and 25,000 on Ultimate. (confirmed by the publication itself: evidence; «Authenticated traffic for a user 5,000 each hour 15,000 each hour 25,000 each hour»)
  • When a limit is exceeded, GitLab will return 429 Too Many Requests and advises waiting for the time specified in the Retry-After header before retrying. (confirmed by the publication itself: evidence; «When a request is rate limited, GitLab responds with a 429 Too Many Requests status code. 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.»)

Publications:

Primary sources:

score 71.9 out of 100 · kind: announcement