Rate limits on GitLab.com are changing

GitLab.com will introduce subscription-tier-based rate limits to manage growing platform demand, with Free accounts and unauthenticated traffic affected beginning October 19, 2026, and Premium and Ultimate limits changing in January 2027. Unauthenticated requests will be limited to 60 per hour per IP address, while authenticated requests will receive limits based on the user’s or top-level group’s subscription tier; GitLab will offer Free-tier and anonymous-traffic preview brownouts on October 7 and 14 to help users test workloads. Most ordinary signed-in activity, including UI use, Git operations, editors, and plan-supported CI/CD, is expected to remain unaffected, though heavy automation and some Free-tier workloads may reach the new ceilings. GitLab recommends authenticating API calls with personal access, OAuth, or CI/CD job tokens; using batching, caching, pagination, and exponential backoff; and monitoring RateLimit-Remaining and Retry-After headers. Users needing more capacity can upgrade tiers, contact GitLab about exceptional anonymous integrations or future purchasable additional capacity, while GitLab Self-Managed and Dedicated deployments are not affected.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.