GitLab.com hosts millions of projects for teams of each size that request a level they tin trust on. Demand is climbing quickly, and we expect level load to turn respective times complete this year. Predictable limits are what support GitLab.com accelerated for everyone connected it, including the automation and supplier workloads teams are building connected the platform.
To clasp that arsenic we scale, we're updating really complaint limits work. Starting October 19, 2026, complaint limits connected GitLab.com will align pinch your subscription tier.accounts and unauthenticated requests hap first, connected October 19. Premium and Ultimate move successful January 2027.
What is changing
Limits align pinch your subscription. Free, Premium, and Ultimate subscription plans get their ain limits, applied per personification and per top-level group.takes effect October 19; Premium and Ultimate successful January 2027.
Signing successful gets you the afloat limit. An authenticated petition is governed by your subscription scheme below. A petition that arrives pinch nary credentials gets 60 requests per hr per IP address.
The per-plan limits are published successful the rate limits documentation.
What happens connected October 19
There will beryllium 2 preview windows forand unauthenticated traffic, connected October 7 and October 14 from 15:00 to 19:00 UTC. Signed-in Premium and Ultimate requests are not affected, since those limits do not alteration until January. Unauthenticated requests are capped nary matter wherever they travel from, including automation moving against a paid relationship without credentials. A preview model (engineers telephone these brownouts) is simply a short, planned model wherever we move the caller limits connected and past move them backmost off. Nothing other astir the work changes while it runs. The constituent is to springiness you a existent look astatine really your ain workloads behave nether the caller limits, weeks earlier they use for good.
On October 19 the caller limits return effect.
We group these limits by looking astatine really GitLab.com is really used. Almost each users are already wrong the caller limits and won't announcement immoderate change. We besides looked astatine what akin platforms allow. Thelimit and the anonymous allowance lucifer the manufacture norm, while Premium and Ultimate are much generous, astatine levels different platforms reserve for their endeavor tiers aliases don't people astatine all.
If you're adjacent to a limit
If you find that you are nearing a limit, authenticate your requests. It's usually a mini change: Invoking a personal entree token, an OAuth token, aliases the CI/CD occupation token each move a petition disconnected the anonymous 60 requests per hr and onto your plan's limits, which are overmuch higher.
Next, look astatine really you're calling the API. Batching, caching, and pagination spell a agelong way, and polling successful a tight loop burns done your allowance fast. When you do transverse a limit, you get an HTTP 429 backmost pinch a Retry-After header saying really agelong to wait, truthful a customer that sounds its ain consequence headers mostly fixes itself. Backing disconnected exponentially recovers faster than retrying immediately.
Upgrading to Premium aliases Ultimate increases the limits, too, per personification and per top-level group.
If you request a higher limit connected an ongoing basis, we are moving connected a measurement to acquisition capacity supra the modular scheme limits, pinch specifications coming later this year. If that sounds for illustration you, scope retired to your relationship squad aliases email [email protected] and show america what you need.
What changes and what doesn't
These limits are group truthful nary azygous workload tin slow the level for everyone else. Ordinary signed-in activity isn't the target, and, for almost each users, a normal time looks identical. Browsing the UI, moving successful your editor, pushing and pulling pinch git, and moving CI/CD wrong your scheme each transportation connected precisely arsenic they do today. Some dense automation and a mini number of Free-tier workloads will scope the caller ceilings.
What doesn't change:
- You tin ever scope and export your ain information and repositories.
- GitLab Self-Managed and GitLab Dedicated limits enactment pinch your operator. This is only a GitLab.com change.
- We'll notify you earlier we make further changes.
A reminder: Make judge to authenticate your requests to GitLab.com truthful your limits are higher.
FAQ
How do I cognize whether this affects me?
Compare your busiest infinitesimal against the published limits for your plan. Most customers are not close. The quickest awesome successful the meantime is the RateLimit-Remaining header connected your API responses, which tells you really overmuch of your existent model is left, and we are building a position successful the merchandise for merchandise later this twelvemonth that shows your usage against your plan's limits.
My task is nationalist and busy. What are my options?
Three things help. Ask the automation that calls your task to motion in, which moves it onto its ain limits alternatively than the anonymous allowance. Make the task backstage if the postulation is not coming from the assemblage you built it for, which stops anonymous callers reaching it astatine all. Or upgrade to Premium aliases Ultimate for overmuch higher limits.
What if I americium a personnel of respective top-level groups?
Your personification limit will beryllium the highest subscription tier disposable to you. If you are a personnel of an Ultimate group, you will person entree to the Ultimate limit.
What happens erstwhile I deed a limit?
You get 429 Too Many Requests pinch RateLimit-* headers and a Retry-After. Wait the interval it gives you, past retry.
My integration genuinely can't authenticate. What now?
Reach retired to america astatine [email protected]. There are morganatic anonymous patterns, a nationalist position badge being the evident one. If you are concerned that an integration you ain whitethorn beryllium affected, interaction us.
Does this use to GitLab Self-Managed aliases GitLab Dedicated?
No. This is simply a GitLab.com-only change.
Additional resources
- Rate limits by plan
- Authenticating your API requests
- Questions, aliases you've encountered a lawsuit we haven't thought of? Contact your relationship squad aliases email [email protected].
English (US) · 
Indonesian (ID) · 
