GitLab CI/CD · Rate Limits
Gitlab Ci Rate Limits
GitLab.com SaaS enforces general request, search, autocomplete and raw-file rate limits per IP / user / project, plus per-project pipeline and CI resource limits. Self-managed instances expose the same configuration via Application Settings.
Gitlab Ci Rate Limits is the machine-readable rate-limit profile for GitLab CI/CD on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 10 rate-limit definitions, measuring requests and jobs.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include DevOps, CI/CD, Pipelines, GitLab, and DevSecOps.
10 Limits
Throttle: 429
DevOpsCI/CDPipelinesGitLabDevSecOpsRate LimitingQuotasThrottling
Limits
Search API (authenticated) user
30
Search API (unauthenticated) ip
10
Autocomplete users (authenticated) user
300
Autocomplete users (unauthenticated) ip
100
Raw blob endpoint (per project & path) project+path
300
Raw blob endpoint (unauthenticated, per project) project
800
Default API (unauthenticated) ip
500
Default global API throttle on GitLab.com.
Default API (authenticated) user
2000
Default global API throttle on GitLab.com.
Pipeline jobs in active pipelines project
tier-dependent
Tier-dependent ceiling on jobs across active pipelines.
Maximum deployment jobs pipeline
500
Default maximum deployment jobs per pipeline.
Policies
Backoff Strategy
Honor Retry-After on 429; use exponential backoff with jitter.
Tokens
Use personal/project/group access tokens or CI job tokens; OAuth supported.
Sources
- https://docs.gitlab.com/ee/user/gitlab_com/index.html#gitlabcom-specific-rate-limits
- https://docs.gitlab.com/administration/instance_limits/
- https://docs.gitlab.com/api/rest/troubleshooting/#status-code-429
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.