GitLab.com hosts millions of projects for teams of every size that need a platform they can rely on. Demand is climbing quickly, and platform load is expected to grow several times over this year. Predictable limits are what keep GitLab.com fast for everyone, including automation and agent workloads teams are building on the platform.

Starting October 19, 2026, rate limits on GitLab.com will align with subscription tier. Free accounts and unauthenticated requests happen first, on October 19. Premium and Ultimate move in January 2027. What is changing: limits align with subscription. Free, Premium, and Ultimate subscription plans get their own limits, applied per user and per top-level group. Free takes effect October 19; Premium and Ultimate in January 2027. Signing in gets you the full limit. An authenticated request is governed by your subscription plan. A request that arrives with no credentials gets 60 requests per hour per IP address. The per-plan limits are published in the rate limits documentation.

On October 19, the new limits take effect. There will be two preview windows for Free and unauthenticated traffic, on 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 change until January. Unauthenticated requests are capped no matter where they come from, including automation running against a paid account without credentials. Almost all users are already inside the new limits and won't notice any change. If you find that you are nearing a limit, authenticate your requests. It's usually a small change: invoking a personal access token, an OAuth token, or the CI/CD job token all move a request off the anonymous 60 requests per hour and onto your plan's limits, which are much higher.