--- title: GitLab Tightens Rate Limits as Coding Agents Drive Demand description: GitLab is rolling out new rate limits on GitLab.com starting October 19, driven by surging traffic from AI coding agents and automated tools. Unauthenticated... canonical: https://daily.dev/posts/gitlab-tightens-rate-limits-as-coding-agents-drive-demand-znzakbnvg twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: GitLab Tightens Rate Limits as Coding Agents Drive Demand | daily.dev og:description: GitLab is rolling out new rate limits on GitLab.com starting October 19, driven by surging traffic from AI coding agents and automated tools. Unauthenticated... og:url: https://daily.dev/posts/gitlab-tightens-rate-limits-as-coding-agents-drive-demand-znzakbnvg og:image: https://api.daily.dev/og/posts/znZAkBNvG.png og:image:alt: GitLab Tightens Rate Limits as Coding Agents Drive Demand og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # GitLab Tightens Rate Limits as Coding Agents Drive Demand **[DevOps.com](https://daily.dev/sources/devops)** · 3 min read · 0 upvotes · 0 comments ## Summary GitLab is rolling out new rate limits on GitLab.com starting October 19, driven by surging traffic from AI coding agents and automated tools. Unauthenticated requests will be capped at 60 per hour per IP, while Free, Premium, and Ultimate authenticated users get 5,000, 15,000, and 25,000 requests per hour respectively, with matching per-minute burst limits. Free-tier and unauthenticated users face enforcement first; Premium and Ultimate authenticated traffic keeps current allowances until January 2027. GitLab plans temporary test windows on October 7 and 14, a future paid capacity add-on, and a usage-monitoring dashboard, while recommending caching, batching, and reduced polling to stay under thresholds. The changes apply only to GitLab.com, not Self-Managed or Dedicated deployments. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What are GitLab.com's new API rate limits starting October 2026? Unauthenticated requests are limited to 60 per hour per IP address. Authenticated Free-tier users get 5,000 requests per hour, Premium subscribers get 15,000, and Ultimate subscribers get 25,000. Per-minute burst limits are also set at 100, 1,250, and 2,000 requests respectively. Enforcement begins October 19, 2026 for Free-tier and unauthenticated traffic, with Premium and Ultimate authenticated limits changing in January 2027. _Teams adjusting CI/CD and agent workflows to new GitLab quotas can track platform changes like this on daily.dev._ ### Why is GitLab introducing new rate limits on GitLab.com? GitLab is tightening rate limits because AI coding agents and automated development tools are generating much higher API traffic, with the company forecasting several times more traffic in 2026. The limits are meant to protect infrastructure performance, and GitLab says nearly all current users already operate below the new thresholds, so the restrictions mainly target heavy automation workloads and a small share of Free-tier accounts. _Developers scaling AI agent automation against platform limits can follow infrastructure shifts like this via daily.dev._ ### How can I avoid hitting GitLab's new anonymous rate limit with my automated tool? Authenticate requests using a personal access token, OAuth token, or CI/CD job token instead of sending unauthenticated calls, since unauthenticated traffic is capped at only 60 requests per hour per IP regardless of the account's paid plan. GitLab also recommends caching frequently requested data, batching API operations, and reducing unnecessary polling to stay within thresholds; exceeding limits triggers an HTTP 429 with a Retry-After header. _Anyone tuning automated tooling to a provider's quotas can keep tabs on similar API changes through daily.dev._ ## Similar posts on daily.dev - [GitLab Adds Flat-Rate Code Reviews, Free-Tier AI Access, and Spending Caps](https://daily.dev/posts/gitlab-adds-flat-rate-code-reviews-free-tier-ai-access-and-spending-caps-ipmcq22nq) · InfoQ · 0 upvotes · 0 comments - [GitLab 18.11: Budget guardrails for GitLab Credits](https://daily.dev/posts/gitlab-18-11-budget-guardrails-for-gitlab-credits-dtn7kgt6u) · GitLab · 0 upvotes · 0 comments - [All roads lead to metered pricing](https://daily.dev/posts/all-roads-lead-to-metered-pricing-yvoujksya) · Kilo Blog · 132 upvotes · 31 comments --- Tags: [#devops](https://daily.dev/tags/devops), [#ai-agents](https://daily.dev/tags/ai-agents), [#gitlab](https://daily.dev/tags/gitlab) [View this post on daily.dev](https://daily.dev/posts/gitlab-tightens-rate-limits-as-coding-agents-drive-demand-znzakbnvg) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"GitLab Tightens Rate Limits as Coding Agents Drive Demand","url":"https://daily.dev/posts/gitlab-tightens-rate-limits-as-coding-agents-drive-demand-znzakbnvg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/gitlab-tightens-rate-limits-as-coding-agents-drive-demand-znzakbnvg"},"datePublished":"2026-09-21T22:58:12.272Z","dateModified":"2026-09-21T22:59:05.737Z","description":"GitLab is rolling out new rate limits on GitLab.com starting October 19, driven by surging traffic from AI coding agents and automated tools. Unauthenticated...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/965304d3a25c466433bb069895749909?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/965304d3a25c466433bb069895749909?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"DevOps.com","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"DevOps.com","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/db8f2265cff0416c878c6e7e92bb8715","url":"https://daily.dev/sources/devops"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/gitlab-tightens-rate-limits-as-coding-agents-drive-demand-znzakbnvg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"devops,ai-agents,gitlab","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"DevOps.com","item":"https://daily.dev/sources/devops"},{"@type":"ListItem","position":3,"name":"GitLab Tightens Rate Limits as Coding Agents Drive Demand"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/gitlab-tightens-rate-limits-as-coding-agents-drive-demand-znzakbnvg#faq","mainEntity":[{"@type":"Question","name":"What are GitLab.com's new API rate limits starting October 2026?","acceptedAnswer":{"@type":"Answer","text":"Unauthenticated requests are limited to 60 per hour per IP address. Authenticated Free-tier users get 5,000 requests per hour, Premium subscribers get 15,000, and Ultimate subscribers get 25,000. Per-minute burst limits are also set at 100, 1,250, and 2,000 requests respectively. Enforcement begins October 19, 2026 for Free-tier and unauthenticated traffic, with Premium and Ultimate authenticated limits changing in January 2027. Teams adjusting CI/CD and agent workflows to new GitLab quotas can track platform changes like this on daily.dev."}},{"@type":"Question","name":"Why is GitLab introducing new rate limits on GitLab.com?","acceptedAnswer":{"@type":"Answer","text":"GitLab is tightening rate limits because AI coding agents and automated development tools are generating much higher API traffic, with the company forecasting several times more traffic in 2026. The limits are meant to protect infrastructure performance, and GitLab says nearly all current users already operate below the new thresholds, so the restrictions mainly target heavy automation workloads and a small share of Free-tier accounts. Developers scaling AI agent automation against platform limits can follow infrastructure shifts like this via daily.dev."}},{"@type":"Question","name":"How can I avoid hitting GitLab's new anonymous rate limit with my automated tool?","acceptedAnswer":{"@type":"Answer","text":"Authenticate requests using a personal access token, OAuth token, or CI/CD job token instead of sending unauthenticated calls, since unauthenticated traffic is capped at only 60 requests per hour per IP regardless of the account's paid plan. GitLab also recommends caching frequently requested data, batching API operations, and reducing unnecessary polling to stay within thresholds; exceeding limits triggers an HTTP 429 with a Retry-After header. Anyone tuning automated tooling to a provider's quotas can keep tabs on similar API changes through daily.dev."}}]} ```