Hacker News front pageSam Wiskow4 min readintermediate
Rate limits on GitLab.com are changing
Summary
GitLab.com will tie API rate limits to subscription tiers: free users (and unauthenticated IPs) get 60 req/hr, while Premium/Ultimate get higher per‑user and per‑group caps starting Oct 19 2026 (free) and Jan 2027 (paid). Authenticated requests use the plan’s limits; hitting a limit returns 429 with Retry‑After. Preview “brownout” windows on Oct 7 and 14 let you test the new caps. If you need mor…
- Rate limits become tier‑specific: free = 60 req/hr per IP; Premium/Ultimate have higher, unpublished caps.
- Unauthenticated traffic is always limited to 60 req/hr regardless of project visibility.
- Authenticated requests (PAT, OAuth, CI job token) are counted against the user’s plan limits.
- Two preview windows (Oct 7 & 14, 15:00‑19:00 UTC) will temporarily enforce the new free limits for testing.
Automation and CI/CD pipelines that hit the anonymous 60 req/hr ceiling can suddenly throttle, breaking builds or status badges. Aligning limits with subscription tiers encourages proper authentication and gives paid teams higher throughput, while protecting overall platform performance as usage sc…
5/10




